Executive Summary

CVE-2026-0322 is a remote code execution flaw in the management interface of Palo Alto Networks PAN-OS software that allows an authenticated attacker with network access to run arbitrary code with root privileges on the firewall. When that firewall is the device enforcing separation between IT and OT, root-level compromise means the attacker controls the one asset your segmentation architecture depends on.

Technical Exposure Breakdown

The vulnerable component is the PAN-OS management interface, not the data plane that passes production traffic. Per the grounding data, affected ranges include builds up to 10.2.0, the 11.2.0 through 11.2.16 range, and the 12.2.0 through 12.2.4 range. The CVSS score is 7.2, and the vulnerability is flagged in the known exploited vulnerability catalog. Patch status in our source data is unknown, so operators should not assume a fixed build is available for their specific train without direct confirmation from the vendor.

The attack requires authentication and network access to the management plane. That precondition matters. The exploit is not a pre-auth internet drive-by, but authenticated access to a firewall management interface is a far lower bar than many operators assume. Credential reuse, exposed management VLANs, jump hosts shared between IT and OT administration, and flat engineering networks all shorten the path to a valid session. Once authenticated, the attacker executes code as root, which gives full control of rule sets, logging, routing, and the device configuration itself.

The vendor position is that risk is reduced by restricting management access to trusted internal IP addresses. That is correct as far as it goes, but it is a containment statement, not a fix. If the management interface is reachable from a compromised IT segment, the control does not apply to your actual exposure.

OT Impact and Compliance Risk

In most process environments the PAN-OS firewall sits at the IT/OT boundary or between zones inside the control network. Root on that device lets an adversary rewrite firewall policy to permit lateral movement into the control zone, disable or blind logging so the intrusion goes unrecorded, and establish persistence on a device that OT teams rarely reimage. The physical consequence is not that the firewall fails in place. It is that the firewall becomes an attacker-controlled pivot sitting inside your most trusted chokepoint, with visibility into engineering traffic and the ability to reroute or drop it.

For NERC CIP environments, a compromised Electronic Security Perimeter device implicates CIP-005 and CIP-007, and loss of logging integrity raises CIP-010 and CIP-008 concerns. For asset owners aligned to IEC 62443, root compromise of a zone conduit enforcement point degrades the foundational requirement for network segmentation and defeats the zone and conduit model. Pipeline operators under TSA SD-02C and water utilities operating under AWIA 2018 obligations should treat a boundary firewall compromise as a reportable network segmentation failure, not a routine patch cycle item.

Compensating Controls

Do not rely on a patch alone, and in OT do not rush active scanning of the management plane to find vulnerable units. Aggressive probing of embedded appliances can disrupt management sessions and management plane services. Build your inventory from configuration records and passive flow data first.

BreachSpider tracks known exploited vulnerability activity and OT-relevant advisories against our catalog of 170,000+ products so your team can monitor exposure like CVE-2026-0322 without touching fragile management planes.