Palo Alto Expedition End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Palo Alto Expedition versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Every tracked Palo Alto Expedition version is past end of life; the most recent to reach it, 1, did so on December 31, 2024. The full Palo Alto Expedition 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 |
|---|---|---|---|---|---|
| 1 | 1.2.101 | — | Dec 31, 2024 | 617 days past EOL | EOL |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/palo-alto-expedition)
Palo Alto Expedition lifecycle status — the real story
Palo Alto Networks Expedition, the firewall configuration migration tool, is modelled as one line (Expedition 1.x) because the vendor retired the whole product: Palo Alto's security advisory PAN-SA-2025-0001 (published 2025-01-08) states 'Expedition reached its End of Life (EoL) date on December 31, 2024' and 'we do not plan to make any additional updates or security fixes'; the last fixes shipped in 1.2.100 and 1.2.101 before that date, so 1.2.101 is recorded as the final release. The release date of the 1.x line is not published on a page we can read and is left null, never estimated. Vendor statements read 2026-09-09; the End of Life Announcement itself lives on LIVEcommunity behind a bot challenge, so the advisory is the verification route.
KEV context (CISA catalog 2026.09.08, product string 'Expedition' under vendor Palo Alto Networks): CVE-2024-5910 (added 2024-11-07), CVE-2024-9463 and CVE-2024-9465 (added 2024-11-14). Fixes for all three existed before the EoL date; Palo Alto's guidance is that Expedition was a temporary migration tool and should not remain deployed.
The advisory adds that these issues do not affect PAN-OS firewalls, Panorama, Prisma Access or Cloud NGFW; those are tracked on their own pages.
Palo Alto Expedition security intelligence
CISA KEV history: Palo Alto Expedition is named in CISA's Known Exploited Vulnerabilities catalog 3 times, most recently on 2024-11-14. Derived from CISA's live catalog at every build.
What does Palo Alto Expedition end of life mean for your organization?
When a version of Palo Alto Expedition 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 Palo Alto Expedition 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 Palo Alto Expedition 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 Palo Alto Expedition versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Palo Alto Expedition has 1 version 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 Palo Alto Expedition 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."