// .NET 8 extended support
.NET 8 support after 10 November 2026.
Patched runtimes, VEX attestations and 24/7 operations.
Microsoft stops shipping fixes for .NET 8 LTS and .NET 9 STS on 10 November 2026. From that date OSSeva delivers patched .NET 8 runtime and ASP.NET Core builds, VEX attestations that answer scanner findings, and 24/7 operations for the applications that are still on it. Your teams move to .NET 10 on their own release plan, not Microsoft's calendar.
Trusted globally by enterprises
Why some .NET 8 applications will still be running in December
Moving between modern .NET versions is easier than it used to be, but estates rarely move as one.
Two versions leave support at once
Teams that moved to .NET 9 to get ahead now share the same deadline as teams that stayed on 8, so the whole estate converges on one migration window.
Dependencies set the pace
Third-party packages, internal libraries and vendor SDKs have to support .NET 10 before your applications can. The slowest dependency sets the date.
Regulated release cycles
Applications with validated or certified releases, common in healthcare and finance, cannot retarget a runtime in a few weeks without re-running their assurance process.
The dates that matter
2024-11-12
.NET 6 end of support.
2025-11-11
.NET 10 (LTS) released.
2026-11-10
.NET 8 (LTS) and .NET 9 (STS) end of support. No further security patches from Microsoft. OSSeva coverage continues.
2028-11-14
.NET 10 end of support.
What OSSeva delivers
Patched .NET 8 runtime builds
Security fixes backported to the .NET 8 runtime, ASP.NET Core and the base class libraries after Microsoft's last release, delivered as drop-in builds for the versions you run.
VEX attestations and audit evidence
When a scanner flags a .NET 8 CVE, you get a VEX statement saying whether it is fixed, not present or not reachable in your build, plus written evidence that the runtime is under security support for PCI DSS, SOC 2 and customer questionnaires.
24/7 operations and the path to .NET 10
Round-the-clock monitoring and incident response for .NET 8 workloads on the Operate tier, and a dependency assessment that shows which packages block .NET 10 and the order to move applications in.
Your options, compared
| Option | What you get | Trade-off |
|---|---|---|
| Move to .NET 10 before 10 November | Microsoft support until 14 November 2028 | Every application and dependency has to be ready at once. |
| OSSeva .NET 8 extended support | Patched builds, VEX attestations and 24/7 operations for .NET 8 or 9 after the date | A subscription while applications migrate. |
| Stay unpatched | Nothing | New runtime advisories stay open, and audits flag an unsupported framework. |
Dates from the Microsoft .NET and .NET Core support policy.
Frequently asked questions
What does OSSeva provide for .NET 8 after 10 November 2026?
Patched .NET 8 runtime and ASP.NET Core builds with security fixes backported after Microsoft's last release, VEX attestations for scanner findings, and 24/7 operations on the Operate tier.
Does Microsoft sell extended support for .NET 8?
Microsoft's published .NET support policy ends patches for .NET 8 and .NET 9 on 10 November 2026 and does not list a paid extension. The supported route from Microsoft is .NET 10. Third-party extended support covers applications that need more time.
What are the options for .NET 8 applications that need CVE coverage past end of support?
Move to .NET 10, which is supported until 14 November 2028, or keep running .NET 8 with third-party extended security support while you migrate. OSSeva provides that coverage for the runtime and ASP.NET Core.
Will .NET 8 applications stop working after November 2026?
No. They keep running. They stop receiving security fixes from Microsoft, so any runtime vulnerability published afterwards stays open unless a support provider patches it.
Does extended support also cover .NET 9?
.NET 9 ends on the same day as .NET 8, and OSSeva covers both. Most teams on .NET 9 move to .NET 10 sooner, because the jump is one release.
Not every application will reach .NET 10 by 10 November.
Discovery call, estate assessment, proposal. Coverage can start before 10 November.