.NET 10 · Version Status
.NET 10 End of Life Date
.NET 10 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
✓
.NET 10 is actively supported. EOL date: November 14, 2028.
EOL Date
Nov 14, 2028
920 days remaining
Latest Release
10.0.7
LTS release
Release Date
Nov 11, 2025
.NET 10 series
| Version | Latest | EOL Date | Status |
|---|
| 1.0 |
1.0.16 |
Jun 27, 2019 |
EOL |
| 1.1 |
1.1.13 |
Jun 27, 2019 |
EOL |
| 2.0 |
2.0.9 |
Oct 1, 2018 |
EOL |
| 2.1 LTS |
2.1.30 |
Aug 21, 2021 |
EOL |
| 2.2 |
2.2.8 |
Dec 23, 2019 |
EOL |
| 3.0 |
3.0.3 |
Mar 3, 2020 |
EOL |
| 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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running .NET 10 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
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 reached end of life on November 14, 2028. That is 920 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 remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL .NET should migrate immediately or implement compensating controls.