Complete end-of-life dates, support windows, and security status for all .NETfx versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 3.5-sp1 | — | Nov 19, 2007 | Jan 9, 2029 | 976 days remaining | Active |
| 4.0 | — | Apr 12, 2010 | Jan 12, 2016 | 3770 days past EOL | EOL |
| 4.5 | — | Aug 15, 2012 | Jan 12, 2016 | 3770 days past EOL | EOL |
| 4.5.1 | — | Oct 17, 2013 | Jan 12, 2016 | 3770 days past EOL | EOL |
| 4.5.2 | — | May 5, 2014 | Apr 26, 2022 | 1474 days past EOL | EOL |
| 4.6 | — | Jul 20, 2015 | Apr 26, 2022 | 1474 days past EOL | EOL |
| 4.6.1 | — | Nov 30, 2015 | Apr 26, 2022 | 1474 days past EOL | EOL |
| 4.6.2 | — | Aug 2, 2016 | Jan 12, 2027 | 248 days remaining | Active |
| 4.7 | — | Apr 5, 2017 | Already EOL | Supported | Active |
| 4.7.1 | — | Oct 17, 2017 | Already EOL | Supported | Active |
| 4.7.2 | — | Apr 30, 2018 | Already EOL | Supported | Active |
| 4.8 | — | Apr 18, 2019 | Already EOL | Supported | Active |
| 4.8.1 | — | Aug 9, 2022 | Already EOL | Supported | Active |
When a .NETfx 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 .NETfx 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →