End of life

.NET 9 end of life: support ended on 10 November 2026

.NET 9 reached end of support on 10 November 2026, the same day as .NET 8. Its final release is 9.0.23, released on 10 November 2026. .NET 9 was a Standard Term Support release, so there is no further Microsoft patch. Move to .NET 10, one major version and supported until 14 November 2028, or keep .NET 9 patched with OSSeva.

Still on .NET 9 after 10 November?

Get extended support or ask for a quote

Only your email is required · An engineer replies within 1 business day · No commitment

End of life
10 November 2026
Released
Nov 2024
Final release
9.0.23 (final, 10 November 2026)
Successor
.NET 10 (LTS, supported to 14 November 2028)

Date published by Microsoft .NET release metadata. We do not publish a lifecycle date we cannot source. Dates checked against Microsoft's .NET support policy and release metadata on 11 November 2026.

Last reviewed

When .NET 8 and .NET 9 support ended

Microsoft supported .NET 8 and .NET 9 until 10 November 2026, the November Patch Tuesday. .NET 8 is a Long Term Support release with three years of support and .NET 9 a Standard Term Support release with two, so the two windows closed on 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 only current release with a longer window. Dates checked against Microsoft's .NET support policy and release metadata on 11 November 2026.

.NET support dates, checked 11 November 2026

VersionTypeReleasedMicrosoft support endedFinal release
.NET 8LTS14 Nov 202310 Nov 20268.0.34 (10 November 2026)
.NET 9STS12 Nov 202410 Nov 20269.0.23 (10 November 2026)
.NET 10LTS11 Nov 2025Supported to 14 Nov 2028Latest: 10.0.15 (10 November 2026)

Source: Microsoft's .NET support policy and release metadata, checked 11 November 2026.

What changed on 10 November 2026

  • Monthly servicing for the .NET 9 runtime, ASP.NET Core 9 and the 9.0 SDKs. Microsoft's metadata lists an end-of-life date of 10 November 2026 for 9.0.
  • Security fixes. Microsoft kept fixing .NET 9 into its last months: its release metadata lists 42 CVEs against 9.0.21, the October 2026 release, and 3 more fixed in 9.0.22 on 25 October 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. Advisories found after 10 November 2026 do not reach 9.0.
  • Microsoft support cases for applications on .NET 9, and rebuilt .NET 9 container images with OS-level fixes.

Upgrade to .NET 10: effort and risks

9 and 8 end together

.NET 8 and .NET 9 both reached end of support on 10 November 2026. A team that moved from 8 to 9 to buy time has no time left from that move, and a team on 9 cannot step back to 8. .NET 10, supported to 14 November 2028, is the only supported target.

One major, not two

From .NET 9 the move to .NET 10 is a single major version, so the breaking-change review covers one release instead of the two an 8 estate faces. Retarget from net9.0 to net10.0, update the NuGet packages that pinned 9.x versions, and rerun the test suite.

Self-contained apps each need a rebuild

Framework-dependent apps pick up whatever runtime the host has installed. Self-contained and single-file deployments carry their own runtime, so every one has to be rebuilt and redeployed to leave 9.0. Count them before you plan the dates.

Stay on .NET 9: extended support and what it covers

OSSeva patches this line

OSSeva ships patched .NET 9 runtimes now, with security fixes backported to the runtime and ASP.NET Core 9 after Microsoft's last release. They are delivered as signed builds through your own repository manager, on the Patch, Assure and Operate tiers: installers for Windows, and packages and container images for Linux.

.NET extended support

If you are still on .NET 9 today

Install the final patch, list what is still on 9.0, and decide per application: upgrade now, isolate, or cover with extended support.

Install 9.0.23, the final .NET 9 release, on every host that stays on .NET 9. Rebuild self-contained and single-file apps too: they carry their own runtime and do not pick up a patch installed on the host.

List what is still on 9.0: the output of dotnet --list-runtimes on every server and build agent, net9.0 target frameworks and SDK pins in source, 9.0 tags in Dockerfiles and running images, and the stack settings of App Service, Azure Functions and AWS Lambda apps.

Upgrade what can move now to .NET 10, supported until 14 November 2028. Start with applications that face the internet or handle regulated data.

Isolate or cover the rest. Remove internet exposure while the upgrade finishes, or keep .NET 9 patched with OSSeva extended support: Critical CVEs patched within 48 hours and High within 7 days. Either way, record the owner, the move date and who accepted the risk, because lifecycle scanners and auditors are likely to flag the runtime as unsupported.

How fast fixes arrive

These are the same commitments published on the OSSeva Patch, Assure and Operate pages, and they apply to .NET 8 and .NET 9 after 10 November 2026.

Patch and response commitments

