Palo Alto PAN-OS Management RCE Is Listed as Attacked

P1 — VALIDATE AND UPDATEHigh · 8.6 (CVSS v4.0)EXPLOITATION: NOT STATED

Quick Answer

Palo Alto Networks published CVE-2026-0322 for PAN-OS management interfaces and labels exploit maturity ATTACKED. Match each firewall or Panorama system to the detailed branch table, install the exact fixed build, restrict management access, review telemetry, and retain evidence.

Confirm Scope And Apply The Supported Remediation

What to do now: Inventory PA-Series, VM-Series, and Panorama management interfaces and versions; remove internet exposure; deploy the exact fixed build for each branch; enable the authority-supported Threat Prevention path only where its SSL-decryption prerequisites are satisfied; and review management-plane activity.

Open the authoritative advisory

Last verified: 2026-10-15 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopePAN-OS management interfaces on PA-Series, VM-Series, and Panorama
AdvisoryCVE-2026-0322 / CISA KEV addition 2026-10-14
CVECVE-2026-0322
Authoritative release date2026-10-14 16:00:00 UTC
Authority revision date2026-10-14 19:27:28 UTC
Affected versionsPAN-OS 12.2 before 12.2.4; the advisory-listed hotfix ranges in PAN-OS 12.1, 11.2, 11.1, and 10.2; Cloud NGFW and Prisma Access are not affected.
Fixed versionthe advisory-matched fixed build: 12.2.4, 12.1.4-h12/12.1.7-h8/12.1.10-h2, 11.2.4-h22/11.2.7-h21/11.2.10-h15/11.2.13-h3/11.2.16, 11.1 branch fixes through 11.1.16-h3, or 10.2 branch fixes through 10.2.18-h12
CVSS base score8.6 (CVSS v4.0)
CVSS severityHigh
Exploitation statusPalo Alto Networks labels the issue ATTACKED; CISA includes it in KEV.; no exploitation claim is inferred.

What Changed

Palo Alto Networks disclosed authenticated root-code execution through the management interface, labels exploit maturity ATTACKED, and says no special configuration is required. CISA added the CVE to KEV.

What To Validate Now

  1. Inventory. Locate PAN-OS management interfaces on PA-Series, VM-Series, and Panorama deployments, versions, enabled features, exposure paths, owners, and dependent services.
  2. Establish applicability. Compare each deployment with the authority's affected-version statement: PAN-OS 12.2 before 12.2.4; the advisory-listed hotfix ranges in PAN-OS 12.1, 11.2, 11.1, and 10.2; Cloud NGFW and Prisma Access are not affected. Do not infer applicability from product family or severity alone.
  3. Remediate. Apply the advisory-matched fixed build: 12.2.4, 12.1.4-h12/12.1.7-h8/12.1.10-h2, 11.2.4-h22/11.2.7-h21/11.2.10-h15/11.2.13-h3/11.2.16, 11.1 branch fixes through 11.1.16-h3, or 10.2 branch fixes through 10.2.18-h12 through the supported vendor or project channel, following the current advisory and change-control requirements.
  4. Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document exceptions.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

No general workaround exists. Threat IDs 510046 and 510047 provide only limited coverage and require the documented traffic routing, inbound certificate, SSL decryption, and threat-prevention configuration. Preserve the authority snapshot, asset and owner records, before-and-after versions, change approval, installation output, validation results, exceptions, and rollback evidence.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.