OpenBSD 8.0 · Version Status

OpenBSD 8.0 End of Life Date

OpenBSD 8.0 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.

✓ OpenBSD 8.0 is actively supported. No end-of-life date has been announced yet.
EOL Date
TBD
Supported
Latest Release
—
Standard release
Release Date
Oct 20, 2026
OpenBSD 8.0 series
Where these dates come from
ReleaseOct 20, 2026Vendor's own page (our correction) · openbsd.org · checked Oct 19, 2026medium · 1 source agrees
Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale. How we source dates.
Spotted a date that disagrees with the vendor's own lifecycle page? Report it with the vendor's link → Every correction is published on the accuracy page.
Lifecycle detail

OpenBSD 8.0 was released on October 20, 2026 and has no published end-of-life date yet.

← OpenBSD 7.9 All OpenBSD versions
30 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
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 →
All OpenBSD Versions
VersionLatestEOL DateStatus
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 8.0 end of life mean?

When OpenBSD 8.0 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running OpenBSD 8.0 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to OpenBSD 8.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does OpenBSD 8.0 reach end of life?
OpenBSD 8.0 has no announced end-of-life date yet — it is currently supported, with EOL to be determined.
Is OpenBSD 8.0 still supported?
Yes, OpenBSD 8.0 is currently supported. The EOL date is TBD.
What should I upgrade to from OpenBSD 8.0?
The recommended upgrade from OpenBSD 8.0 is OpenBSD 8.0 — the latest actively supported version. Check the OpenBSD full timeline for all supported versions.
What are the security risks of running OpenBSD 8.0 past EOL?
When OpenBSD 8.0 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL OpenBSD should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →