# CVE-2026-0322: Palo Alto Networks PAN-OS, is it exploitable where you run it

Ledger entry, disclosed 14 Oct 2026, sources read 19 Nov 2026

**The short answer.** CVE-2026-0322 affects Palo Alto Networks PAN-OS and was disclosed 14 Oct 2026 with a CVSS score of 8.6. Exposure needs these conditions: PAN-OS runs below the fixed build for its release train; the attacker can reach the management interface and holds a valid administrator account. CISA added it to the Known Exploited Vulnerabilities catalog on 14 Oct 2026.

## What the flaw is

CVE-2026-0322 is a code injection flaw (CWE-94) in the management interface of Palo Alto Networks PAN-OS. An attacker who can reach the management interface over the network and holds a valid account can run arbitrary code as root on the firewall. Root on a firewall gives full control of the device and the traffic it handles.

It affects PAN-OS on PA-Series and VM-Series firewalls and on Panorama (virtual and M-Series). Cloud NGFW and Prisma Access are not affected. Palo Alto says no special configuration is needed to be affected, so every running instance of an affected build counts.

Palo Alto rates it 8.6 on the CVSS 4.0 base score: network, low complexity, high privileges required, high impact on the device. NVD's own CVSS 3.1 score is 7.2 with the same high-privilege requirement. The vendor says risk is highest when the management interface is open to the internet, and that restricting it to trusted internal addresses minimizes the risk.

## Are you exposed: each condition and how to check it

| Condition for exposure | How to check it on your system |
| --- | --- |
| PAN-OS runs below the fixed build for its release train | On the CLI run `show system info` and read the sw-version line. In the web interface, open Dashboard and read General Information > Software Version. Compare with the versions table. Check Panorama and every firewall it manages. `show system info` also prints the model and family lines. |
| the attacker can reach the management interface and holds a valid administrator account | Open Device > Setup > Interfaces > Management Interface Settings and read Permitted IP Addresses. Also open Network > Network Profiles > Interface Mgmt and list every profile that allows HTTPS or SSH, then see which data-plane interfaces use it. From outside, test whether the management address answers from an untrusted network. A management address reachable from the internet is the highest-risk case. Open Device > Administrators and list accounts and their roles. Review Device > Authentication Profile and any RADIUS, LDAP or SAML server in use, and check who holds credentials, including shared or stale admin accounts. |

## Affected and fixed versions

| Release train | Affected builds | Upgrade to |
| --- | --- | --- |
| PAN-OS 12.2 | 12.2.0 to 12.2.3 | 12.2.4 or later |
| PAN-OS 12.1 | 12.1.8 up to, not including, 12.1.10-h2 | 12.1.10-h2 or later |
| PAN-OS 12.1 | 12.1.5 up to, not including, 12.1.7-h8 | 12.1.7-h8, or 12.1.10-h2 or later |
| PAN-OS 12.1 | 12.1.2 up to, not including, 12.1.4-h12 | 12.1.4-h12, or 12.1.10-h2 or later |
| PAN-OS 11.2 | 11.2.14 to 11.2.15 | 11.2.16 or later |
| PAN-OS 11.2 | 11.2.11 up to, not including, 11.2.13-h3 | 11.2.13-h3, or 11.2.16 or later |
| PAN-OS 11.2 | 11.2.8 up to, not including, 11.2.10-h15 | 11.2.10-h15, or 11.2.16 or later |
| PAN-OS 11.2 | 11.2.5 up to, not including, 11.2.7-h21 | 11.2.7-h21, or 11.2.16 or later |
| PAN-OS 11.2 | 11.2.0 up to, not including, 11.2.4-h22 | 11.2.4-h22, or 11.2.16 or later |
| PAN-OS 11.1 | 11.1.14 up to, not including, 11.1.16-h3 | 11.1.16-h3 or later |
| PAN-OS 11.1 | 11.1.11 up to, not including, 11.1.13-h15 | 11.1.13-h15, or 11.1.16-h3 or later |
| PAN-OS 11.1 | 11.1.8 up to, not including, 11.1.10-h35 | 11.1.10-h35, or 11.1.16-h3 or later |
| PAN-OS 11.1 | 11.1.7 up to, not including, 11.1.7-h11 | 11.1.7-h11, or 11.1.16-h3 or later |
| PAN-OS 11.1 | 11.1.5 up to, not including, 11.1.6-h39 | 11.1.6-h39, or 11.1.16-h3 or later |
| PAN-OS 11.1 | 11.1.0 up to, not including, 11.1.4-h37 | 11.1.4-h37, or 11.1.16-h3 or later |
| PAN-OS 10.2 | 10.2.17 up to, not including, 10.2.18-h12 | 10.2.18-h12 or later |
| PAN-OS 10.2 | 10.2.14 up to, not including, 10.2.16-h11 | 10.2.16-h11, or 10.2.18-h12 or later |
| PAN-OS 10.2 | 10.2.11 up to, not including, 10.2.13-h26 | 10.2.13-h26, or 10.2.18-h12 or later |
| PAN-OS 10.2 | 10.2.8 up to, not including, 10.2.10-h41 | 10.2.10-h41, or 10.2.18-h12 or later |
| PAN-OS 10.2 | 10.2.0 up to, not including, 10.2.7-h38 | 10.2.7-h38, or 10.2.18-h12 or later |
| All older unsupported PAN-OS | All versions | Upgrade to a supported fixed version |

