Palo Alto PAN-OS vulnerabilities: known CVEs & security history
Palo Alto Networks · Network / Security · 212 tracked CVEs · 14 actively exploited · updated June 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Palo Alto PAN-OS release lines — 212 in total, with 14 actively exploited in the wild. A CVE here doesn't mean your version is affected — check Palo Alto PAN-OS's current status and the safe version to run.
Known Palo Alto PAN-OS CVEs
Actively-exploited and most-severe first. Showing the top 80 of 212. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2024-3400⚡ exploited | critical | 10 | 100% | 2024 |
| CVE-2020-2021⚡ exploited | critical | 10 | 4% | 2020 |
| CVE-2026-0300⚡ exploited | critical | 9.8 | 32% | 2026 |
| CVE-2024-0012⚡ exploited | critical | 9.8 | 100% | 2024 |
| CVE-2017-15944⚡ exploited | critical | 9.8 | 98% | 2017 |
| CVE-2026-0257⚡ exploited | critical | 9.1 | 19% | 2026 |
| CVE-2025-0108⚡ exploited | critical | 9.1 | 98% | 2025 |
| CVE-2022-0028⚡ exploited | high | 8.6 | 2% | 2022 |
| CVE-2019-1579⚡ exploited | high | 8.1 | 39% | 2019 |
| CVE-2018-14634⚡ exploited | high | 7.8 | 15% | 2018 |
| CVE-2024-3393⚡ exploited | high | 7.5 | 27% | 2024 |
| CVE-2024-9474⚡ exploited | high | 7.2 | 95% | 2024 |
| CVE-2016-5195⚡ exploited | high | 7 | 84% | 2016 |
| CVE-2025-0111⚡ exploited | medium | 6.5 | 2% | 2025 |
| CVE-2019-17440 | critical | 10 | 2% | 2019 |
| CVE-2021-3064 | critical | 9.8 | 19% | 2021 |
| CVE-2020-2040 | critical | 9.8 | 4% | 2020 |
| CVE-2019-1581 | critical | 9.8 | 3% | 2019 |
| CVE-2019-1580 | critical | 9.8 | 3% | 2019 |
| CVE-2017-15940 | critical | 9.8 | 5% | 2017 |
| CVE-2017-9458 | critical | 9.8 | 2% | 2017 |
| CVE-2017-8390 | critical | 9.8 | 6% | 2017 |
| CVE-2017-7945 | critical | 9.8 | 2% | 2017 |
| CVE-2016-9150 | critical | 9.8 | 35% | 2016 |
| CVE-2016-3657 | critical | 9.8 | 5% | 2016 |
| CVE-2016-3655 | critical | 9.8 | 3% | 2016 |
| CVE-2020-2018 | critical | 9 | 1% | 2020 |
| CVE-2012-6603 | high | 10 | 4% | 2013 |
| CVE-2012-6601 | high | 10 | 4% | 2013 |
| CVE-2012-6593 | high | 10 | 4% | 2013 |
| CVE-2012-6592 | high | 10 | 4% | 2013 |
| CVE-2012-6605 | high | 9 | 3% | 2013 |
| CVE-2012-6604 | high | 9 | 3% | 2013 |
| CVE-2012-6602 | high | 9 | 3% | 2013 |
| CVE-2012-6600 | high | 9 | 3% | 2013 |
| CVE-2012-6599 | high | 9 | 3% | 2013 |
| CVE-2012-6598 | high | 9 | 3% | 2013 |
| CVE-2012-6595 | high | 9 | 3% | 2013 |
| CVE-2012-6594 | high | 9 | 3% | 2013 |
| CVE-2012-6591 | high | 9 | 3% | 2013 |
| CVE-2023-6790 | high | 8.8 | 1% | 2023 |
| CVE-2021-3058 | high | 8.8 | 2% | 2021 |
| CVE-2021-3056 | high | 8.8 | 1% | 2021 |
| CVE-2021-3050 | high | 8.8 | 2% | 2021 |
| CVE-2020-2036 | high | 8.8 | 24% | 2020 |
| CVE-2020-2017 | high | 8.8 | 1% | 2020 |
| CVE-2020-2015 | high | 8.8 | 2% | 2020 |
| CVE-2020-2014 | high | 8.8 | 3% | 2020 |
| CVE-2019-1576 | high | 8.8 | 2% | 2019 |
| CVE-2019-1575 | high | 8.8 | 2% | 2019 |
| CVE-2016-4971 | high | 8.8 | 46% | 2016 |
| CVE-2020-2013 | high | 8.3 | 1% | 2020 |
| CVE-2020-2050 | high | 8.2 | 1% | 2020 |
| CVE-2022-0030 | high | 8.1 | 1% | 2022 |
| CVE-2021-3062 | high | 8.1 | 1% | 2021 |
| CVE-2021-3060 | high | 8.1 | 34% | 2021 |
| CVE-2021-3059 | high | 8.1 | 2% | 2021 |
| CVE-2020-2034 | high | 8.1 | 6% | 2020 |
| CVE-2020-2002 | high | 8.1 | 1% | 2020 |
| CVE-2020-2001 | high | 8.1 | 1% | 2020 |
| CVE-2020-1992 | high | 8.1 | 3% | 2020 |
| CVE-2020-1979 | high | 8.1 | 1% | 2020 |
| CVE-2021-3052 | high | 8 | 1% | 2021 |
| CVE-2020-1980 | high | 7.8 | 1% | 2020 |
| CVE-2019-17437 | high | 7.8 | 0% | 2019 |
| CVE-2015-6531 | high | 7.8 | 3% | 2017 |
| CVE-2017-7218 | high | 7.8 | 1% | 2017 |
| CVE-2016-9151 | high | 7.8 | 1% | 2016 |
| CVE-2016-1712 | high | 7.8 | 0% | 2016 |
| CVE-2026-0227 | high | 7.5 | 1% | 2026 |
| CVE-2025-0130 | high | 7.5 | 0% | 2025 |
| CVE-2025-0114 | high | 7.5 | 0% | 2025 |
| CVE-2024-2551 | high | 7.5 | 0% | 2024 |
| CVE-2024-2550 | high | 7.5 | 1% | 2024 |
| CVE-2024-9468 | high | 7.5 | 0% | 2024 |
| CVE-2024-3385 | high | 7.5 | 1% | 2024 |
| CVE-2024-3384 | high | 7.5 | 1% | 2024 |
| CVE-2024-3382 | high | 7.5 | 1% | 2024 |
| CVE-2021-3063 | high | 7.5 | 1% | 2021 |
| CVE-2021-3053 | high | 7.5 | 1% | 2021 |
132 older / lower-severity CVEs not shown — see Palo Alto PAN-OS's full record.
Is my Palo Alto PAN-OS version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your Palo Alto PAN-OS version → · Monitor Palo Alto PAN-OS for new CVEs →
Palo Alto PAN-OS vulnerabilities — frequently asked
How many known vulnerabilities does Palo Alto PAN-OS have?
IsItPatched tracks 212 CVEs for Palo Alto PAN-OS, 14 of which are actively exploited (CISA KEV). 20 are critical-severity and 94 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Palo Alto PAN-OS have any actively-exploited vulnerabilities?
Yes — 14 Palo Alto PAN-OS CVEs are in CISA's Known Exploited Vulnerabilities catalog, meaning they are confirmed exploited in the wild (5 linked to ransomware). Patch these as a priority.
What is the most severe Palo Alto PAN-OS vulnerability?
Among tracked issues, CVE-2024-3400 (CRITICAL, CVSS 10), which is actively exploited, ranks highest — a Improper input validation weakness.
Is Palo Alto PAN-OS safe to use?
It depends on the version. The latest supported Palo Alto PAN-OS release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Palo Alto PAN-OS security status · Palo Alto PAN-OS end-of-life · actively-exploited CVEs. Always verify against Palo Alto Networks's advisories — see our disclaimer.