RequestCommitmentTier
Critical vulnerability (CVSS 9.0 or higher)Patched within 48 hoursPatch
High-severity vulnerabilityPatched within 7 daysPatch
Everything elseQuarterly batchPatch
Any issue, at any hour24/7 reactive support: an OSSeva engineer works it with youAssure
P1 incident15-minute response, 24/7Operate

CVEs already fixed on .NET 9

These are the .NET 9 fixes recorded in OSSeva's CVE directory, newest first. An extended-support build starts from Microsoft's last release and carries every one of them forward, then adds the fixes for advisories published after 10 November 2026.

.NET 9 CVEs in the OSSeva CVE directory

CVECVSSPublishedIssueFixed in .NET 9
CVE-2026-628987.511 Aug 2026.NET: use after free in Microsoft QUIC discloses memory9.0.19
CVE-2026-473049.814 Jul 2026.NET: EncryptedXml signature verification flaw allows security feature bypass9.0.18
CVE-2026-473038.814 Jul 2026ASP.NET Core Negotiate authentication: improper parsing allows elevation of privilege9.0.18
CVE-2026-473008.814 Jul 2026ASP.NET Core Negotiate authentication: incorrect validation with LDAP roles allows elevation of privilege9.0.18
CVE-2026-505288.214 Jul 2026.NET SslStream: authorization checks can be bypassed on TLS connections9.0.18
CVE-2026-455917.59 Jun 2026ASP.NET Core SignalR and Blazor Server: deeply nested MessagePack arrays cause denial of service9.0.17
CVE-2025-553159.914 Oct 2025ASP.NET Core Kestrel: HTTP request smuggling allows security feature bypass9.0.10

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.

Your options, costed honestly

Including the ones that do not involve buying anything from us.

OptionWhat it isEffortCostOur view
Upgrade to .NET 10Retarget, update dependencies, retest, redeploy.One major version: scales with test coverage and self-contained appsEngineering timeThe destination. One major version from 9, supported to November 2028.
OSSeva patched .NET 9Signed .NET 9 runtimes with backported security fixes after 10 November 2026.Install the patched runtime or imageSubscriptionFor applications that could not be retargeted and redeployed before the date.
Wait for .NET 11.NET 11 is at release candidate stage and is a Standard Term Support release.A second upgrade projectEngineering timeDoes not solve 10 November. It is another short-support release.
Stay unpatchedNo Microsoft fixes after 10 November 2026.NoneZero nowHard to defend for anything that faces the internet. ASP.NET Core has had critical advisories, such as CVE-2025-55315.

What your auditor will say

PCI DSS v4 Requirement 6.3.3

Every system component in the cardholder data environment needs its applicable security patches. A runtime, framework or broker with no upstream fix supply needs a patched source or a documented compensating control.

SOC 2 CC7.1

Auditors ask for evidence that production systems receive security fixes. A version past end of life fails that test unless another supplier ships the fixes and can show which CVEs they close.

Compliance library .NET end of life dates for every version

Questions

.NET 9 end of life: common questions

Book a 15-minute call

When did .NET 9 reach end of support?

On 10 November 2026. Microsoft's release metadata lists 10 November 2026 as the end-of-life date for .NET 9, the same date as .NET 8. The date was checked against Microsoft's support policy on 11 November 2026.

How long will .NET 9 be supported?

.NET 9 is a Standard Term Support release, supported for two years from 12 November 2024, so Microsoft support ran until 10 November 2026. .NET 10, the LTS release, is supported until 14 November 2028.

Is .NET 9 an LTS release?

No. .NET 9 is a Standard Term Support release. .NET 8 and .NET 10 are the LTS releases around it.

Is .NET 9 still supported?

No. Microsoft support for .NET 9 ended on 10 November 2026, the same day as .NET 8; the final release is 9.0.23. Microsoft ships no further .NET 9 patches. OSSeva extended support keeps .NET 9 patched.

Should I upgrade from .NET 9 to .NET 10?

Yes. .NET 10 is the LTS release and is supported to 14 November 2028. .NET 11 is a Standard Term Support release, so it gives a shorter window than .NET 10.

What are the best options for .NET 9 applications that need CVE coverage past end of support?

Move to .NET 10, one major version from .NET 9, and put a third-party patch source under any application that cannot make the date. OSSeva backports security fixes to .NET 9 and .NET 8 as signed builds for Windows and Linux. Staying unpatched needs a documented compensating control.

Can I get security patches for .NET 9 after November 2026?

Not from Microsoft. OSSeva delivers .NET 9 security fixes on the Patch, Assure and Operate tiers. Critical vulnerabilities (CVSS 9.0 or higher) are patched within 48 hours and High within 7 days.

Get a quote

Still running .NET 9?

Tell us the versions and the estate size. We will tell you honestly whether to upgrade or to buy cover — and we say 'upgrade' more often than you would expect.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call