Netbsd 4 · Version Status
Netbsd 4 End of Life Date
Netbsd 4 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
✓
Netbsd 4 is actively supported. EOL date: Supported indefinitely.
EOL Date
Supported indefinitely
Supported
Latest Release
4.0.1
Standard release
Release Date
Dec 19, 2007
Netbsd 4 series
| Version | Latest | EOL Date | Status |
|---|
| 1 |
1.6.2 |
May 17, 2006 |
EOL |
| 2 |
2.1 |
Aug 21, 2008 |
EOL |
| 3 |
3.1 |
May 30, 2009 |
EOL |
| → 4 |
4.0.1 |
Supported |
Active |
| 5 |
5.2.3 |
Nov 11, 2015 |
EOL |
| 6 |
6.1.5 |
Aug 23, 2018 |
EOL |
| 7 |
7.2 |
Jun 30, 2020 |
EOL |
| 8 |
8.3 |
May 4, 2024 |
EOL |
What does Netbsd 4 end of life mean?
When Netbsd 4 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 Netbsd 4 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Netbsd 10 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Netbsd 4 reach end of life?
Netbsd 4 has no scheduled end-of-life date and is supported indefinitely.
Is Netbsd 4 still supported?
Yes, Netbsd 4 is currently supported. The EOL date is Supported indefinitely.
What should I upgrade to from Netbsd 4?
The recommended upgrade from Netbsd 4 is
Netbsd 10 — the latest actively supported version. Check the
Netbsd full timeline for all supported versions.
What are the security risks of running Netbsd 4 past EOL?
When Netbsd 4 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 Netbsd should migrate immediately or implement compensating controls.