CVE-2026-0300

CRITICALPre-NVD 9.39.8
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than the CVSS score beside it.

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-05-06), indicating real-world exploitation has been confirmed by US federal agencies. The CNA's CVSS baseline 9.3 retained for reference (NVD's own analysis pending). Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this weekExploited in the wild
9.8EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low mission impact
CISA-KEV: ExploitedEPSS PROB: 32%CVSS: 9.3Exploit: Public PoCExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (Palo Alto Networks, Inc.) lists Palo Alto Networks PAN-OS versions 12.1.0 up to but not including 12.1.7, 11.2.0 up to but not including 11.2.12, 11.1.0 up to but not including 11.1.15 and 10.2.0 up to but not including 10.2.18-h6 as affected. No release containing a fix is confirmed on record.

A buffer overflow vulnerability in the User-ID™ Authentication Portal (aka Captive Portal) service of Palo Alto Networks PAN-OS software allows an unauthenticated attacker to execute arbitrary code with root privileges on the PA-Series and VM-Series firewalls by sending specially crafted packets.

The risk of this issue is greatly reduced if you secure access to the User-ID™ Authentication Portal per the best practice guidelines https://knowledgebase.paloaltonetworks.com/KCSArticleDetail by restricting access to only trusted internal IP addresses.

Prisma Access, Cloud NGFW and Panorama appliances are not impacted by this vulnerability.

CVSS v3
9.3
EG Score
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Attend at low mission impact; Act at medium or high.
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation sooner than your standard update timelines at low mission impact and as soon as possible at medium or high, and watch the vendor's advisory for the fix.
EPSS PROB
32%
EPSS %ILE
98th
KEV
⚠ Exploited

