CVE Intelligence
High Memory corruption

CVE-2026-0310 — PAN-OS: Buffer Overflow Vulnerability via XML Processing

A buffer overflow vulnerability in the XML processing functionality of Palo Alto Networks PAN-OS® software enables an unauthenticated attacker with network access to the management web or dataplane interface to cause a denial of service (DoS) condition on VM-Series firewalls or execute arbitrary code with root privileges on the PA-Series firewalls. The security risk posed by this issue is minimized when the management interface is restricted to only trusted internal IP addresses according to our recommended best practice deployment guidelines https://live.paloaltonetworks.com/t5/community-blogs/tips-amp-tricks-how-to-secure-the-management-access-of-your-palo/ba-p/464431 . Panorama is impacted by this vulnerability.

Published Sep 10, 2026 · Updated Oct 15, 2026 · Sources: CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database, GitHub Security Advisories · CNA: palo_alto

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.4% (30-day exploitation probability)+4
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.37%
ahead of 29% of scored CVEs · Oct 14, 2026
Affects
Palo Alto Networks
Cloud NGFW and 2 more
CVSS base
7.2
High · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Palo Alto Networks Cloud NGFW, Palo Alto Networks PAN-OS, Palo Alto Networks Prisma Access).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Palo Alto Networks Cloud NGFW version All Vulnerable CVE Program (cve.org) e CISA ADP
Palo Alto Networks PAN-OS ≥ 12.2.0 and < 12.2.3≥ 12.1.0 and < 12.1.4-h10≥ 11.2.0 and < 11.2.4-h21≥ 11.1.0 and < 11.1.4-h36≥ 10.2.0 and < 10.2.7-h37 Vulnerable CVE Program (cve.org) e CISA ADP
Palo Alto Networks Prisma Access ≥ 11.2.0 and < 11.2.4-h21≥ 10.2.0 and < 10.2.7-h37 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
High
Attack requirements
None
Privileges required
None
User interaction
None
Scope
X
Confidentiality (vulnerable system)
High
Integrity (vulnerable system)
High
Availability (vulnerable system)
High
Confidentiality (subsequent)
Low
Integrity (subsequent)
Low
Availability (subsequent)
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.2 CVSS 4.0 High — — psirt@paloaltonetworks.com via NIST National Vulnerability Database
7.2 CVSS 4.0 High — — palo_alto via CVE Program (cve.org) e CISA ADP
6.6 CVSS 4.0 Medium — — palo_alto via CVE Program (cve.org) e CISA ADP
5.2 CVSS 4.0 Medium — — palo_alto via CVE Program (cve.org) e CISA ADP
4.8 CVSS 4.0 Medium — — palo_alto via CVE Program (cve.org) e CISA ADP
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:U/V:D/RE:M/U:Red (score shown at the top: psirt@paloaltonetworks.com)
Sources assign different scores within the same severity band. For prioritization we use 7.2 (psirt@paloaltonetworks.com via NIST National Vulnerability Database) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-787 · Out-of-bounds Write

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
web/proxy/WAF logsnetwork IDS/IPSendpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Published → Awaiting Analysis
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 15, 2026
  • CVSS changed · 7.2
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Record created in this database
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • CVE published
    Sep 10, 2026 · palo_alto

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 15, 2026 – Oct 15, 2026
  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

4 on the record

Elsewhere on this site

Palo Alto Networks
every CVE for this vendor
Memory corruption
same class
CWE-787
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-0320 PAN-OS: Authenticated Admin Command Injection Vulnerability 1d
  • CVE-2026-0318 PAN-OS: Denial of Service (DoS) on Panorama 1d
  • CVE-2026-0319 PAN-OS: Improper Input Handling Vulnerability 1d
  • CVE-2026-0316 PAN-OS: Stored Cross-Site Scripting (XSS) Vulnerability 1d
  • CVE-2026-0317 PAN-OS: Denial of Service Vulnerability 1d
  • CVE-2026-0321 PAN-OS: Denial of Service (DoS) Vulnerabilities in Network Services 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-0310 is "PAN-OS: Buffer Overflow Vulnerability via XML Processing", rated High. It affects Cloud NGFW (Palo Alto Networks); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.2 describes technical severity. EPSS 0.37% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.