Skip to main content
BumbleTap
Add to ChromeInstall

.NET 8 End of Life (EOL): Support Ended 10 November 2026, What to Do Now

.NET 8 reached end of support on 10 November 2026 with its final patch, 8.0.34, and .NET 9 ended the same day. Apps keep running, but Microsoft ships no more fixes. Who still patches it, what ends next, and how to move to .NET 10.

Written Shahzeb Umer

Subscribe

Status

No longer supportedLTS

Support ended .

Since end of life
9 days
Final release
8.0.34
Move to
Microsoft .NET 10fixed until 14 Nov 2028

3 years of support

  • Supported14 Nov 2023 – 10 Nov 2026
  • No fixes10 Nov 2026 – today

Supported for 3 years, from 14 Nov 2023 to 10 Nov 2026.

Who still patches it

Nine places Microsoft .NET 8 runs, five deadlines.

  • Microsoft (runtime, ASP.NET Core, SDK): Ended 10 Nov 2026, final 8.0.34
  • Azure App Service (Windows and Linux): Runs unpatched, no end set
  • Azure Functions (isolated and in-process): Runs unpatched, may get 1 instance
  • AWS Lambda (dotnet8): Updates blocked 31 Aug 2027
  • Ubuntu 22.04, 24.04 (dotnet8, Main): 8.0.34; later fixes untested
  • RHEL 8, 9, 10 (dotnet8.0): Ended 10 Nov 2026, last 8.0.34
  • Amazon Linux 2023 (dotnet-sdk-8.0): End of support 10 Nov 2026
  • Container images (mcr.microsoft.com/dotnet, 8.0): Last rebuilt 10 Nov 2026
  • HeroDevs NES (paid, third party): Paid, price on request
Sources: .NET support policy and release metadata, Azure App Service and Azure Functions language support, AWS Lambda runtimes, Ubuntu archive and Microsoft's Ubuntu guide, Red Hat .NET life cycle and errata, Amazon Linux 2023 package list, dotnet-docker, HeroDevs. Checked 17 Nov 2026.

Where to move

Be on Microsoft .NET 10.

The short version

  • .NET 8 reached end of support on 10 November 2026, three years after its release as a long-term support (LTS) release on 14 November 2023. Its final patch, 8.0.34, with SDKs 8.0.428 and 8.0.134, shipped that day. .NET 9 ended alongside it, with 9.0.23. Microsoft ships no more fixes for either.
  • Apps keep running. Azure App Service and Azure Functions run them without security patches, and Functions may limit them to one instance. AWS Lambda deprecated dotnet8 the same day and blocks updates from 31 August 2027. Microsoft's 8.0 container tags were last rebuilt on 10 November. Ubuntu 22.04 and 24.04 still carry .NET 8 in their main archive.
  • Move to .NET 10, the current LTS release, supported until 14 November 2028. .NET 11 ends on the same day, so it buys no extra time. Budget for the Azure Functions in-process model, whose support also ended on 10 November, BinaryFormatter, EF Core 10 and NuGet's transitive audit.
On this page
  1. What changed on 10 November 2026
  2. Who still patches .NET 8
  3. What ends next
  4. How to check what you run
  5. Which version to move to: 10
  6. How to upgrade from .NET 8 to .NET 10
  7. A note on .NET 9
  8. Sources

.NET 8 reached end of support on 10 November 2026. That day Microsoft released its final patch, 8.0.34, with SDKs 8.0.428 and 8.0.134, and stopped servicing the release. In the words of its announcement, Microsoft "will no longer provide servicing updates, security fixes, or technical support" for it.

Your apps keep running. Nothing in the runtime checks the date, and a service on 8.0.34 behaves now as it did on 9 November. What ended is the supply of fixes. .NET 9 ended the same day with 9.0.23, so the oldest .NET that Microsoft still patches is now .NET 10, supported until 14 November 2028.

.NET 8 came out on 14 November 2023 as a long-term support (LTS) release, which Microsoft supports for three years. The .NET hub has every version's dates.

What changed on 10 November 2026

The last patch shipped. 8.0.34 was a security release: its release notes list 17 CVEs, across ASP.NET Core, the runtime and Visual Studio components. It closed a busy final stretch. Microsoft's release metadata lists more than 100 CVEs across the twelve .NET 8 patches of 2026, 40 of them in 8.0.32 on 13 October. An out-of-band 8.0.33 followed on 25 October, for a flaw in the Brotli decoder. The next vulnerability found in .NET 8 gets no fix from Microsoft.

