PAN-OS CVE-2026-0322: Fixed Versions and Mitigations

An exploited flaw in the PAN-OS management interface lets an authenticated attacker with high privileges and network access to that interface run code as root on the firewall. Palo Alto Networks lists affected builds on the 10.2, 11.1, 11.2, 12.1 and 12.2 branches for PA-Series, VM-Series and Panorama, and says older unsupported versions should be upgraded to a supported fixed version.

Find your fixed version
By CalMax Systems Security Research · Published November 16, 2026 · Last updated: November 18, 2026

What is CVE-2026-0322, and which version fixes it?

CVE-2026-0322 is a code injection flaw (CVSS 4.0 score 8.6) in the PAN-OS management interface. An authenticated attacker with high privileges and network access to that interface can run code as root. Upgrade to a fixed build for your branch, such as 12.2.4, 12.1.10-h2, 11.2.16, 11.1.16-h3 or 10.2.18-h12, and keep management off the internet.

Palo Alto Networks has seen very limited exploitation. CISA added CVE-2026-0322 to its Known Exploited Vulnerabilities catalog on October 14, 2026, with a due date of October 17, 2026 and a forensic triage flag. Under CISA’s BOD 26-04, each US federal civilian agency’s timeline depends on the asset’s exposure. Cloud NGFW and Prisma Access are not affected.

Fixed PAN-OS Versions by Branch

From the Palo Alto Networks advisory for CVE-2026-0322 (published October 14, 2026; updated October 15, 2026, when 11.2.16 was released). Find the row for the release you run now.

Branch If you run Upgrade to
PAN-OS 12.212.2.0 through 12.2.312.2.4 or later. Before upgrading to 12.2.4, install Applications and Threats content release 9157 or later.
PAN-OS 12.112.1.8 through 12.1.10-h*12.1.10-h2 or later
12.1.5 through 12.1.7-h*12.1.7-h8, or 12.1.10-h2 or later
12.1.2 through 12.1.4-h*12.1.4-h12, or 12.1.10-h2 or later
PAN-OS 11.211.2.14 through 11.2.1511.2.16 or later
11.2.11 through 11.2.13-h*11.2.13-h3, or 11.2.16 or later
11.2.8 through 11.2.10-h*11.2.10-h15, or 11.2.16 or later
11.2.5 through 11.2.7-h*11.2.7-h21, or 11.2.16 or later
11.2.0 through 11.2.4-h*11.2.4-h22, or 11.2.16 or later
PAN-OS 11.111.1.14 through 11.1.16-h*11.1.16-h3 or later
11.1.11 through 11.1.13-h*11.1.13-h15, or 11.1.16-h3 or later
11.1.8 through 11.1.10-h*11.1.10-h35, or 11.1.16-h3 or later
11.1.7 through 11.1.7-h*11.1.7-h11, or 11.1.16-h3 or later
11.1.5 through 11.1.6-h*11.1.6-h39, or 11.1.16-h3 or later
11.1.0 through 11.1.4-h*11.1.4-h37, or 11.1.16-h3 or later
PAN-OS 10.210.2.17 through 10.2.18-h*10.2.18-h12 or later
10.2.14 through 10.2.16-h*10.2.16-h11, or 10.2.18-h12 or later
10.2.11 through 10.2.13-h*10.2.13-h26, or 10.2.18-h12 or later
10.2.8 through 10.2.10-h*10.2.10-h41, or 10.2.18-h12 or later
10.2.0 through 10.2.7-h*10.2.7-h38, or 10.2.18-h12 or later
Older unsupported PAN-OS versionsAllUpgrade to a supported fixed version
Cloud NGFWNot affectedNo action needed
Prisma AccessNot affectedNo action needed
Read “-h*” as any hotfix of that release. A row ending in “-h*” also covers hotfixes that are already fixed, so compare your full build with the fixed build in your row. For example, 11.1.10-h21 falls in the row “11.1.8 through 11.1.10-h*”, so it needs 11.1.10-h35 or 11.1.16-h3 or later; 11.1.10-h35 and later hotfixes of 11.1.10 are already fixed. A fixed hotfix on one release does not cover the next one: 11.1.7-h11 is fixed, but 11.1.8 is affected. The same versions apply to Panorama. Check the advisory before upgrading, because Palo Alto Networks can add builds after publication.

What CVE-2026-0322 Does

The flaw is in the management interface, the interface administrators use to manage PAN-OS.

Palo Alto Networks describes CVE-2026-0322 as a remote code execution vulnerability in the management interface of PAN-OS that “enables an authenticated attacker with network access to execute arbitrary code with root privileges on the firewall.” It is classed as CWE-94, code injection. The company found it internally.

It applies to PAN-OS on PA-Series and VM-Series firewalls and on Panorama (virtual and M-Series). The advisory says no special configuration is required to be affected. Cloud NGFW and Prisma Access are not impacted.

