.NETfx 3.5-sp1 · Version Status
.NETfx 3.5-sp1 End of Life Date
.NETfx 3.5-sp1 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
✓
.NETfx 3.5-sp1 is actively supported. EOL date: January 9, 2029.
EOL Date
Jan 9, 2029
976 days remaining
Latest Release
—
Standard release
Release Date
Nov 19, 2007
.NETfx 3.5-sp1 series
| 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 |
Active |
What does .NETfx 3.5-sp1 end of life mean?
When .NETfx 3.5-sp1 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 .NETfx 3.5-sp1 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to .NETfx 4.8.1 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does .NETfx 3.5-sp1 reach end of life?
.NETfx 3.5-sp1 reached end of life on January 9, 2029. That is 976 days remaining.
Is .NETfx 3.5-sp1 still supported?
Yes, .NETfx 3.5-sp1 is currently supported. The EOL date is January 9, 2029.
What should I upgrade to from .NETfx 3.5-sp1?
The recommended upgrade from .NETfx 3.5-sp1 is
.NETfx 4.8.1 — the latest actively supported version. Check the
.NETfx full timeline for all supported versions.
What are the security risks of running .NETfx 3.5-sp1 past EOL?
When .NETfx 3.5-sp1 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 .NETfx should migrate immediately or implement compensating controls.