Two of the final fixes need more than the runtime. CVE-2026-118747 is fixed in the System.Formats.Cbor package, version 8.0.2 on the .NET 8 line, so apps that reference it need a package update and a rebuild. CVE-2026-118741 is in ASP.NET Core Identity scaffolding and templates, and Microsoft says updating the runtime alone "does not repair generated code": apps generated from them have to be corrected, rebuilt and redeployed.

Azure stopped patching it. App Service keeps running .NET 8 apps "unchanged", but "can't provide security patches or related customer support" for the runtime, and removes outdated runtimes from the portal's create and configure pages. Azure Functions apps on .NET 8 "can still be created and deployed, and they continue to run", without security patches, and Microsoft may limit them to a single instance. Azure Static Web Apps announced the same end for managed Functions APIs on .NET 8 and 9.

The Azure Functions in-process model lost support. Its support ended the same day, and .NET 8 was the only version it supported. Microsoft's retirement notice says in-process apps can still be used, "but they will no longer receive security and feature updates", and every in-process app has to move to the isolated worker model to reach a supported .NET.

AWS Lambda deprecated dotnet8. AWS may no longer apply security patches to the runtime, functions using it are no longer eligible for technical support, and the Lambda console no longer creates or updates them.

Microsoft's container images froze. The 8.0 tags were rebuilt with 8.0.34 on 10 November, and on 13 November Microsoft removed .NET 8 and 9 from its dotnet-docker repository. The tags still pull, but "will no longer receive updates for any reason", operating system packages included. The same change retired the Debian 12 (bookworm-slim), Ubuntu 22.04 (jammy) and Windows Server 2019 images, which only .NET 8 and 9 still used. latest moved to .NET 11 on 10 November.

Your build won't warn you. The SDK raises NETSDK1138 when a project targets an out-of-support framework, but as of 17 November 2026 its list of end-of-life versions still stops at 7.0, in the SDK's main branch and its 10.0 and 11.0 release branches. A net8.0 project builds cleanly, so use the checks below to find them.

Who still patches .NET 8

Where it runs Status since 10 November 2026 What happens next Source
Microsoft: runtime, ASP.NET Core, SDK Ended; final patch 8.0.34, SDKs 8.0.428 and 8.0.134 No fixes or technical support Support policy
Azure App Service, Windows and Linux Runs unchanged, without security patches or related support; removed from the portal's create pages No removal date; subscription owners get an email before a runtime is removed App Service policy
Azure Functions, isolated worker model Apps can still be created, deployed and run, without security patches; may be limited to one instance Move to .NET 10; from Linux Consumption, via Flex Consumption Functions policy
Azure Functions, in-process model The model's support ended 10 November 2026; apps run without security or feature updates Migrate to the isolated worker model Retirement notice
AWS Lambda, dotnet8 on Amazon Linux 2023 Deprecated 10 November 2026: no guaranteed patches, no technical support, no console create or update Create blocked 29 July 2027, update blocked 31 August 2027; invocations continue Lambda runtimes
Ubuntu 22.04 and 24.04, dotnet8 in Main 8.0.34 (SDK 8.0.134) in the security pocket since 10 November Canonical's commitment past Microsoft's date is untested for .NET 8 Ubuntu archive
Ubuntu 26.04, ppa:dotnet/backports Best-effort support only "does not extend beyond the Microsoft-provided support lifetime" .NET on Ubuntu
RHEL 8, 9 and 10, dotnet8.0 8.0.34 (SDK 8.0.134) in advisories issued 11 November 2026 Red Hat's life cycle ends .NET 8 on 10 November 2026 Red Hat, RHSA-2026:99146
Amazon Linux 2023, dotnet-sdk-8.0 End of support 10 November 2026 Leaves Amazon Linux's support AL2023 packages
mcr.microsoft.com/dotnet images, 8.0 Last rebuilt 10 November with 8.0.34; removed from the repository 13 November Still pull, never updated Supported tags
HeroDevs NES for .NET Paid patched builds for .NET 6, 8 and 9 No end date announced; price on request HeroDevs