Two conditions limit who can use it. The attacker needs network access to the management interface and must be authenticated with high privileges, as the vendor’s CVSS vector specifies. Palo Alto Networks rates the flaw 8.6 (CVSS 4.0) when the management interface is reachable over the network, and 8.5 when access is restricted to a jump box that is the only system allowed to reach it. It gives the flaw its highest urgency rating.

Is your firewall at risk? The risk is highest, in Palo Alto Networks’ words, “when you allow access to the management interface from external IP addresses on the internet.” A firewall is exposed if it runs an affected version and someone outside your trusted admin network can reach its management interface, either on the dedicated MGT port or on a dataplane interface whose interface management profile allows HTTP, HTTPS, SSH or Telnet.

How to Check Your Version and Exposure

These are standard PAN-OS steps. The advisory itself does not give a check procedure.

1. Find the running version

In the web interface, the Dashboard’s General Information widget shows the software version. From the CLI:

show system info | match sw-version

Compare the result with the table above. Do this for every firewall and for Panorama. After installing the fixed release, complete the required reboot and check the running version again on each upgraded device.

2. Check who can reach management

  • MGT port: on a firewall, open Device > Setup > Interfaces > Management; on Panorama, open Panorama > Setup > Interfaces and click Management. Check which services are enabled and the Permitted IP Addresses list. An empty list leaves the enabled services unrestricted by the device’s source-address allowlist. Check upstream firewall rules and other network access controls to determine which sources can actually connect.
  • Dataplane interfaces: under Network > Network Profiles > Interface Mgmt, find profiles that allow HTTP, HTTPS, SSH or Telnet, then check which interfaces use them (Network > Interfaces, Advanced tab). Check each profile’s Permitted IP Addresses as well. Palo Alto Networks says not to attach a profile that allows HTTP, HTTPS, SSH or Telnet to an interface reachable from the internet or other untrusted zones, including one that hosts a GlobalProtect portal or gateway, because that exposes management to the internet.
  • From outside: from a network outside your own, try the firewall’s public addresses in a browser over HTTPS on port 443 and on any other port you have mapped to management. A PAN-OS administrator login page (not the GlobalProtect portal login) means management is exposed. Palo Alto Networks’ Unit 42 has found that GlobalProtect setups can expose management on ports 4443 and 3879, so test HTTPS on those ports too. Also check whether port 80 (HTTP web management) or port 22 (SSH) answers.

Mitigations Until You Can Upgrade

Palo Alto Networks says no known workarounds exist. These steps reduce the risk; upgrading removes it.

Restrict management access

Allow the management interface only from trusted internal IP addresses, ideally a single jump box, as Palo Alto Networks’ administrative access best practices recommend. Remove HTTP, HTTPS, SSH and Telnet from interface management profiles on untrusted interfaces. This is the advisory’s main risk reduction, and it is worth keeping after you upgrade.

Threat IDs 510046 and 510047 (limited coverage)

Customers with a Threat Prevention subscription can enable Threat IDs 510046 and 510047, available from Applications and Threats content version 9159-10287 and later. They only work under specific conditions. The advisory lists these steps:

The advisory warns that the coverage is limited: known attack patterns are detected, but “variations may exist that cannot currently be detected.” Treat the Threat IDs as a stopgap, not a fix.

Protect administrator accounts

Because the attacker must be authenticated with high privileges, administrator accounts and sessions are the gate. Use unique, strong passwords for every admin account, turn on MFA for all management access as Palo Alto Networks’ administrative access best practices recommend, remove accounts nobody uses, and give admins only the roles they need.

Check for Signs of Compromise

Upgrading closes the flaw. It does not tell you whether someone used it first.

Indicators from the advisory

Palo Alto Networks lists three IP addresses associated with threat activity and limited exploit attempts against this vulnerability:

66.42.72[.]14
208.83.239[.]114
149.248.47[.]234

Search your system and configuration logs (administrator logins and changes), logs from upstream devices such as an edge router or firewall, and any copies kept in your SIEM, for these addresses (remove the brackets first). If you route management traffic through a dataplane port under a logged Security policy rule, search those traffic logs too. Security policy does not apply to traffic that arrives on the dedicated MGT port, so use upstream logs for those connections. A match calls for investigation; on its own it does not prove the firewall was compromised.

What else to review

  • Administrator logins under Monitor > Logs > System: logins from unexpected addresses, at unusual times, or by accounts you don’t recognize.
  • Configuration changes under Monitor > Logs > Configuration that no one on your team made, including new administrator accounts.
  • Review retained logs for every period when management was reachable from the internet or other untrusted networks.
  • If you find activity you can’t explain, activate your incident response process and contact Palo Alto Networks support. Preserve logs and, where possible, collect volatile evidence before making changes. Coordinate containment and the revocation or rotation of potentially exposed credentials and secrets with your incident response team.