Hotfix builds (-h) are listed per sub-train: any build below the fixed hotfix for your sub-train is affected, so pick the fixed build that matches your minor release. Siemens lists RUGGEDCOM APE1808 devices running a PAN-OS Virtual NGFW as affected by this CVE and points customers to Siemens support for patch information (Siemens SSA-104023, version 1.3, 10 Nov 2026).

## If the fix cannot go in yet

- No workaround exists (Palo Alto). Upgrading to the fixed build for your train is the fix.
- Restrict management interface access to trusted internal IP addresses, ideally one jump box that is the only system allowed to reach it. Cost: administrators must connect through that host or from those addresses, and any tool or script that manages the device from elsewhere stops working. Palo Alto rates the jump-box case 8.5 instead of 8.6 because the attack vector becomes adjacent, so it lowers the risk only a little and does not remove it.
- Threat Prevention subscribers can enable Threat IDs 510046 and 510047 (Applications and Threats content version 9159-10287 or later). Palo Alto calls this limited coverage. It works only if you route management-port traffic through a data-plane interface (management profile on a data-plane interface), replace the certificate for inbound traffic management, decrypt inbound traffic to the management interface, and enable threat prevention on it. Cost: SSL decryption load and certificate work on the firewall, and attack variants may still pass.

## What to look for

- Indicator addresses Palo Alto ties to limited exploit attempts: 66[.]42[.]72[.]14, 208[.]83[.]239[.]114, 149[.]248[.]47[.]234. In the web interface, open Monitor > Logs > System and filter on the source address in the event description: administrator logins to the management interface are recorded there with the client address. In Monitor > Logs > Configuration, the Host column holds the address an administrator connected from. In Monitor > Logs > Traffic, filter on the Source Address field, for example `( addr.src in 66.42.72.14 )`; this shows only sessions that crossed a data-plane interface, so it covers management traffic only where you route it through one. Palo Alto does not say which log records the attempts.
- CISA's KEV entry marks forensic triage as required for this CVE. Its required action says to apply vendor mitigations in line with BOD 26-04 and CISA's forensics triage requirements. Palo Alto publishes no log signatures or file indicators beyond the three addresses.

## Timeline

| Date | Event | Source |
| --- | --- | --- |
| 14 Oct 2026 | Palo Alto Networks publishes advisory CVE-2026-0322 (internal discovery, credited to Suraj Siddharudh) with fixed builds, exploit maturity ATTACKED and the note that very limited exploitation has been observed. NVD publishes the record and CISA adds the CVE to KEV the same day, with a due date of 17 Oct 2026. | [source](https://security.paloaltonetworks.com/CVE-2026-0322) |
| 15 Oct 2026 | Palo Alto records an update to the advisory (the Updated field reads 2026-10-15). | [source](https://security.paloaltonetworks.com/CVE-2026-0322) |
| 10 Nov 2026 | Siemens adds CVE-2026-0322 to advisory SSA-104023 for RUGGEDCOM APE1808 devices running PAN-OS Virtual NGFW (version 1.3). | [source](https://cert-portal.siemens.com/productcert/html/ssa-104023.html) |

The earliest dated mark of exploitation is CISA's, on 14 Oct 2026, the day of disclosure; exploitation may have begun earlier.

## Exploitation reported so far

CISA's SSVC data in the NVD record shows exploitation as active, automatable as no and technical impact as total. KEV lists ransomware campaign use as Unknown.

## Why attack-path analysis settles it

Exposure needs two things at once: a network path to the management interface and a valid high-privilege account. The version row tells you if the code is present, but only the reachability and account rows tell you whether an attacker can use it. An attack-path view answers that, and the permitted-IP and administrator lists are where to read it.

## Related pages

- [CVE-2026-97229: GitLab CE/EE, GitLab CI/CD regex RCE](/ledger/cve-2026-97229/)
- [CVE-2026-102764: BeyondTrust Remote Support](/ledger/cve-2026-102764/)
- [CVE-2026-21589: Atlassian Data Center products](/ledger/cve-2026-21589/)

## Sources

- CVE-2026-0322: NVD record: https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-0322 (read 19 Nov 2026)
- CVE-2026-0322: CISA KEV entry (feed version 2026.11.18): https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-0322 (read 19 Nov 2026)
- CVE-2026-0322: Palo Alto Networks security advisory (fixed builds, exploit status, Threat IDs, indicator addresses): https://security.paloaltonetworks.com/CVE-2026-0322 (read 19 Nov 2026)
- CVE-2026-0322: Siemens ProductCERT advisory SSA-104023 (RUGGEDCOM APE1808): https://cert-portal.siemens.com/productcert/html/ssa-104023.html (read 19 Nov 2026)

Last reviewed 19 Nov 2026. Canonical: https://reachabilityanalysis.com/ledger/cve-2026-0322/