Ubuntu's promise needs reading carefully. Microsoft's Ubuntu guide says Canonical supports .NET versions in the built-in feed "for the lifetime of that Ubuntu version, even beyond the Microsoft-provided support lifetime". Standard support for Ubuntu 24.04 runs to May 2029, and for 22.04 to May 2027. The record so far is thin: 22.04's dotnet6 package, also in Main, hasn't changed since 6.0.136, its build of Microsoft's final .NET 6 release from November 2024. The promise also covers only Ubuntu's package, not a copy from dotnet-install.sh, Microsoft's binaries or a container image on the same machine. Plan around Microsoft's date, on Ubuntu too.

Red Hat follows Microsoft. Red Hat shipped 8.0.34 for RHEL 8, 9 and 10 the day after Microsoft, and its life cycle page says "Microsoft establishes and maintains the life-cycle support policy for .NET on Red Hat Enterprise Linux". It lists the same end date for .NET 8 and 9.

Paid support comes from a third party. HeroDevs says NES for .NET is a drop-in replacement covering the runtime, SDK, ASP.NET Core, Entity Framework, WPF and WinForms, with a new release each time it fixes a security issue. It publishes no prices and licenses by the number of users who commit code. Microsoft's own support policy describes no paid extension.

What ends next

AWS Lambda: 29 July and 31 August 2027. Until the first date you can still create dotnet8 functions through the AWS CLI, AWS SAM or CloudFormation, though not in the console, and until the second you can update them. After 31 August a deploy to a dotnet8 function fails. You can still switch it to a supported runtime, but not back. Lambda's responsibility for the dotnet8 runtime and its container base image ended at deprecation.

Azure Functions on Linux Consumption. .NET 9 is the last .NET version that plan supports, and the plan itself retires on 30 September 2028. A .NET 8 app on Linux Consumption has to move to Flex Consumption before it can run .NET 10.

Microsoft's NuGet packages. On 10 November Microsoft shipped version 11.0.0 of System.Text.Json and the Microsoft.Extensions packages with no net8.0 or net9.0 builds: they target net10.0 and net11.0, plus .NET Standard and .NET Framework 4.6.2. A .NET 8 project that takes one gets the .NET Standard build and a build warning that the package "doesn't support net8.0 and has not been tested with it". The 10.0 packages still include net8.0 builds. EF Core 10 targets only .NET 10, and EF Core 8 and 9, the versions that ran on .NET 8, lost support on 10 November.

Visual Studio. In June, Microsoft said a future Visual Studio 2022 servicing update would mark the .NET 8 and 9 components out of support. Existing installations aren't affected, and the installer's "remove out of support components" option removes them. Targeting net10.0 is supported only from Visual Studio 2026, version 18.0.

How to check what you run

On a machine or in a container:

dotnet --list-runtimes   # Microsoft.NETCore.App 8.0.x or Microsoft.AspNetCore.App 8.0.x means .NET 8
dotnet --list-sdks       # 8.0.428 and 8.0.134 are the last .NET 8 SDKs
dotnet --info            # also shows which global.json, if any, picked the SDK
apt list --installed 'dotnet*' 'aspnetcore*' 2>/dev/null   # Ubuntu's packages

In your repositories:

grep -rhoE --include='*.csproj' --include='*.fsproj' --include='*.vbproj' --include='Directory.Build.props' \
  '<TargetFrameworks?>[^<]+' . | sort | uniq -c        # net8.0 or net9.0 needs to move
cat global.json 2>/dev/null                            # an 8.0.xxx SDK pins an out-of-support SDK
grep -rnE --include='Dockerfile*' 'mcr\.microsoft\.com/dotnet/[a-z-]+:(8|9)\.0' .
grep -rnE "dotnet-version: *['\"]?(8|9)\." .github/workflows/
grep -rn 'System.Formats.Cbor' --include='*.csproj' --include='Directory.Packages.props' .

On your platforms:

# Azure App Service on Linux: DOTNETCORE|8.0 means .NET 8
az webapp config show --name APP --resource-group RG --query linuxFxVersion -o tsv

# Azure Functions: "dotnet" is the in-process model, "dotnet-isolated" the isolated worker
az functionapp config appsettings list --name APP --resource-group RG \
  --query "[?name=='FUNCTIONS_WORKER_RUNTIME'].value" -o tsv
az functionapp show --name APP --resource-group RG --query "siteConfig.netFrameworkVersion" -o tsv

# AWS Lambda: once per region and account
aws lambda list-functions --function-version ALL --region us-east-1 --output text \
  --query "Functions[?Runtime=='dotnet8'].FunctionArn"