CISA’s catalog entry also flags this CVE for forensic triage under BOD 26-04, its federal patching directive, and tells agencies to evaluate each asset’s internet exposure. Federal civilian agencies must perform forensic triage for assets that meet the directive’s triage criteria.

Timeline

DateEvent
October 14, 2026Palo Alto Networks publishes the advisory with fixed versions. CISA adds CVE-2026-0322 to the Known Exploited Vulnerabilities catalog.
October 15, 2026PAN-OS 11.2.16 is published and the advisory is updated.
October 17, 2026Due date in CISA’s KEV entry. Under BOD 26-04, each US federal civilian agency’s timeline depends on the asset’s exposure.

Where ThreatListPro Fits

A known-attacker list helps on the VPN side. It does not fix this flaw.

CVE-2026-0322 needs network access to the management interface, so the lasting fix is to upgrade and keep management off the internet. No block list replaces either step.

ThreatListPro is an External Dynamic List for the traffic your firewall does expose, such as GlobalProtect portals and gateways. It covers 5.4M+ IPv4 addresses and is checked for new attackers every 6 hours. Its entries come from real attacks on live production Palo Alto GlobalProtect VPN portals in the US. A deny rule that uses it rejects traffic from listed addresses before they can try a password. The GlobalProtect guide shows the setup, and What Is an External Dynamic List? explains how PAN-OS uses EDLs.

PAN-OS CVE-2026-0322 FAQs

Is CVE-2026-0322 being exploited?

Yes. Palo Alto Networks says very limited exploitation has been observed targeting the PAN-OS management interface, and rates exploit maturity as Attacked. CISA added CVE-2026-0322 to its Known Exploited Vulnerabilities catalog on October 14, 2026. The catalog entry lists a due date of October 17, 2026 and flags the CVE for forensic triage; under BOD 26-04, each US federal civilian agency's timeline depends on the asset's exposure.

Which PAN-OS version fixes CVE-2026-0322?

Fixed releases include PAN-OS 12.2.4, 12.1.10-h2, 11.2.16, 11.1.16-h3 and 10.2.18-h12. The advisory also lists hotfix builds for earlier releases on the 12.1, 11.2, 11.1 and 10.2 branches, such as 11.1.4-h37 or 10.2.7-h38. The right build depends on the release you run now. Older unsupported PAN-OS versions need an upgrade to a supported fixed version.

Is GlobalProtect affected by CVE-2026-0322?

The flaw is in the management interface, not in the GlobalProtect portal or gateway. What matters is who can reach management: the dedicated MGT port, or a dataplane interface with an interface management profile that allows HTTP, HTTPS, SSH or Telnet. If the internet-facing interface that hosts GlobalProtect also has such a profile and its Permitted IP Addresses do not limit who can connect, the management interface is exposed there.

What access does an attacker need to exploit CVE-2026-0322?

Authenticated access with high privileges, plus network access to the management interface. Palo Alto Networks describes an authenticated attacker with network access, and its CVSS vector lists high privileges required. Restrict management access to trusted internal IP addresses, require MFA for all management access and give admin accounts only the roles they need.

Is there a workaround for CVE-2026-0322?

Palo Alto Networks says no known workarounds exist. For limited coverage, Threat Prevention subscribers must enable Threat IDs 510046 and 510047 (content version 9159-10287 or later), route inbound management traffic through a firewall dataplane port, replace the inbound management certificate, decrypt the traffic and apply Threat Prevention to it. Restrict management access to trusted internal IP addresses and upgrade to a fixed build.

Are Cloud NGFW and Prisma Access affected?

No. Palo Alto Networks says Cloud NGFW and Prisma Access are not impacted and need no action. The flaw affects PAN-OS on PA-Series and VM-Series firewalls and on Panorama, both virtual and M-Series.

What are the indicators of compromise for CVE-2026-0322?

The advisory lists three IP addresses associated with threat activity and limited exploit attempts: 66.42.72[.]14, 208.83.239[.]114 and 149.248.47[.]234. Search your logs for connections or administrator logins from these addresses, and treat any unexplained administrator login as a possible incident.

Sources

Block Known VPN Attackers on Your Palo Alto

ThreatListPro covers 5.4M+ IPv4 addresses and is checked for new attackers every 6 hours, as an External Dynamic List for PAN-OS. Monthly is $19.99 with a 14-day free trial and no card needed.

Start a 14-day free trial Or test the free sample first: free, no signup

Firewall Guides

ThreatListPro uses a plain-text feed for firewalls that support external IPv4 address lists.

Palo Alto FortiGate pfSense OPNsense SonicWall Cisco ASA Sophos XG UniFi

Related Resources

More on Palo Alto hardening and the other exploited flaws we track.

All Security Alerts GlobalProtect Hardening GlobalProtect Brute Force: Stop Authentication Attempts What Is an External Dynamic List? Palo Alto EDL Troubleshooting Password Spraying on VPNs