#panos

Read Time:3 Minute, 58 Second

Palo Alto Networks has confirmed that a pair of critical remote-code-execution flaws in the PHP language runtime extend into its own PAN-OS firewall software and Panorama management platform, and that fixes won’t be fully available for roughly a week after the advisory update.

The two issues, tracked as CVE-2026-109618 and CVE-2026-109619, stem from how PHP handles severe internal errors through a function called longjmp(), which abruptly jumps program execution back to an earlier saved checkpoint. When that jump happens at the wrong moment, it can leave stale or uninitialized memory behind — memory that a later part of the program may then act on, opening a path for an attacker to run their own code.

Two Related but Distinct FlawsCVE-2026-109618 is triggered when the server runs out of memory partway through handling a request, leaving that request’s memory in an incomplete state. If cleanup routines later operate on that incomplete memory, an attacker who can reliably force memory exhaustion may be able to turn the resulting instability into remote code execution.

CVE-2026-109619 is a related but separate issue involving global memory references that continue pointing at memory after it has already been freed. A subsequent request that reads or acts on one of those dangling references can again give an attacker a route to execute arbitrary code.

Both flaws trace back to the broader PHP vulnerability research effort published under the name “PHP2Shell,” which carries a CVSS v4.0 base score of 9.2. Palo Alto has assessed its own product-specific exposure slightly lower, at 8.7, and notes that for its products the primarily affected security property is availability rather than confirmed data theft or configuration tampering — though the company is careful to frame that as the current assessment, not a guarantee against more severe impact.

Scope: Management Interfaces, Not GlobalProtectAccording to the updated advisory, the vulnerable surface is limited to PAN-OS management interfaces — the HTTPS administrative console and the XML API — rather than the data-plane components most organizations expose to end users. A dataplane interface is only affected if it has a management profile explicitly attached to it. Notably, GlobalProtect portals and gateways, Clientless VPN, and Captive Portal are all listed as unaffected, which should reduce panic for organizations whose remote-access infrastructure runs through those services.

Affected branches span a wide swath of PAN-OS releases, including 10.2, 11.1, 11.2, 12.1, and 12.2, running on PA-Series and VM-Series firewalls, as well as Panorama (including virtual and M-Series deployments). No unusual configuration is required to be vulnerable — any device on an affected branch with its management interface reachable is a candidate for exploitation.

Two cloud-delivered products, Cortex XCORE SaaS and WildFire Cloud, were also affected but have already received fixes, delivered on October 21 and October 22 respectively. Cloud NGFW, Cortex XDR, Cortex XSIAM, Prisma Cloud, Prisma Access, and the GlobalProtect App are all currently listed as unaffected by this issue.

Patches Are Still ComingAs of the October 24 advisory update, Palo Alto said it has no evidence of malicious exploitation against its own products — but that comes with an important caveat: security researchers at Unit 42 have already observed proof-of-concept exploit code circulating for the broader PHP2Shell vulnerabilities, meaning the gap between disclosure and active abuse could close quickly.

Firmware fixes are still on a rolling schedule rather than available today. The earliest hotfixes — versions 10.2.18-h13, 11.1.16-h4, and 11.2.10-h16 — are estimated for October 26, with PAN-OS 12.2.4-h1 targeted for October 28 and additional hotfixes planned through October 30. Palo Alto has emphasized that these dates are estimates and may shift.

What Administrators Should Do NowRestrict access to PAN-OS and Panorama management interfaces to trusted internal IP ranges or a dedicated jump host — internet-facing management interfaces represent the highest-risk configuration.

Where possible, enable Threat Prevention coverage for this issue, which Palo Alto has tied to signature 543004 and subsequent content updates (versions 9162 through 9164 and later). Doing so requires routing management traffic through a dataplane port, configuring an inbound certificate, and enabling HTTPS decryption and inspection.

Track each affected device’s specific hotfix path against Palo Alto’s advisory and Unit 42’s threat brief, since release timing varies by branch.