Which version to move to: 10

Move to .NET 10. It is the current LTS release, supported until 14 November 2028, and its latest patch is 10.0.15, from 10 November 2026. It is the version AWS Lambda offers as a managed runtime, Red Hat lists in its life cycle and Ubuntu 24.04 and 26.04 ship in their own archive.

.NET 11 buys features, not time. It came out on 10 November 2026 as a Standard Term Support release and also ends on 14 November 2028, and Lambda has no dotnet11 runtime. The .NET 11 page covers when its features are worth taking.

Skip 9. It ended with 8.

Version Support Latest patch Visual Studio to target it AWS Lambda
8 (LTS) Ended 10 November 2026 8.0.34, final 2022, 17.8 or later dotnet8, deprecated
9 (STS) Ended 10 November 2026 9.0.23, final 2022, 17.12 or later Container base image only, deprecated
10 (LTS) Until 14 November 2028 10.0.15 2026, 18.0 or later dotnet10, deprecated 14 November 2028
11 (STS) Until 14 November 2028 11.0.0 2026, 18.12 or later None

Whichever you pick, you move again before November 2028. .NET 12, expected in November 2027, will be the next LTS release: Microsoft ships a major version every November, and the ones released in odd-numbered years are LTS.

How to upgrade from .NET 8 to .NET 10

  1. Install the tools first: Visual Studio 2026 or the .NET 10 SDK, 10.0.404 at present, and update global.json. The new SDK still builds net8.0 projects, because Microsoft keeps targeting support for out-of-support versions, so the SDK can move before the code does.
  2. Retarget. Change <TargetFramework>net8.0</TargetFramework> to net10.0, as Microsoft's announcement shows, then move every Microsoft.AspNetCore.*, Microsoft.EntityFrameworkCore.* and Microsoft.Extensions.* package to 10.0.x.
  3. Build with warnings visible and work through the obsoletions and NuGet audit warnings before suppressing anything.
  4. Change where it runs: FROM lines to 10.0, dotnet-version in CI, DOTNETCORE|10.0 on App Service for Linux, dotnet10 on Lambda, and the .NET 10 isolated worker stack on Functions.
  5. Test behind a slot or canary, then retire the .NET 8 build.

Going straight from 8 to 10 is normal, but skipping 9 doesn't skip its breaking changes. These are the ones most likely to cost time; the .NET 10 page has the longer list.

BinaryFormatter throws (9). The built-in implementation "throws exceptions on use, even with the settings that previously enabled its use". A separate, unsupported NuGet package restores it; moving to another serializer is the real fix.

NuGet audits transitive packages (10). For projects targeting .NET 10, NuGetAuditMode defaults to all, so a vulnerable package deep in the graph raises NU1901 to NU1904, which fails builds that treat warnings as errors. dotnet nuget why <package> finds what pulled it in.

EF Core 10 requires .NET 10. EF Core 9 ran on .NET 8, so an app on EF Core 9 moves both at once and takes the EF Core 10 breaking changes with it.

Azure Functions in-process to isolated. [FunctionName] becomes [Function], Microsoft.Azure.WebJobs.* packages give way to Microsoft.Azure.Functions.Worker.Extensions.*, and FUNCTIONS_WORKER_RUNTIME becomes dotnet-isolated. Serialization moves to System.Text.Json, which ignores Newtonsoft attributes such as [JsonProperty] without an error. Changing the setting and publishing the code are two restarts with a mismatch between them, so do both in a staging slot and swap.

The container OS changes (10). The 8.0 tags were Debian 12. 10.0 is Ubuntu 24.04, and Microsoft publishes no Debian images for .NET 10, so apt-get package names and anything that inspects the OS need checking.

No default SIGTERM handler (10). The runtime no longer handles termination signals itself, so a console app outside the Generic Host exits immediately on docker stop without raising ProcessExit. ASP.NET Core apps and apps using UseConsoleLifetime are unaffected.

ASP.NET Core 10 defaults. Cookie authentication no longer redirects known API endpoints to a login page, and WebHostBuilder, IWebHost, WebHost and Razor runtime compilation are obsolete, which breaks builds that treat warnings as errors.

A note on .NET 9

