PAN-OS End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all PAN-OS 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 |
|---|---|---|---|---|---|
| 1.3 | — | Nov 15, 2007 | Nov 20, 2008 | 6471 days past EOL | EOL |
| 2.0 | — | May 20, 2008 | May 20, 2009 | 6290 days past EOL | EOL |
| 2.1 | — | Jan 5, 2009 | Jan 5, 2012 | 5330 days past EOL | EOL |
| 3.0 | — | Jun 17, 2009 | Dec 17, 2010 | 5714 days past EOL | EOL |
| 3.1 | — | Mar 15, 2010 | Jun 30, 2013 | 4788 days past EOL | EOL |
| 4.0 | — | Feb 22, 2011 | Dec 31, 2014 | 4239 days past EOL | EOL |
| 4.1 | — | Oct 31, 2011 | Apr 30, 2015 | 4119 days past EOL | EOL |
| 5.0 | — | Nov 13, 2012 | Nov 13, 2016 | 3556 days past EOL | EOL |
| 5.1 | — | May 9, 2013 | May 9, 2017 | 3379 days past EOL | EOL |
| 6.0 | 6.0.15 | Jan 19, 2014 | Mar 19, 2017 | 3430 days past EOL | EOL |
| 6.1 | 6.1.22 | Oct 25, 2014 | Oct 25, 2018 | 2845 days past EOL | EOL |
| 7.0 | 7.0.19 | Jun 4, 2015 | Dec 4, 2017 | 3170 days past EOL | EOL |
| 7.1 | 7.1.26 | Mar 29, 2016 | Jun 30, 2020 | 2231 days past EOL | EOL |
| 8.0 | 8.0.20 | Jan 29, 2017 | Oct 31, 2019 | 2474 days past EOL | EOL |
| 8.1 | 8.1.24 | Mar 1, 2018 | Mar 1, 2022 | 1622 days past EOL | EOL |
| 9.0 | 9.0.17-h5 | Feb 6, 2019 | Mar 1, 2022 | 1622 days past EOL | EOL |
| 9.0-XFR (VM-Series only) | 9.0-XFR (VM-Series only) | Sep 19, 2019 | Sep 19, 2020 | 2150 days past EOL | EOL |
| 9.1 | 9.1.19 | Dec 13, 2019 | Jun 30, 2024 | 770 days past EOL | EOL |
| 10.0 | 10.0.12-h6 | Jul 16, 2020 | Jul 16, 2022 | 1485 days past EOL | EOL |
| 10.1 | 10.1.14-h20 | May 31, 2021 | Dec 1, 2024 | 616 days past EOL | EOL |
| 10.2 | 10.2.18-h9 | Feb 27, 2022 | Aug 27, 2025 | 347 days past EOL | EOL |
| 11.0 | 11.0.6-h1 | Nov 17, 2022 | Nov 17, 2024 | 630 days past EOL | EOL |
| 11.1 | 11.1.16 | Nov 3, 2023 | May 3, 2027 | 267 days remaining | Active |
| 11.2 | 11.2.13 | May 2, 2024 | May 2, 2027 | 266 days remaining | Active |
| 12.1 | 12.1.8 | Aug 28, 2025 | Aug 28, 2028 | 750 days remaining | Active |
| 12.2 | 12.2.2 | Jul 30, 2026 | Jul 30, 2029 | 1086 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/panos)
What does PAN-OS end of life mean for your organization?
When a version of PAN-OS 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 PAN-OS 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 PAN-OS 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 PAN-OS versions. This is a bridge, not a permanent solution — plan your migration in parallel.
PAN-OS has 22 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for PAN-OS 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.