SSVC (CISA's decision table, applied by EchelonGraph)Attend at low mission impact; Act at medium or high.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation sooner than your standard update timelines at low mission impact and as soon as possible at medium or high, and watch the vendor's advisory for the fix.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.

In CISA KEV yes (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Until the vendor releases an official fix, the following workaround should be implemented: - Restrict User-ID Authentication Portal access to only trusted zones. - Disable User-ID Authentication Portal if not required. 5/13/2026: Palo Alto has released a variety of patches. If these are relevant to your environment, please apply the designated patch.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://security.paloaltonetworks.com/CVE-2026-0300 · https://nvd.nist.gov/vuln/detail/CVE-2026-0300

Published

May 6, 2026

Last Modified

July 14, 2026

Advisory Details (2)

Auto-updated Oct 8, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). No fix on record yet.
Web page

CVE-2026-0300 PAN-OS: Unauthenticated user initiated Buffer Overflow Vulnerability in User-ID™ Authentication Portal

https://security.paloaltonetworks.com/CVE-2026-0300
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-0300

Vendor Advisories for CVE-2026-0300(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 47× in last 7d / 231× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 1,102 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 1,002 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 04:34 UTCEG score recompute
  2. 2026-10-14 04:34 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-13 16:33 UTCEPSS rescoreEPSS 32% · 98th percentile
  4. 2026-10-13 06:33 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-12 16:42 UTCEG score recompute
  6. 2026-10-12 08:31 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-12 04:34 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-12 00:38 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-11 20:43 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-11 20:17 UTCEG score recompute
  11. 2026-10-11 16:47 UTCEG score recompute
  12. 2026-10-11 16:47 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-11 15:03 UTCEG score recompute
  14. 2026-10-11 13:47 UTCEPSS rescoreEPSS 32% · 98th percentile
  15. 2026-10-11 12:52 UTCEG score recompute
  16. 2026-10-11 12:52 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-11 08:56 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-11 04:59 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-11 01:03 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-10 21:08 UTCEG score recompute
  21. 2026-10-10 21:07 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-10 19:59 UTCEPSS rescoreEPSS 32% · 98th percentile
  23. 2026-10-10 17:12 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-10 13:17 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-10 09:21 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 75 more
  1. 2026-10-10 05:27 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-10-10 01:32 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-09 21:35 UTCEG score recompute
  4. 2026-10-09 21:35 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-09 20:06 UTCEPSS rescoreEPSS 32% · 98th percentile
  6. 2026-10-09 17:39 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-09 13:44 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-09 09:49 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-09 05:53 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-09 01:58 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-08 22:03 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-08 18:08 UTCEG score recompute
  13. 2026-10-08 18:08 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-08 17:11 UTCEPSS rescoreEPSS 32% · 98th percentile
  15. 2026-10-08 14:13 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-08 10:18 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-08 06:23 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-08 02:28 UTCEG score recompute
  19. 2026-10-08 02:28 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-07 23:47 UTCEPSS rescoreEPSS 32% · 98th percentile
  21. 2026-10-07 22:32 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-07 18:37 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-07 14:42 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-07 10:47 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-07 06:52 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-10-07 02:57 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-10-06 23:02 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-10-06 19:07 UTCEG score recompute
  29. 2026-10-06 19:07 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  30. 2026-10-06 15:17 UTCEPSS rescoreEPSS 32% · 98th percentile
  31. 2026-10-06 15:11 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-06 11:15 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  33. 2026-10-06 07:20 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-10-06 03:25 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  35. 2026-10-05 23:29 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-10-05 19:34 UTCEG score recompute
  37. 2026-10-05 19:34 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  38. 2026-10-05 17:42 UTCEPSS rescoreEPSS 32% · 98th percentile
  39. 2026-10-05 15:39 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  40. 2026-10-05 11:44 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-10-05 07:50 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-10-05 03:55 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-04 23:59 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-10-04 20:04 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-04 16:08 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-10-04 12:12 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  47. 2026-10-04 08:18 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-10-04 04:23 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-10-04 00:28 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-10-03 20:34 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-10-03 16:38 UTCEG score recompute
  52. 2026-10-03 16:38 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-10-03 14:25 UTCEPSS rescoreEPSS 32% · 98th percentile
  54. 2026-10-03 12:44 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  55. 2026-10-03 08:48 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-10-03 04:53 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-10-03 00:58 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-10-02 21:03 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-10-02 17:08 UTCEG score recompute
  60. 2026-10-02 17:08 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-10-02 13:13 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-10-02 09:16 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-10-02 05:21 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-10-02 01:25 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-10-01 21:30 UTCEG score recompute
  66. 2026-10-01 21:30 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-10-01 19:49 UTCEPSS rescoreEPSS 32% · 98th percentile
  68. 2026-10-01 17:35 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-10-01 13:39 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-10-01 09:44 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-10-01 05:49 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-10-01 01:54 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  73. 2026-09-30 21:57 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-09-30 18:02 UTCEG score recompute
  75. 2026-09-30 18:02 UTCGHSA enrichmentGHSA-3vfh-3cpw-2378 · GitHub severity CRITICAL · GitHub CVSS 9.8

Publicly available exploits

(4 references)

Public exploit code is referenced for this CVE (4 GitHub PoCs). No fix is confirmed yet, so defenders should restrict or isolate affected systems accordingly until one is published.

  • GitHub PoCridhinva/panos-captive-portal-rce
    Published May 22, 2026

    Scanner: CVE-2026-0300 PAN-OS User-ID Captive Portal Buffer Overflow RCE — Python CLI for detecting actively exploited BOF vulnerability in Palo Alto firewalls (CISA KEV 2026-05-13)

    Open source ↗
  • GitHub PoCmatad0r-maghribi/CVE-2026-0300-PANOS
    Published May 6, 2026

    Security Research and Proof-of-Concept (PoC) for CVE-2026-0300 : Unauthenticated Remote Code Execution (RCE) in Palo Alto Networks PAN-OS User-ID Portal.

    Open source ↗
  • GitHub PoCp3Nt3st3r-sTAr/CVE-2026-0300-POC
    Published May 6, 2026
    Open source ↗
  • GitHub PoCqassam-315/PAN-OS-User-ID-Buffer-Overflow-PoC
    Published May 6, 2026

    A research-grade Proof-of-Concept (PoC) for CVE-2026-0300, targeting the Buffer Overflow vulnerability in Palo Alto Networks PAN-OS User-ID™ Authentication Portal (CWE-787).

    Open source ↗

Frequently asked(6)

What is CVE-2026-0300?
CVE-2026-0300 is a critical-severity vulnerability; its CVE record was published on May 6, 2026. A buffer overflow vulnerability in the User-ID™ Authentication Portal (aka Captive Portal) service of Palo Alto Networks PAN-OS software allows an unauthenticated attacker to execute arbitrary code with root privileges on the PA-Series and VM-Series firewalls by sending specially crafted packets.…
When was CVE-2026-0300 made public?
CVE-2026-0300 was made public on May 5, 2026: that is the date its CVE record's CNA, Palo Alto Networks, Inc., gives for when the vulnerability was made public. The CVE record itself was published on May 6, 2026. EchelonGraph's copy of the record carries a last-modified date of July 14, 2026; the record at its source may have been updated since.
Is CVE-2026-0300 actively exploited?
Yes. CISA added CVE-2026-0300 to the Known Exploited Vulnerabilities catalog on May 6, 2026, affecting Palo Alto Networks PAN-OS. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation, and watch the vendor's advisory for the fix.
What is the CVSS score of CVE-2026-0300?
CVE-2026-0300 has a CVSS base score of 9.3 (the CNA's own assessment, by palo_alto; NVD's own analysis pending). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
Which products are affected by CVE-2026-0300?
CVE-2026-0300 affects Palo Alto Networks PAN-OS.
How do I remediate CVE-2026-0300?
No fix for CVE-2026-0300 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (Palo Alto Networks, Inc.) lists Palo Alto Networks PAN-OS versions 12.1.0 up to but not including 12.1.7, 11.2.0 up to but not including 11.2.12, 11.1.0 up to but not including 11.1.15 and 10.2.0 up to but not including 10.2.18-h6 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-0300 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-0300

Explore →

Is Your Infrastructure Affected by CVE-2026-0300?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.