.NET 9 ended on the same day as 8, with 9.0.23 and SDKs 9.0.321 and 9.0.124 as its final release. It was a Standard Term Support release due to end on 12 May 2026. In September 2025 Microsoft moved STS releases to 24 months of support, starting with .NET 9. Its reason was dependencies: an out-of-band release can pull STS versions of packages into an app built on an LTS release, and under the old policy those packages lost support first.

It has even less afterlife than 8. Ubuntu's LTS releases carry it only in the backports PPA, whose best-effort support stops at Microsoft's date. AWS Lambda only ever offered it as a container base image, deprecated on 10 November. Red Hat and Amazon Linux 2023 ended it the same day. Azure Functions treats it like 8, and it is the last .NET version Functions supports on Linux Consumption.

Move 9 apps to 10 as well. It is the smaller step, since only .NET 10's breaking changes apply. One leftover from the final release: the .NET 9 fix for CVE-2026-118747 is System.Formats.Cbor 9.0.24, not 9.0.23, so updating the runtime alone doesn't fix it.

Sources

Common questions

What is the .NET 8 end of support date?
10 November 2026, Microsoft's Patch Tuesday that month. .NET 8 was a long-term support (LTS) release, supported for three years from its release on 14 November 2023. Its final patch, 8.0.34, shipped the same day, and .NET 9 reached end of support alongside it.
Is .NET 8 still supported?
Not by Microsoft. Since 10 November 2026 it provides no "servicing updates, security fixes, or technical support" for .NET 8. A few platforms carry it on their own terms: Ubuntu 22.04 and 24.04 keep it in their main archive, AWS Lambda accepts updates to dotnet8 functions until 31 August 2027, and HeroDevs sells patched builds. Move to .NET 10.
What is the last version of .NET 8?
8.0.34, released on 10 November 2026, with SDKs 8.0.428 and 8.0.134. Its release notes list 17 CVEs. If you run an older 8.0.x, update to 8.0.34 at least. Two of its fixes need more than the runtime: the System.Formats.Cbor package moves to 8.0.2, and ASP.NET Core Identity code generated from the old scaffolding has to be corrected and redeployed.
Do .NET 8 apps still run after end of support?
Yes. Microsoft says apps built on .NET 8 "will continue to run", and nothing in the runtime checks the date. Azure App Service and Azure Functions keep running them without security patches, and Functions may limit them to one instance. What stops is the fixes: the next vulnerability found in .NET 8 gets none from Microsoft.
When did .NET 9 support end?
Also on 10 November 2026, with 9.0.23 as its final patch. .NET 9 is a Standard Term Support (STS) release and was due to end on 12 May 2026, until Microsoft extended STS support from 18 to 24 months in September 2025. .NET 9 apps should move to .NET 10 as well.
What happens to .NET 8 on Azure App Service and Azure Functions?
Apps keep running. App Service "can't provide security patches or related customer support" for an end-of-support runtime and removes it from the portal's create and configure pages. Functions apps on .NET 8 can still be created and deployed, but get no security patches and may be limited to one instance. Support for the Functions in-process model also ended on 10 November 2026.
What happens to .NET 8 on AWS Lambda?
AWS deprecated the dotnet8 runtime on 10 November 2026. AWS may no longer patch it, functions using it lose technical support, and the console no longer creates or updates them. Lambda blocks creating dotnet8 functions from 29 July 2027 and updating them from 31 August 2027. Existing functions can still be invoked indefinitely. Move to dotnet10.
Should I upgrade from .NET 8 to .NET 10 or .NET 11?
To .NET 10, for most apps. Both are supported until 14 November 2028, so 11 adds features but no time, and AWS Lambda has a dotnet10 runtime but none for 11. Skip 9, which ended with 8. Either way you move again before November 2028, to .NET 12, expected in November 2027. The .NET 11 page covers when 11 is worth it.
Can I pay for extended support for .NET 8?
Not from Microsoft: its .NET support policy ends with the maintenance period and describes no paid extension. HeroDevs sells Never-Ending Support (NES) for .NET 6, 8 and 9, patched builds of the runtime, SDK, ASP.NET Core and Entity Framework, with prices on request. On Ubuntu 22.04 and 24.04, Microsoft's Ubuntu guide says Canonical supports the archive's .NET 8 beyond Microsoft's date.

Also on the calendar

End-of-life dates for the rest of your stack.

Dates checked against endoflife.date (MIT). How we check datesReport a wrong dateEvery Microsoft .NET version