OPNsense End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all OPNsense versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
OPNsense 26.7 is supported, with no end-of-life or end-of-support date announced yet. 23 of 24 tracked OPNsense versions are past end of life; the most recent to reach it, 26.1, did so on July 15, 2026. The full OPNsense lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 15.1 | 15.1.12 | Jan 2, 2015 | Jul 2, 2015 | 4101 days past EOL | EOL |
| 15.7 | 15.7.25 | Jul 2, 2015 | Jan 28, 2016 | 3891 days past EOL | EOL |
| 16.1 | 16.1.20 | Jan 28, 2016 | Jul 26, 2016 | 3711 days past EOL | EOL |
| 16.7 | 16.7.14 | Jul 26, 2016 | Jan 27, 2017 | 3526 days past EOL | EOL |
| 17.1 | 17.1.11 | Jan 27, 2017 | Jul 26, 2017 | 3346 days past EOL | EOL |
| 17.7 | 17.7.12 | Jul 26, 2017 | Jan 26, 2018 | 3162 days past EOL | EOL |
| 18.1 | 18.1.13 | Jan 26, 2018 | Jul 29, 2018 | 2978 days past EOL | EOL |
| 18.7 | 18.7.10 | Jul 29, 2018 | Jan 28, 2019 | 2795 days past EOL | EOL |
| 19.1 | 19.1.10 | Jan 28, 2019 | Jul 15, 2019 | 2627 days past EOL | EOL |
| 19.7 | 19.7.10 | Jul 15, 2019 | Jan 29, 2020 | 2429 days past EOL | EOL |
| 20.1 | 20.1.9 | Jan 29, 2020 | Jul 28, 2020 | 2248 days past EOL | EOL |
| 20.7 | 20.7.8 | Jul 28, 2020 | Jan 26, 2021 | 2066 days past EOL | EOL |
| 21.1 | 21.1.9 | Jan 26, 2021 | Jul 23, 2021 | 1888 days past EOL | EOL |
| 21.7 | 21.7.8 | Jul 23, 2021 | Jan 25, 2022 | 1702 days past EOL | EOL |
| 22.1 | 22.1.10 | Jan 25, 2022 | Jul 25, 2022 | 1521 days past EOL | EOL |
| 22.7 | 22.7.11 | Jul 25, 2022 | Jan 25, 2023 | 1337 days past EOL | EOL |
| 23.1 | 23.1.11 | Jan 25, 2023 | Jul 28, 2023 | 1153 days past EOL | EOL |
| 23.7 | 23.7.12 | Jul 28, 2023 | Jan 26, 2024 | 971 days past EOL | EOL |
| 24.1 | 24.1.10 | Jan 26, 2024 | Jul 25, 2024 | 790 days past EOL | EOL |
| 24.7 | 24.7.12 | Jul 23, 2024 | Jan 28, 2025 | 603 days past EOL | EOL |
| 25.1 | 25.1.12 | Jan 28, 2025 | Jul 23, 2025 | 427 days past EOL | EOL |
| 25.7 | 25.7.11 | Jul 22, 2025 | Jan 28, 2026 | 238 days past EOL | EOL |
| 26.1 | 26.1.11 | Jan 28, 2026 | Jul 15, 2026 | 70 days past EOL | EOL |
| 26.7 | 26.7.4 | Jul 15, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/opnsense)
OPNsense release and support pattern
Across the 24 release lines with a published release date, OPNsense has shipped a new line roughly every 6 months (median interval). A line typically stays supported for about 6 months from its release to its end-of-life date (measured on the 23 lines with both dates published).
Of the 24 release lines tracked, 23 are past end of life and 1 is still within support. The newest line, 26.7, was released July 15, 2026. No end-of-life date is currently published for the 1 supported line.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does OPNsense end of life mean for your organization?
When a version of OPNsense 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: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL OPNsense 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 OPNsense 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.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL OPNsense versions. This is a bridge, not a permanent solution — plan your migration in parallel.
OPNsense has 23 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for OPNsense is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."