OpenBSD End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all OpenBSD versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2.1 | — | Jun 1, 1997 | May 19, 1998 | 10309 days past EOL | EOL |
| 2.2 | — | Dec 1, 1997 | Dec 1, 1998 | 10113 days past EOL | EOL |
| 2.3 | — | May 19, 1998 | May 19, 1999 | 9944 days past EOL | EOL |
| 2.4 | — | Dec 1, 1998 | Dec 1, 1999 | 9748 days past EOL | EOL |
| 2.5 | — | May 19, 1999 | Jun 15, 2000 | 9551 days past EOL | EOL |
| 2.6 | — | Dec 1, 1999 | Dec 1, 2000 | 9382 days past EOL | EOL |
| 2.7 | — | Jun 15, 2000 | Jun 1, 2001 | 9200 days past EOL | EOL |
| 2.8 | — | Dec 1, 2000 | Dec 1, 2001 | 9017 days past EOL | EOL |
| 2.9 | — | Jun 1, 2001 | May 19, 2002 | 8848 days past EOL | EOL |
| 3.0 | — | Dec 1, 2001 | Nov 1, 2002 | 8682 days past EOL | EOL |
| 3.1 | — | May 19, 2002 | May 1, 2003 | 8501 days past EOL | EOL |
| 3.2 | — | Nov 1, 2002 | Nov 1, 2003 | 8317 days past EOL | EOL |
| 3.3 | — | May 1, 2003 | May 1, 2004 | 8135 days past EOL | EOL |
| 3.4 | — | Nov 1, 2003 | Nov 1, 2004 | 7951 days past EOL | EOL |
| 3.5 | — | May 1, 2004 | May 19, 2005 | 7752 days past EOL | EOL |
| 3.6 | — | Nov 1, 2004 | Nov 1, 2005 | 7586 days past EOL | EOL |
| 3.7 | — | May 19, 2005 | May 1, 2006 | 7405 days past EOL | EOL |
| 3.8 | — | Nov 1, 2005 | Nov 1, 2006 | 7221 days past EOL | EOL |
| 3.9 | — | May 1, 2006 | May 1, 2007 | 7040 days past EOL | EOL |
| 4.0 | — | Nov 1, 2006 | Nov 1, 2007 | 6856 days past EOL | EOL |
| 4.1 | — | May 1, 2007 | May 1, 2008 | 6674 days past EOL | EOL |
| 4.2 | — | Nov 1, 2007 | Nov 1, 2008 | 6490 days past EOL | EOL |
| 4.3 | — | May 1, 2008 | May 1, 2009 | 6309 days past EOL | EOL |
| 4.4 | — | Nov 1, 2008 | Oct 18, 2009 | 6139 days past EOL | EOL |
| 4.5 | — | May 1, 2009 | May 19, 2010 | 5926 days past EOL | EOL |
| 4.6 | — | Oct 18, 2009 | Nov 1, 2010 | 5760 days past EOL | EOL |
| 4.7 | — | May 19, 2010 | May 1, 2011 | 5579 days past EOL | EOL |
| 4.8 | — | Nov 1, 2010 | Nov 1, 2011 | 5395 days past EOL | EOL |
| 4.9 | — | May 1, 2011 | May 1, 2012 | 5213 days past EOL | EOL |
| 5.0 | — | Nov 1, 2011 | Nov 1, 2012 | 5029 days past EOL | EOL |
| 5.1 | — | May 1, 2012 | May 1, 2013 | 4848 days past EOL | EOL |
| 5.2 | — | Nov 1, 2012 | Nov 1, 2013 | 4664 days past EOL | EOL |
| 5.3 | — | May 1, 2013 | May 1, 2014 | 4483 days past EOL | EOL |
| 5.4 | — | Nov 1, 2013 | Nov 1, 2014 | 4299 days past EOL | EOL |
| 5.5 | — | May 1, 2014 | May 1, 2015 | 4118 days past EOL | EOL |
| 5.6 | — | Nov 1, 2014 | Oct 18, 2015 | 3948 days past EOL | EOL |
| 5.7 | — | May 1, 2015 | Mar 29, 2016 | 3785 days past EOL | EOL |
| 5.8 | — | Oct 18, 2015 | Sep 1, 2016 | 3629 days past EOL | EOL |
| 5.9 | — | Mar 29, 2016 | Apr 11, 2017 | 3407 days past EOL | EOL |
| 6.0 | — | Sep 1, 2016 | Oct 9, 2017 | 3226 days past EOL | EOL |
| 6.1 | — | Apr 11, 2017 | Apr 15, 2018 | 3038 days past EOL | EOL |
| 6.2 | — | Oct 9, 2017 | Oct 18, 2018 | 2852 days past EOL | EOL |
| 6.3 | — | Apr 2, 2018 | May 3, 2019 | 2655 days past EOL | EOL |
| 6.4 | — | Oct 18, 2018 | Oct 17, 2019 | 2488 days past EOL | EOL |
| 6.5 | — | Apr 24, 2019 | May 19, 2020 | 2273 days past EOL | EOL |
| 6.6 | — | Oct 17, 2019 | Oct 18, 2020 | 2121 days past EOL | EOL |
| 6.7 | — | May 19, 2020 | May 1, 2021 | 1926 days past EOL | EOL |
| 6.8 | — | Oct 18, 2020 | Oct 14, 2021 | 1760 days past EOL | EOL |
| 6.9 | — | May 1, 2021 | Apr 21, 2022 | 1571 days past EOL | EOL |
| 7.0 | — | Oct 14, 2021 | Oct 20, 2022 | 1389 days past EOL | EOL |
| 7.1 | — | Apr 21, 2022 | Apr 10, 2023 | 1217 days past EOL | EOL |
| 7.2 | — | Oct 20, 2022 | Oct 16, 2023 | 1028 days past EOL | EOL |
| 7.3 | — | Apr 10, 2023 | Apr 5, 2024 | 856 days past EOL | EOL |
| 7.4 | — | Oct 16, 2023 | Oct 8, 2024 | 670 days past EOL | EOL |
| 7.5 | — | Apr 5, 2024 | Apr 28, 2025 | 468 days past EOL | EOL |
| 7.6 | — | Oct 8, 2024 | Oct 22, 2025 | 291 days past EOL | EOL |
| 7.7 | — | Apr 28, 2025 | May 19, 2026 | 82 days past EOL | EOL |
| 7.8 | — | Oct 22, 2025 | Nov 1, 2026 | 84 days remaining | Warning |
| 7.9 | — | May 19, 2026 | Jun 1, 2027 | 296 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/openbsd)
What does OpenBSD end of life mean for your organization?
When a version of OpenBSD reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL OpenBSD should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when OpenBSD reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL OpenBSD versions. This is a bridge, not a permanent solution — plan your migration in parallel.
OpenBSD has 57 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for OpenBSD exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.