Palo Alto Expedition 1 · Version Status
Palo Alto Expedition 1 End of Life Date
Palo Alto Expedition 1 end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (security.paloaltonetworks.com); the source of each date is on the product page.
⚠
Palo Alto Expedition 1 is past end of life. This version no longer receives security patches. 662 days past EOL — migrate to a supported version immediately.
EOL Date
Dec 31, 2024
662 days past EOL
Latest Release
1.2.101
Standard release
Release Date
—
Palo Alto Expedition 1 series
Where these dates come from
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.
Lifecycle detail
It has been past its end-of-life date for 1 year and 10 months.
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 →
Extended Support
Extended Palo Alto Expedition 1 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
All Palo Alto Expedition Versions
| Version | Latest | EOL Date | Status |
|---|
| → 1 |
1.2.101 |
Dec 31, 2024 |
EOL |
What does Palo Alto Expedition 1 end of life mean?
When Palo Alto Expedition 1 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 Palo Alto Expedition 1 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to a supported version or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Palo Alto Expedition 1 reach end of life?
Palo Alto Expedition 1 reached end of life on December 31, 2024. This version is no longer receiving security patches.
Is Palo Alto Expedition 1 still supported?
No. Palo Alto Expedition 1 reached end of life on December 31, 2024 and is no longer receiving security patches.
What should I upgrade to from Palo Alto Expedition 1?
What are the security risks of running Palo Alto Expedition 1 past EOL?
Since Palo Alto Expedition 1 reached end of life, the maintainers no longer issue 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 Palo Alto Expedition should migrate immediately or implement compensating controls.