.NET 6 · Version Status
.NET 6 End of Life Date
.NET 6 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
.NET 6 is past end of life. This version no longer receives security patches. 635 days past EOL — migrate to a supported version immediately.
EOL Date
Nov 12, 2024
635 days past EOL
Latest Release
6.0.36
LTS release
Release Date
Nov 8, 2021
.NET 6 series
Lifecycle detail
.NET 6 was released on November 8, 2021 and support ended on November 12, 2024 — a supported lifespan of 3 years, in line with the 3 years median for .NET LTS releases. It was a long-term support (LTS) release, so it received a longer patch window than the interim releases around it. The last patch it will ever receive is 6.0.36, published November 12, 2024 — on the day support ended. It has been without security patches for 1 year and 9 months. 1 newer .NET release has shipped since.
Attack Surface
30/30 Critical tier
CISA KEV Exposure
0/20 Not in 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 →
Extended Support
Extended .NET 6 support is available
Commercial vendors offer security patches beyond EOL. Right now that coverage spans .NET 6, 8, 9, with 40+ post-EOL CVE fixes documented in vendor release notes. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| Core 1.0 |
1.0.16 |
Jun 27, 2019 |
EOL |
| Core 1.1 |
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 6 end of life mean?
When .NET 6 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 6 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 6 reach end of life?
.NET 6 reached end of life on November 12, 2024. This version is no longer receiving security patches.
Is .NET 6 still supported?
No. .NET 6 reached end of life on November 12, 2024 and is no longer receiving security patches.
What should I upgrade to from .NET 6?
The recommended upgrade from .NET 6 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 6 past EOL?
When .NET 6 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.