OpenBSD 7.8 · Version Status
OpenBSD 7.8 End of Life Date
OpenBSD 7.8 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚡
OpenBSD 7.8 reaches end of life on November 1, 2026. Plan your migration now — 176 days remaining.
EOL Date
Nov 1, 2026
176 days remaining
Latest Release
—
Standard release
Release Date
Oct 22, 2025
OpenBSD 7.8 series
| Version | Latest | EOL Date | Status |
|---|
| 2.1 |
— |
May 19, 1998 |
EOL |
| 2.2 |
— |
Dec 1, 1998 |
EOL |
| 2.3 |
— |
May 19, 1999 |
EOL |
| 2.4 |
— |
Dec 1, 1999 |
EOL |
| 2.5 |
— |
Jun 15, 2000 |
EOL |
| 2.6 |
— |
Dec 1, 2000 |
EOL |
| 2.7 |
— |
Jun 1, 2001 |
EOL |
| 2.8 |
— |
Dec 1, 2001 |
EOL |
What does OpenBSD 7.8 end of life mean?
When OpenBSD 7.8 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 OpenBSD 7.8 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to a supported version or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does OpenBSD 7.8 reach end of life?
OpenBSD 7.8 reached end of life on November 1, 2026. That is 176 days remaining.
Is OpenBSD 7.8 still supported?
OpenBSD 7.8 is still supported but approaching end of life on November 1, 2026. Begin planning your migration now.
What should I upgrade to from OpenBSD 7.8?
What are the security risks of running OpenBSD 7.8 past EOL?
When OpenBSD 7.8 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 OpenBSD should migrate immediately or implement compensating controls.