// .NET 8 and 9 extended support
.NET 8 and .NET 9 extended support after 10 November 2026
.NET 8 and .NET 9 extended support is a supply of security fixes after Microsoft's support ended on 10 November 2026. OSSeva provides it as signed runtime, ASP.NET Core and EF Core builds and patched container base images for the applications you deploy yourself, on servers, VMs, containers and Kubernetes. Enter your work email and the version you run, and an engineer replies within 1 business day.
- Covered
- .NET 8 and .NET 9 runtime, ASP.NET Core and EF Core, on Windows and Linux
- Critical CVEs (CVSS 9.0 or higher)
- Patched within 48 hours
- High-severity CVEs
- Patched within 7 days
- Support hours
- Assure includes 24/7 reactive support; Operate adds a 15-minute P1 response
- Microsoft support ended
- 10 November 2026 (Microsoft's .NET support policy, checked 11 November 2026)
Dates checked against Microsoft's .NET support policy on 11 November 2026.
Trusted globally by enterprises





What ended on 10 November 2026
Microsoft stopped shipping .NET 8 and .NET 9 updates on 10 November 2026 (dates checked against Microsoft's .NET support policy on 11 November 2026). Microsoft shipped 8.0.34 and 9.0.23 on 10 November 2026, the final releases for both versions, with fixes for 16 CVEs in .NET 8 and 14 in .NET 9. Applications keep running; what stopped is the supply of fixes. Moving between modern .NET versions is easier than it used to be, but estates rarely move as one.
Two versions ended on the same day
.NET 9 is a Standard Term Support release, and Microsoft's 24-month window for it ended on 10 November 2026, the same day as .NET 8. Moving from 8 to 9 buys no time. The only forward move with a support window is .NET 10.
8 to 10 is two majors of breaking changes
The review covers both .NET 9 and .NET 10: System.Text.Json defaults, obsoleted cryptography APIs, and ASP.NET Core hosting and authentication. Applications with WCF client code, System.Web shims or Windows Forms and WPF interop are where a straight upgrade stops being simple.
Self-contained apps each need a rebuild
Framework-dependent apps pick up whatever runtime is installed on the host. Self-contained and single-file apps carry their own runtime, so each one has to be rebuilt and redeployed, and the slowest dependency sets the date.
The platforms moved on the same date
Azure Functions ended support for the in-process model on 10 November 2026, and AWS Lambda deprecated the dotnet8 runtime that day. Function apps and Lambda functions need their own plan alongside the services you run yourself.
The dates that matter
2024-11-12
.NET 6 end of support.
2026-10-13
.NET 8.0.32 and .NET 9.0.21 released on Patch Tuesday.
2026-10-25
.NET 8.0.33 and .NET 9.0.22 released out of band with 3 security fixes each.
2026-11-10
.NET 8.0.34 and .NET 9.0.23, the final Microsoft releases.
2026-11-10
.NET 8 and .NET 9 reached end of support. Azure Functions in-process model support ended, and AWS Lambda deprecated the dotnet8 runtime. OSSeva patches continue for runtimes you deploy.
2027-07-29
AWS Lambda blocks creating new functions on dotnet8.
2027-08-31
AWS Lambda blocks updates to functions on dotnet8.
2028-11-14
.NET 10 end of support.
What OSSeva delivers
Patched .NET 8 runtime builds
CVE fixes for the CLR runtime, ASP.NET Core, Entity Framework Core and the base class libraries after Microsoft's last release. Signed with GPG and Sigstore and delivered as Windows installers or as Docker, apt, yum or binary packages on Linux, for the versions you run.
Patched container base images
Microsoft's 8.0 image tags can still be pulled after the date but stop receiving updates. OSSeva ships patched base images for the .NET SDK and the ASP.NET Core runtime in Alpine and Debian variants: change the FROM line, rebuild and redeploy.
Audit evidence and the path to .NET 10
On Assure, NuGet dependency vulnerability scanning, a SOC 2 and HIPAA attestation package and a .NET 10 migration assessment. On Operate, 24/7 CLR and application health monitoring, a 15-minute P1 response and .NET version migration carried out with your team.
What .NET 8 extended support covers
OSSeva covers the open-source .NET stack: the runtime, ASP.NET Core and Entity Framework Core, delivered as installers for Windows and as signed packages and container images for Linux, on machines you run yourself. .NET 9 is covered on the same terms as .NET 8, because its window closes on the same day. For most teams on .NET 9 the better move is .NET 10, one release away, and extended support is for the applications that cannot make the date.
The matrix shows each version, with Microsoft's dates checked against its .NET support policy on 11 November 2026.
Coverage by .NET version
| .NET 8 (LTS) | .NET 9 (STS) | .NET 10 (LTS) | |
|---|---|---|---|
| Microsoft support end date | 10 November 2026 | 10 November 2026 | 14 November 2028 |
| Final Microsoft release | 8.0.34 (10 November 2026) | 9.0.23 (10 November 2026) | Latest: 10.0.15 (10 November 2026) |
| Runtime and base class libraries | Covered now | Covered now | Covered after 14 November 2028 |
| ASP.NET Core | Covered now | Covered now | Covered after 14 November 2028 |
| Entity Framework Core | Covered now | Covered now | Covered after 14 November 2028 |
| Operating system packaging | Linux: apt and yum packages, binary packages, and SDK and ASP.NET Core runtime container images in Alpine and Debian variants, signed with GPG and Sigstore. Windows: installers. | Same as .NET 8 | Same as .NET 8 |
| Windows hosts | Covered. OSSeva delivers patched .NET builds for Windows as installers. | Same as .NET 8 | Same as .NET 8 |
| Not covered | The managed .NET 8 stacks on Azure App Service, Azure Functions and AWS Lambda. Windows .NET Framework 4.x is a services engagement, not a patched build. | Same as .NET 8 | Same as .NET 8 |
Dates from Microsoft's .NET support policy and release metadata, checked 11 November 2026. Until 14 November 2028, Microsoft ships .NET 10 fixes itself.
How patched runtimes ship and are verified
Every build is signed with GPG and Sigstore, so your repository manager and your pipeline can check the signature before a runtime is promoted. Patched builds install in place of Microsoft's: on Linux you change the package source or the FROM line of a container, and on Windows you run the installer. Nothing is forked and nothing is added, so a patched .NET 8 stays .NET 8.
The commitments below are the ones published on the OSSeva Patch, Assure and Operate pages, and they apply to .NET 8 and .NET 9 now that Microsoft has stopped releasing them.
Patch and response commitments
| Request | Commitment | Tier |
|---|---|---|
| Critical vulnerability (CVSS 9.0 or higher) | Patched within 48 hours | Patch |
| High-severity vulnerability | Patched within 7 days | Patch |
| Everything else | Quarterly batch | Patch |
| Any issue, at any hour | 24/7 reactive support: an OSSeva engineer works it with you | Assure |
| P1 incident | 15-minute response, 24/7 | Operate |
Patch commitments are as published on the OSSeva Patch page. Assure includes 24/7 reactive support. The 15-minute P1 response and proactive 24/7 operations are part of Operate, not Patch.
Which .NET 8 CVEs an extended-support build carries forward
An extended-support build starts from Microsoft's last .NET 8 release, 8.0.34, so it carries every fix below, then adds the fixes for advisories published after 10 November 2026. The table is built from OSSeva's own CVE directory, newest first.
.NET 8 CVEs in the OSSeva CVE directory
| CVE | CVSS | Published | Issue | Fixed in .NET 8 |
|---|---|---|---|---|
| CVE-2026-62898 | 7.5 | 11 Aug 2026 | .NET: use after free in Microsoft QUIC discloses memory | 8.0.30 |
| CVE-2026-47304 | 9.8 | 14 Jul 2026 | .NET: EncryptedXml signature verification flaw allows security feature bypass | 8.0.29 |
| CVE-2026-47303 | 8.8 | 14 Jul 2026 | ASP.NET Core Negotiate authentication: improper parsing allows elevation of privilege | 8.0.29 |
| CVE-2026-47300 | 8.8 | 14 Jul 2026 | ASP.NET Core Negotiate authentication: incorrect validation with LDAP roles allows elevation of privilege | 8.0.29 |
| CVE-2026-50528 | 8.2 | 14 Jul 2026 | .NET SslStream: authorization checks can be bypassed on TLS connections | 8.0.29 |
| CVE-2026-45591 | 7.5 | 9 Jun 2026 | ASP.NET Core SignalR and Blazor Server: deeply nested MessagePack arrays cause denial of service | 8.0.28 |
| CVE-2025-55315 | 9.9 | 14 Oct 2025 | ASP.NET Core Kestrel: HTTP request smuggling allows security feature bypass | 8.0.21 |
| CVE-2024-0057 | 9.8 | 9 Jan 2024 | .NET: X.509 chain building returns an incorrect failure reason | 8.0.1 |
The directory lists .NET CVEs with a CVSS score of 7.0 or higher, matched at NVD to the product, so it is a subset of every .NET advisory. CVSS is NVD's score where NVD has scored the record, otherwise Microsoft's score as the CNA. Fixed-in versions are from Microsoft's advisories.
Which vendors provide extended support for .NET 8 after 10 November 2026?
Microsoft stopped shipping fixes for .NET 8 on 10 November 2026, and its published support policy lists no paid extension. Since that date a fix for a .NET 8 runtime vulnerability has to come from a third-party provider. HeroDevs, TuxCare and OSSeva each offer one. They differ on versions, operating systems, how fixes are delivered and how the contract is priced, and the comparison below sets them side by side using each company's own pages. Where a page does not say, the cell says so. Terms change, so confirm with each provider before you buy.
Compared on 11 November 2026
| HeroDevs NES for .NET | TuxCare ELS for .NET | OSSeva | |
|---|---|---|---|
| Versions listed | .NET 6, 8 and 9 | .NET 1.1, 2.0, 2.2, 6, 8 and 10, varying by Windows edition. .NET 9 is not listed. | .NET 6, 7, 8 and 9 now, .NET 10 after 14 November 2028 |
| Components named | Runtime, SDK, ASP.NET, Entity Framework, WPF, WinForms | SDK, ASP.NET Core Runtime, Desktop Runtime, Runtime | Runtime, ASP.NET Core, Entity Framework Core, base class libraries |
| Operating systems | Windows and Linux, per its .NET 8 announcement of 1 April 2026. The product page does not list them. | Windows only: Windows Server 2012 to 2025, Windows 10 and 11, Nano Server | Windows and Linux. Patched builds for Windows as installers; for Linux as apt and yum packages, Docker images and binaries. |
| Delivery | Not described on the product page | TuxCare Installer (GUI), a PowerShell script, or manual setup files from a tokenised URL. An ELS licence key is required. To update, rerun the installer for the new build. | Windows: installers. Linux: apt, yum, Docker and binary packages, signed with GPG and Sigstore. |
| Response commitment | Security issues prioritised for same-day resolution where possible. SLA on request, no figures published. | No SLA stated on the page | Critical in 48 hours and High in 7 days (Patch). 24/7 reactive support (Assure). 15-minute P1 response (Operate). |
| Pricing basis | Number of users committing code to the repository | Not stated. Contact sales. | Per application runtime environment. Contact us for a quote. |
Sources: herodevs.com/support/dot-net-nes, herodevs.com announcement of .NET 8 NES, docs.tuxcare.com/els-for-runtimes/dotnet, and the OSSeva Patch and .NET pages. Vendor pages checked 11 November 2026.
Upgrade to .NET 10 or extend: how to choose
| Option | What you get | Trade-off |
|---|---|---|
| Move to .NET 10 | Microsoft support until 14 November 2028. | Two majors of breaking changes, and every self-contained app rebuilt. The destination for every application. |
| OSSeva .NET 8 extended support | Signed .NET 8 runtimes, ASP.NET Core, EF Core and container images with backported fixes, on the Patch, Assure and Operate tiers. | Covers runtimes you deploy, not managed platform stacks. Priced per application runtime environment. |
| Other third-party .NET support | HeroDevs lists NES for .NET 6, 8 and 9. TuxCare lists ELS for .NET 1.1, 2.0, 2.2, 6, 8 and 10, on Windows. | Compare coverage by operating system and delivery channel, and whether the rest of your open source stack fits on the same contract. |
| Stay on .NET 8 unpatched | Nothing new. | Runtime advisories published after 10 November stay open, and audits flag an unsupported framework. |
Dates and final releases from the Microsoft .NET support policy and release metadata, checked 11 November 2026, and the Azure Functions runtime versions page and the AWS Lambda runtimes page, checked 9 October 2026. Container tag policy from the dotnet-docker repository. Vendor comparison from HeroDevs and TuxCare pages, 11 November 2026.
What is .NET 8 extended support?
.NET 8 extended support is a supply of security fixes for the .NET 8 runtime after Microsoft stopped shipping them on 10 November 2026. OSSeva provides it as signed .NET 8 runtime, ASP.NET Core and EF Core builds and patched container base images, for applications on servers, VMs, containers and Kubernetes.
Which vendors provide extended support for .NET 8 after 10 November 2026?
Microsoft does not: its support policy ended .NET 8 patches on 10 November 2026 and lists no paid extension. Third-party providers include HeroDevs, TuxCare and OSSeva, and Canonical maintains the .NET 8 packages in Ubuntu 22.04 and 24.04. Compare them on versions, operating systems, delivery and response commitments; the comparison above does that from each company's own pages.
When did .NET 8 support end?
On 10 November 2026, the November Patch Tuesday, as listed in Microsoft's .NET support policy (checked 11 November 2026). .NET 9 ended the same day. Microsoft shipped 8.0.34 and 9.0.23 on 10 November 2026, the final releases for both versions, with fixes for 16 CVEs in .NET 8 and 14 in .NET 9. .NET 10 is the LTS release supported to 14 November 2028. The .NET 8 end-of-life page tracks the dates.
Is .NET 8 still supported?
No, since 10 November 2026: Microsoft ships no further .NET 8 security updates, and the final release is 8.0.34 (10 November 2026). OSSeva's extended support is what keeps .NET 8 applications patched.
What happens to .NET 8 applications after November 10, 2026?
They keep running. What stops is the supply of fixes: any runtime vulnerability published afterwards stays open unless a support provider patches it, and Microsoft's 8.0 container image tags can still be pulled but receive no further updates.
Does Microsoft sell extended support for .NET 8?
Microsoft's published .NET support policy ended patches for .NET 8 on 10 November 2026 and does not list a paid extension. The supported route from Microsoft is .NET 10. Third-party providers, including HeroDevs, TuxCare and OSSeva, offer patched .NET 8 builds for applications that need more time.
Can OSSeva patch .NET 8 on Azure Functions, Azure App Service or AWS Lambda?
Not the built-in stacks. Microsoft and AWS run those runtimes, and no third party can patch them. Where you package the runtime yourself, such as a custom container on App Service or a container image function on Lambda, OSSeva's patched .NET 8 base images can fill that role while the move to .NET 10 runs.
Does it also cover .NET 9, .NET 6 and .NET 7?
Yes. OSSeva patches .NET 6, 7, 8 and 9 today, on long-term and standard-term releases alike. Teams on .NET 9 usually move to .NET 10 sooner, because the jump is one release.
Does it cover .NET Framework 4.x?
OSSeva's patched builds cover .NET (Core and 5 onwards), the open-source cross-platform runtime. Windows .NET Framework 4.x is handled as a professional services engagement, so talk to us about your requirements.
How quickly does OSSeva patch .NET 8 after end of life?
Critical vulnerabilities (CVSS 9.0 or higher) within 48 hours and High within 7 days, as published for the Patch tier. Everything else goes into a quarterly batch. Assure includes 24/7 reactive support, and a 15-minute P1 response is part of Operate.
How is .NET 8 extended support priced?
OSSeva for .NET is priced per application runtime environment, not per deployment. The tier you choose, Patch, Assure or Operate, sets how much of the work OSSeva takes on. Send your email and the version you run for a quote.
Get a quote
Not every application made it to .NET 10 by 10 November.
Discovery call, an inventory of the .NET runtimes you deploy, then a quote per application runtime environment.
Prefer to talk or read more first?