.NET · Lifecycle Status

.NET End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all .NET versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

.NET 8.0.26 is actively supported. Next EOL: version 9 on November 10, 2026.
Latest Active
8.0.26
8 series
Next EOL
9
Nov 10, 2026
Active Versions
3
of 13 total
EOL Versions
10
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 20172018201920202021202220232024202520262027202820291.01.12.02.12.23.03.15678910TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
1.0 1.0.16 Jun 27, 2016 Jun 27, 2019 2508 days past EOL EOL
1.1 1.1.13 Nov 16, 2016 Jun 27, 2019 2508 days past EOL EOL
2.0 2.0.9 Aug 14, 2017 Oct 1, 2018 2777 days past EOL EOL
2.1 LTS 2.1.30 May 30, 2018 Aug 21, 2021 1722 days past EOL EOL
2.2 2.2.8 Dec 4, 2018 Dec 23, 2019 2329 days past EOL EOL
3.0 3.0.3 Sep 23, 2019 Mar 3, 2020 2258 days past EOL EOL
3.1 LTS 3.1.32 Dec 3, 2019 Dec 13, 2022 1243 days past EOL EOL
5 5.0.17 Nov 10, 2020 May 10, 2022 1460 days past EOL EOL
6 LTS 6.0.36 Nov 8, 2021 Nov 12, 2024 543 days past EOL EOL
7 7.0.20 Nov 8, 2022 May 14, 2024 725 days past EOL EOL
8 LTS 8.0.26 Nov 14, 2023 Nov 10, 2026 185 days remaining Active
9 9.0.15 Nov 12, 2024 Nov 10, 2026 185 days remaining Active
10 LTS 10.0.7 Nov 11, 2025 Nov 14, 2028 920 days remaining Active

What does .NET end of life mean for your organization?

When a .NET version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.

Organizations running EOL .NET should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Check your full stack for EOL risk

Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.

Open Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for .NET?
The next .NET version reaching EOL is 9 on November 10, 2026. See the full table above for all version EOL dates.
What is the latest supported version of .NET?
The latest active version of .NET is 8.0.26. Always verify against the table above as support windows can change.
What happens when .NET reaches end of life?
When .NET reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of .NET?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL .NET versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →