.NET 3.1 · Version Status
.NET 3.1 End of Life Date
.NET 3.1 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
.NET 3.1 is past end of life. This version no longer receives security patches. 1243 days past EOL — migrate to a supported version immediately.
EOL Date
Dec 13, 2022
1243 days past EOL
Latest Release
3.1.32
LTS release
Release Date
Dec 3, 2019
.NET 3.1 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 3.1 end of life mean?
When .NET 3.1 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 3.1 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 3.1 reach end of life?
.NET 3.1 reached end of life on December 13, 2022. This version is no longer receiving security patches.
Is .NET 3.1 still supported?
No. .NET 3.1 reached end of life on December 13, 2022 and is no longer receiving security patches.
What should I upgrade to from .NET 3.1?
The recommended upgrade from .NET 3.1 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 3.1 past EOL?
When .NET 3.1 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.