NETWORK INCIDENTS

Exploited now

Remediation guide
Palo Alto Networks · PAN-OS

CVE-2026-0322

PAN-OS: Authenticated Remote Code Execution (RCE) in the Management Interface

CISA KEV
Known exploitedadded 14 Oct 2026; US federal deadline 17 Oct 2026
Exploit likelihood
2.1%82nd percentile · FIRST EPSS, 2026-11-15
Severity
8.6 HighCVSS 4.0, Palo Alto Networks; 8.5 when management access is limited to a jump box
Last verified
30 Oct 2026against the sources below

1In plain language

A flaw in the PAN-OS management interface lets an attacker who has logged in to it, and can reach it over the network, run any code they like with root privileges on the firewall.

It affects PAN-OS on PA-Series and VM-Series firewalls and on Panorama. Cloud NGFW and Prisma Access are not affected.

Palo Alto Networks has seen very limited exploitation against the management interface, and CISA lists it as known to be exploited. The risk is highest when the management interface can be reached from the internet.

2Am I affected?

No special configuration is required to be affected by this issue.

ProductAffectedUnaffected
Cloud NGFWNoneAll
PAN-OS 12.2< 12.2.4>= 12.2.4
PAN-OS 12.1< 12.1.4-h12
< 12.1.7-h8
< 12.1.10-h2
>= 12.1.4-h12
>= 12.1.7-h8
>= 12.1.10-h2
PAN-OS 11.2< 11.2.4-h22
< 11.2.7-h21
< 11.2.10-h15
< 11.2.13-h3
< 11.2.16
>= 11.2.4-h22
>= 11.2.7-h21
>= 11.2.10-h15
>= 11.2.13-h3
>= 11.2.16
PAN-OS 11.1< 11.1.4-h37
< 11.1.6-h39
< 11.1.7-h11
< 11.1.10-h35
< 11.1.13-h15
< 11.1.16-h3
>= 11.1.4-h37
>= 11.1.6-h39
>= 11.1.7-h11
>= 11.1.10-h35
>= 11.1.13-h15
>= 11.1.16-h3
PAN-OS 10.2< 10.2.7-h38
< 10.2.10-h41
< 10.2.13-h26
< 10.2.16-h11
< 10.2.18-h12
>= 10.2.7-h38
>= 10.2.10-h41
>= 10.2.13-h26
>= 10.2.16-h11
>= 10.2.18-h12
Prisma AccessNoneAll

Check your version

The advisory doesn't say how to check your version. Palo Alto's CLI documentation shows that show system info, run from the CLI, reports information about the device, including its software version as sw-version.

> show system info

In the output, look at the sw-version line. Palo Alto Networks docs ↗

Compare the sw-version value with the table above. A version in an Affected range for your branch is vulnerable; a version at or above an Unaffected value for your branch is not. our analysis

How to check the version on Panorama: Not stated by vendor.

3Fix

Find your branch and current version in the table, and upgrade to the version shown. our analysis

ProductRunningWhat the vendor says to do
Cloud NGFWAllNo action needed.
PAN-OS 12.212.2.0 through 12.2.3Upgrade to 12.2.4 or later.
PAN-OS 12.112.1.8 through 12.1.10-h*Upgrade to 12.1.10-h2 or later.
12.1.5 through 12.1.7-h*Upgrade to 12.1.7-h8 or 12.1.10-h2 or later.
12.1.2 through 12.1.4-h*Upgrade to 12.1.4-h12 or 12.1.10-h2 or later.
PAN-OS 11.211.2.14 through 11.2.15Upgrade to 11.2.16 or later.
11.2.11 through 11.2.13-h*Upgrade to 11.2.13-h3 or 11.2.16 or later.
11.2.8 through 11.2.10-h*Upgrade to 11.2.10-h15 or 11.2.16 or later.
11.2.5 through 11.2.7-h*Upgrade to 11.2.7-h21 or 11.2.16 or later.
11.2.0 through 11.2.4-h*Upgrade to 11.2.4-h22 or 11.2.16 or later.
PAN-OS 11.111.1.14 through 11.1.16-h*Upgrade to 11.1.16-h3 or later.
11.1.11 through 11.1.13-h*Upgrade to 11.1.13-h15 or 11.1.16-h3 or later.
11.1.8 through 11.1.10-h*Upgrade to 11.1.10-h35 or 11.1.16-h3 or later.
11.1.7 through 11.1.7-h*Upgrade to 11.1.7-h11 or 11.1.16-h3 or later.
11.1.5 through 11.1.6-h*Upgrade to 11.1.6-h39 or 11.1.16-h3 or later.
11.1.0 through 11.1.4-h*Upgrade to 11.1.4-h37 or 11.1.16-h3 or later.
PAN-OS 10.210.2.17 through 10.2.18-h*Upgrade to 10.2.18-h12 or later.
10.2.14 through 10.2.16-h*Upgrade to 10.2.16-h11 or 10.2.18-h12 or later.
10.2.11 through 10.2.13-h*Upgrade to 10.2.13-h26 or 10.2.18-h12 or later.
10.2.8 through 10.2.10-h*Upgrade to 10.2.10-h41 or 10.2.18-h12 or later.
10.2.0 through 10.2.7-h*Upgrade to 10.2.7-h38 or 10.2.18-h12 or later.
All older unsupported PAN-OS versionsAllUpgrade to a supported fixed version.
Prisma AccessAllNo action needed.

4Can't patch tonight?

No known workarounds exist for this issue.

Restricting the management interface to trusted internal IP addresses minimizes the risk, following Palo Alto's recommended best-practice deployment guidelines. Source ↗

Customers with a Threat Prevention subscription get limited coverage by enabling Threat IDs 510046 and 510047, from Applications and Threats content version 9159-10287 and later.

The vendor explains that limited coverage means known attack patterns can be identified using the current Threat ID, but variations may exist that can't currently be detected, and it recommends upgrading to an unaffected version.

For these Threat IDs to protect against attacks for this vulnerability, the vendor says to:

  • Route incoming traffic for the MGT port through a DP port, e.g., enabling management profile on a DP interface for management access. How ↗
  • Replace the Certificate for Inbound Traffic Management. How ↗
  • Decrypt inbound traffic to the management interface so the firewall can inspect it. How ↗
  • Enable threat prevention on the inbound traffic to management services.

Please note that this Threat ID requires SSL Decryption.

5Was I hit?

Logs to check and detection steps: Not stated by vendor.

Palo Alto Networks lists IP addresses that have been associated with threat activity and limited exploit attempts targeting this vulnerability, in the FAQ of its advisory. Source ↗

We link to the vendor's list rather than copy it, so you always see its current version. our analysis

CISA's catalog marks forensic triage for this CVE as required, and its required action points to CISA's Forensics Triage Requirements. Source ↗

6Sources

Summary of public vendor guidance. Verify against the vendor advisory before acting.

See CVE-2026-0322 in the exploited-now list (exploit likelihood, CISA's description, deadline).