Someone left a loaded gun in the XML parser guarding your castle gate
CVE-2026-0310 is a heap-based buffer overflow (CWE-787) in the XML processing subsystem of Palo Alto Networks PAN-OS. An unauthenticated attacker with network access to either the management web interface or the dataplane interface can send a crafted XML payload that triggers an out-of-bounds write. On PA-Series hardware firewalls, this yields arbitrary code execution as root. On VM-Series, the impact is limited to denial of service (crash). Affected versions span PAN-OS 10.2 through 12.2, plus Cloud NGFW (AWS and Azure) and Prisma Access — essentially the entire active PAN-OS fleet. Fixed versions include PAN-OS 12.2.3, 12.1.10, 11.2.13-h2, and various hotfix branches for 11.1 and 10.2.
Palo Alto published differentiated CVSS 4.0 scores: 9.2 base for PA-Series, 8.7 for VM-Series, and 7.5–7.7 for cloud-managed variants. This tiering is intellectually honest — hardware firewalls run flat Linux with root meaning total device ownership, while cloud variants have hypervisor containment. However, the vendor's threat-adjusted score (CVSS-BT 7.2 for PA-Series) leans too optimistic for a perimeter device reachable via the dataplane — the interface that *must* face the network by design. History shows PAN-OS XML/auth bugs (CVE-2024-0012, CVE-2024-3400, CVE-2026-0300) get weaponized within days to weeks of disclosure. The vendor's base score is fair; their threat-adjusted downgrade is premature given the target's value.
5 steps from start to impact.
Identify exposed PAN-OS interface
- Target runs PAN-OS 10.2–12.2 on an unpatched version
- Management web interface or dataplane service is network-reachable
- Management interface exposure is avoidable — Palo Alto best practice restricts it to OOB/jump-host only
- Organizations following CIS benchmarks may already block external management access
http.html:"PAN-OS" or ssl.jarm fingerprinting for GlobalProtect portals. GreyNoise tags for PAN-OS scanning activity.Craft malicious XML payload
- Working exploit or deep reverse-engineering capability
- Knowledge of PAN-OS memory layout for the target version/hardware
- AC:H — exploit reliability depends on heap state; may require multiple attempts or version-specific offsets
- No public PoC or exploit framework module available yet
- PA-Series runs PAN-OS on custom MIPS/ARM hardware, complicating generic exploit development
Deliver XML payload to target interface
- Network path to the target interface (direct internet or post-pivot on internal network)
- No WAF or IPS signature blocking the malformed XML
- Well-configured networks restrict management to OOB; dataplane services are harder to restrict
- Palo Alto Threat Prevention signatures may detect malformed XML if content inspection is enabled on the management path
Achieve root code execution (PA-Series) or crash (VM-Series)
- Successful heap corruption on PA-Series hardware
- Target is PA-Series (for RCE) or VM-Series (for DoS)
- VM-Series deployments get DoS only, not RCE — reducing blast radius for cloud-heavy shops
- Crash on VM-Series may trigger HA failover, limiting outage duration
show system software status), unexpected process restarts. SIEM alerts on firewall management session anomalies or sudden config changes.Pivot and persist
- Root shell on PA-Series
- Operational objective beyond initial access
- Forensic artifacts in PAN-OS logs if logging is forwarded to external SIEM before compromise
- Palo Alto Cortex XDR or similar EDR on internal hosts may detect lateral movement originating from the firewall's management IP
- Restricting management interface access alone — while critical hygiene, this does NOT mitigate the dataplane attack vector. The vulnerability is reachable via GlobalProtect portal and Captive Portal interfaces that must be internet-facing by design.
- Network segmentation behind the firewall — the firewall IS the segmentation boundary. Compromising it bypasses all downstream segmentation.
- WAF in front of the firewall for management traffic — placing a WAF in front of a firewall's management interface is architecturally unusual and typically not deployed. The dataplane path bypasses any such control entirely.
- Disabling XML-based features — there is no documented way to disable XML processing in PAN-OS; it is integral to the management and dataplane service stack.
The supporting signals.
| In-the-Wild Exploitation | Not confirmed. Disclosed September 9, 2026. No reports of active exploitation yet, but PAN-OS vulns historically see rapid weaponization (CVE-2024-3400 was 0-day; CVE-2026-0300 was exploited pre-disclosure by state-sponsored actors). |
|---|---|
| Proof of Concept | None public as of September 10, 2026. Discovered internally by Palo Alto Networks security research. AC:H suggests non-trivial exploitation, but determined adversaries with PAN-OS lab access can develop exploits. |
| EPSS Score | Not yet scored — CVE was disclosed <24 hours ago. Expect EPSS to populate within 1–2 weeks. Comparable PAN-OS RCE bugs (CVE-2024-3400) reached top 1% EPSS rapidly. |
| CISA KEV Status | Not listed. No active exploitation confirmed. Given the target profile, KEV listing is likely if exploitation emerges. |
| CVSS Vector (Vendor, CVSS 4.0) | 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 — PA-Series base 9.2, threat-adjusted 7.2. Network-reachable, no auth, high complexity, full CIA impact on vulnerable system. |
| Affected Versions | PAN-OS 10.2 (< various hotfixes), 11.1 (< various hotfixes), 11.2 (< 11.2.13-h2), 12.1 (< 12.1.10), 12.2 (< 12.2.3). Also Cloud NGFW (AWS/Azure) and Prisma Access 10.2/11.2/12.1. |
| Fixed Versions | PAN-OS 12.2.3, 12.1.10 / 12.1.7-h5 / 12.1.4-h10, 11.2.13-h2 / 11.2.10-h14 / 11.2.7-h20, plus hotfix branches for 11.1 and 10.2. Cloud NGFW patched automatically. |
| Scanning / Exposure Data | Censys indexes ~263,000 internet-facing PAN-OS hosts globally. Management interfaces specifically: ~15,400 exposed per Shodan (Sejiyama, 2024 baseline). Dataplane services (GlobalProtect portals) are exposed by design on a much larger subset. |
| Disclosure Date | September 9, 2026 — vendor-coordinated disclosure by Palo Alto Networks. |
| Reporting Researcher | Palo Alto Networks internal security research teams (no external credit listed). |
Sources.
- Palo Alto Networks Security Advisory (CVE-2026-0310)
- SecurityOnline — PAN-OS Buffer Overflow Flaw Analysis
- VulnCheck — Routinely Targeted Vulnerabilities 2026
- Censys Advisory — PAN-OS CVE-2026-0300 (comparable vuln)
- Splunk Vulnerability Disclosure SVD-2026-0310
- CISA Known Exploited Vulnerabilities Catalog
- The Hacker News — PAN-OS RCE Exploit Coverage
Why this verdict
- Canonical high-value role floor: PAN-OS runs exclusively on network edge appliances — firewalls, VPN gateways, and security enforcement points. 100% of PA-Series installs are perimeter infrastructure by definition. Root compromise of this component = network boundary ownership, traffic interception, credential harvesting, and lateral movement pivot. This floors the verdict at CRITICAL.
- Role multiplier: On PA-Series hardware, the chain succeeds at the perimeter high-value role with blast radius of *fleet-scale* — a compromised firewall can modify ACLs to expose the entire internal network, intercept all transit traffic, harvest VPN/SSO credentials, and serve as a persistent C2 relay. On VM-Series the blast radius is limited to DoS (host-level). On Cloud NGFW, blast radius is tenant-level DoS. The worst plausible outcome (PA-Series root RCE at the perimeter) drives the floor.
- Unauthenticated + dataplane reachable: The attack requires no credentials and can target the dataplane interface — the one interface that *cannot* be restricted away because it must face the network to function. This eliminates the most common compensating control (restrict management access) as a complete mitigation.
- Attack complexity friction (AC:H): CVSS rates complexity as High, meaning heap layout dependencies, possible ASLR bypass, and version-specific offsets. No public PoC exists. This is genuine friction that prevents script-kiddie-level exploitation but does NOT stop state-sponsored or well-resourced adversaries who can lab the target hardware.
- Historical precedent: PAN-OS CVE-2024-3400 (command injection) was weaponized as a 0-day. CVE-2026-0300 (similar XML buffer overflow) was exploited pre-disclosure by state-sponsored actors. The pattern strongly suggests CVE-2026-0310 will attract rapid exploit development from APT-tier adversaries.
Why not higher?
The score is 9.0 rather than 10.0 because attack complexity is genuinely High — the exploit must defeat ASLR or similar protections on PAN-OS, requires version-specific heap layout knowledge, and no public PoC or exploitation evidence exists yet. VM-Series deployments (a meaningful fraction of the install base) are limited to DoS, not RCE. These factors cap the score below maximum.
Why not lower?
Downgrading below CRITICAL is not defensible because the affected component is the perimeter by definition — there is no 'restrict network exposure' mitigation that removes the dataplane attack surface. Every PA-Series firewall offering GlobalProtect VPN or Captive Portal presents the vulnerable XML parser to untrusted traffic. The historical pattern of rapid PAN-OS weaponization (CVE-2024-3400 in <48 hours, CVE-2026-0300 pre-disclosure) means the current absence of a public PoC is a temporary condition, not a structural mitigation.
Crowdsourced verification payload.
Run this script on any auditor workstation with SSH access to your PAN-OS devices. Invoke as: bash check_cve_2026_0310.sh <firewall-ip> <admin-username>. Requires SSH key or password authentication to the PAN-OS CLI. The script checks the running PAN-OS version against known-fixed versions.
#!/usr/bin/env bash
# check_cve_2026_0310.sh — Check PAN-OS version for CVE-2026-0310
# Usage: bash check_cve_2026_0310.sh <firewall-ip> <admin-user>
# Requires: SSH access to PAN-OS CLI
# Exit codes: 0=PATCHED, 1=VULNERABLE, 2=UNKNOWN
set -euo pipefail
if [ $# -lt 2 ]; then
echo "Usage: $0 <firewall-ip> <admin-user>"
exit 2
fi
FW_IP="$1"
FW_USER="$2"
# Grab PAN-OS version via CLI
VERSION=$(ssh -o ConnectTimeout=10 -o StrictHostKeyChecking=accept-new "${FW_USER}@${FW_IP}" 'show system info' 2>/dev/null | grep 'sw-version:' | awk '{print $2}' | tr -d '[:space:]')
if [ -z "$VERSION" ]; then
echo "UNKNOWN — could not retrieve PAN-OS version from ${FW_IP}"
exit 2
fi
echo "Detected PAN-OS version: ${VERSION}"
# Version comparison helper
version_gte() {
[ "$(printf '%s\n' "$1" "$2" | sort -V | head -n1)" = "$2" ]
}
# Check against fixed versions per major branch
case "$VERSION" in
12.2*)
if version_gte "$VERSION" "12.2.3"; then
echo "PATCHED — ${VERSION} >= 12.2.3"
exit 0
else
echo "VULNERABLE — ${VERSION} < 12.2.3 (CVE-2026-0310)"
exit 1
fi
;;
12.1*)
if version_gte "$VERSION" "12.1.10"; then
echo "PATCHED — ${VERSION} >= 12.1.10"
exit 0
else
echo "VULNERABLE — ${VERSION} < 12.1.10 (CVE-2026-0310). Check if hotfix 12.1.7-h5 or 12.1.4-h10 applies."
exit 1
fi
;;
11.2*)
if version_gte "$VERSION" "11.2.13-h2"; then
echo "PATCHED — ${VERSION} >= 11.2.13-h2"
exit 0
else
echo "VULNERABLE — ${VERSION} < 11.2.13-h2 (CVE-2026-0310). Check hotfix branches 11.2.10-h14 or 11.2.7-h20."
exit 1
fi
;;
11.1*)
echo "VULNERABLE — PAN-OS 11.1.x requires specific hotfixes for CVE-2026-0310. Consult advisory SVD-2026-0310."
exit 1
;;
10.2*)
echo "VULNERABLE — PAN-OS 10.2.x requires specific hotfixes for CVE-2026-0310. Consult advisory SVD-2026-0310."
exit 1
;;
*)
echo "UNKNOWN — PAN-OS ${VERSION} not in affected range (10.2–12.2) or unrecognized version format."
exit 2
;;
esac