.NET Framework 4.6 · Version Status
.NET Framework 4.6 End of Life Date
.NET Framework 4.6 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
.NET Framework 4.6 is past end of life. This version no longer receives security patches. 1573 days past EOL — migrate to a supported version immediately.
EOL Date
Apr 26, 2022
1573 days past EOL
Latest Release
—
Standard release
Release Date
Jul 20, 2015
.NET Framework 4.6 series
Lifecycle detail
.NET Framework 4.6 was released on July 20, 2015 and support ended on April 26, 2022 — a supported lifespan of 6 years and 9 months, in line with the 6 years and 9 months median for .NET Framework releases. It has been without security patches for 4 years and 4 months. 1 newer .NET Framework release has shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
20/20 Named in CISA 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 Framework 4.6 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
All .NET Framework Versions
| Version | Latest | EOL Date | Status |
|---|
| 3.5 SP1 |
— |
Jan 9, 2029 |
Active |
| 4.0 |
— |
Jan 12, 2016 |
EOL |
| 4.5 |
— |
Jan 12, 2016 |
EOL |
| 4.5.1 |
— |
Jan 12, 2016 |
EOL |
| 4.5.2 |
— |
Apr 26, 2022 |
EOL |
| → 4.6 |
— |
Apr 26, 2022 |
EOL |
| 4.6.1 |
— |
Apr 26, 2022 |
EOL |
| 4.6.2 |
— |
Jan 12, 2027 |
Warning |
What does .NET Framework 4.6 end of life mean?
When .NET Framework 4.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 Framework 4.6 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to .NET Framework 4.8.1 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does .NET Framework 4.6 reach end of life?
.NET Framework 4.6 reached end of life on April 26, 2022. This version is no longer receiving security patches.
Is .NET Framework 4.6 still supported?
No. .NET Framework 4.6 reached end of life on April 26, 2022 and is no longer receiving security patches.
What should I upgrade to from .NET Framework 4.6?
The recommended upgrade from .NET Framework 4.6 is
.NET Framework 4.8.1 — the latest actively supported version. Check the
.NET Framework full timeline for all supported versions.
What are the security risks of running .NET Framework 4.6 past EOL?
When .NET Framework 4.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 Framework should migrate immediately or implement compensating controls.