Executive Summary

CVE-2026-0329 is a buffer overflow in Palo Alto Networks PAN-OS software that lets an unauthenticated attacker trigger a denial of service by sending crafted network traffic to or through a dataplane interface. In an OT environment, a firewall that enforces the boundary between enterprise and process networks is a single point of failure, and loss of that device means loss of segmentation enforcement, inspection, and in some topologies connectivity itself.

Technical Exposure Breakdown

The vulnerable component is the PAN-OS dataplane, the forwarding path that processes packets as they transit the appliance. The flaw is reachable both by traffic destined to a dataplane interface and by traffic passing through the device. That distinction matters. A through-path trigger means the attacker does not need a session to a management address or a published service. Traffic that merely traverses the firewall on an allowed path can carry the malformed condition.

The attack vector is network based and requires no authentication. According to the grounding data, Cloud NGFW and Panorama are not affected, which narrows the scope to on-premise PAN-OS enforcement appliances rather than cloud enforcement or centralized management. No CVSS score, affected version list, or patch status is confirmed in the grounding data, so treat version applicability and fix availability as open items to be verified against the vendor advisory before you plan remediation.

The observed impact is denial of service. For a buffer overflow this is the floor, not necessarily the ceiling. Memory corruption conditions often start as reliable crashes and are later refined. Plan on the assumption that a reliable DoS against a border enforcement device is itself a severe operational event, independent of any future escalation.

OT Impact and Compliance Risk

PAN-OS appliances are commonly deployed at the IT and OT boundary and at conduit chokepoints inside the industrial zone model. A dataplane crash does not corrupt a PLC, but it removes the control that keeps unvetted traffic out of the process network. Depending on your failure mode, the device either fails closed and severs north-south connectivity, or it reboots and leaves a window of degraded inspection. Neither outcome is acceptable during active operations.

For NERC CIP registered entities, loss of the Electronic Security Perimeter enforcement point touches CIP-005 and, if the device is a monitored asset, CIP-007 availability and logging expectations. Under IEC 62443, the firewall is a zone boundary and conduit enforcement mechanism, so a repeatable crash undermines the foundational requirements for zone separation. Pipeline operators under TSA SD-02C should treat a crashable boundary device as a direct hit to the network segmentation and access control measures the directive mandates. Water and wastewater utilities evaluating risk under AWIA 2018 should document this as a loss-of-segmentation scenario in their resilience assessment.

Compensating Controls

Do not run an active vulnerability scan against production PAN-OS appliances to confirm exposure. Scanning traffic through a dataplane that is vulnerable to a crafted-packet overflow can trigger the very condition you are trying to measure, and in OT contexts that means an unplanned outage. Use passive inventory and configuration review instead.

BreachSpider tracks exploitation signals and KEV program movement for boundary enforcement platforms like PAN-OS, so monitor Intel by BreachSpider for status changes on CVE-2026-0329 before you commit a maintenance window.