Treat access restrictions as a stopgap, not a substitute for installing the fixed release once it becomes available for each platform.

The disclosure is a reminder that vulnerabilities in widely used runtimes like PHP don’t stay contained to web applications — they can resurface inside the management stacks of the very security appliances organizations rely on to keep attackers out.

Read Time:3 Minute, 27 Second

Palo Alto Networks has disclosed an actively exploited PAN-OS vulnerability that can give a privileged attacker root-level code execution on affected firewalls. The flaw, tracked as CVE-2026-0322, targets the management interface and has received a CVSS 4.0 score of 8.6. The company describes observed exploitation as very limited, but has assigned its highest remediation urgency and advises customers to upgrade without delay.

The disclosure matters because a firewall is a central enforcement point for network traffic. Root access to the appliance can give an intruder exceptional visibility and control, potentially allowing configuration changes, persistence, or interference with security monitoring. Palo Alto Networks has not attributed the activity or said how many organizations were targeted.

How the PAN-OS flaw worksCVE-2026-0322 is a code-injection weakness classified as CWE-94. Exploitation requires network access to the PAN-OS management interface as well as an authenticated account with high privileges. A successful attacker can execute code as root without further user interaction.

Those prerequisites make this different from an unauthenticated internet-wide compromise. However, they do not make the issue harmless. Stolen administrator credentials, an insider, or an attacker who has already established a foothold could use the bug to turn limited access into full control of a security appliance. Internet-exposed management interfaces face the clearest risk.

Affected platforms include PA-Series hardware firewalls, VM-Series virtual firewalls, and Panorama on virtual systems or M-Series appliances. Palo Alto Networks says Cloud NGFW and Prisma Access are not affected. No unusual configuration is required for a vulnerable installation to be exposed to the weakness.

Fixed releases and affected branchesCustomers should consult the vendor advisory for the exact upgrade path for their branch. Fixed releases identified by Palo Alto Networks include:

PAN-OS 12.2.4;

PAN-OS 12.1.10-h2;

PAN-OS 11.1.16-h3;

PAN-OS 10.2.18-h12;

selected 11.2 hotfixes, including 11.2.4-h22, 11.2.7-h21, 11.2.10-h15, and 11.2.13-h3.

The vendor says there is no workaround that eliminates the flaw. Restricting the management interface to trusted internal addresses and reaching it through a hardened jump host can reduce exposure, but those controls are not substitutes for installing a corrected build.

Before upgrading, operators should back up the current configuration and follow the normal high-availability sequence so paired devices do not lose protection at the same time. Afterward, verify the reported software version, confirm that policy synchronization and traffic processing are healthy, and record the change in the asset inventory. Any appliance that cannot be patched immediately should have management access reduced to the narrowest possible set of source addresses and monitored continuously until remediation is complete.

What defenders should investigatePalo Alto Networks linked three IP addresses to threat activity and limited exploit attempts: 66[.]42[.]72[.]14, 208[.]83[.]239[.]114, and 149[.]248[.]47[.]234. Security teams should search firewall management and upstream network logs for connections involving those addresses, while remembering that attackers can change infrastructure and that an indicator match is not required for compromise.

Defenders should also review administrator logins, unexpected configuration changes, newly created accounts, unusual processes, and management traffic from hosts that do not normally administer the appliance. Where possible, compare local evidence with independent logging because an attacker operating as root may be able to alter records on the device.

Priorities for firewall ownersOrganizations should inventory every physical firewall, virtual instance, and Panorama deployment, including disaster-recovery and lab systems that may still be reachable. Confirm the running version rather than relying on asset records, then apply the vendor-recommended fixed release. Management access should be limited to a small group of dedicated administrative systems protected with strong authentication.

Finally, teams should treat patching and compromise assessment as parallel tasks. Installing an update closes the known route but does not prove that earlier exploitation did not occur. Because the vulnerable component protects the network itself, any suspicious evidence deserves a broader incident-response review of credentials, configurations, and traffic that passed through the device.