.NET 10 · Version Status
.NET 10 End of Life Date
.NET 10 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
✓
.NET 10 is actively supported. EOL date: November 14, 2028.
📅 Get reminded before .NET 10 reaches EOL on November 14, 2028 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Nov 14, 2028
736 days remaining
Latest Release
10.0.13
LTS release
Release Date
Nov 11, 2025
.NET 10 series
Where these dates come from
End of lifeNov 14, 2028Vendor's own page, read by our adapter · builds.dotnet.microsoft.com · checked Nov 3, 2026high · 3 sources agree ReleaseNov 11, 2025Vendor's own page, checked by a person · learn.microsoft.com · checked Sep 17, 2026high · 2 sources agree Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
.NET 10 was released on November 11, 2025 and support is scheduled to end on November 14, 2028 — a planned supported lifespan of 3 years, in line with the 3 years median for .NET LTS releases. It is a long-term support (LTS) release, so it carries a longer patch window than the interim releases around it. Its most recent patch is 10.0.13, published October 13, 2026.
Attack Surface
30/30 Critical tier
CISA KEV Exposure
20/20 Named in CISA KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
| Version | Latest | EOL Date | Status |
|---|
| Core 1.0 LTS |
1.0.16 |
Jun 27, 2019 |
EOL |
| Core 1.1 LTS |
1.1.13 |
Jun 27, 2019 |
EOL |
| Core 2.0 |
2.0.9 |
Oct 1, 2018 |
EOL |
| Core 2.1 LTS |
2.1.30 |
Aug 21, 2021 |
EOL |
| Core 2.2 |
2.2.8 |
Dec 23, 2019 |
EOL |
| Core 3.0 |
3.0.3 |
Mar 3, 2020 |
EOL |
| Core 3.1 LTS |
3.1.32 |
Dec 13, 2022 |
EOL |
| 5 |
5.0.17 |
May 10, 2022 |
EOL |
What does .NET 10 end of life mean?
When .NET 10 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running .NET 10 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to .NET 10 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does .NET 10 reach end of life?
.NET 10 reaches end of life on November 14, 2028. That is 736 days remaining.
Is .NET 10 still supported?
Yes, .NET 10 is currently supported. The EOL date is November 14, 2028.
What should I upgrade to from .NET 10?
The recommended upgrade from .NET 10 is
.NET 10 — the latest actively supported version. Check the
.NET full timeline for all supported versions.
What are the security risks of running .NET 10 past EOL?
When .NET 10 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL .NET should migrate immediately or implement compensating controls.