~/f4n6 $ grep -r "Everyone's patching their web servers. Here's the PAN-OS angle on PHP2Shell" ./investigations/ --include="*.md"
php2shell

Everyone's patching their web servers. Here's the PAN-OS angle on PHP2Shell

Jeff Davies 26 Oct 2026 4 min read

Everyone is patching their web servers. Very few people have looked at the appliance.

PHP2Shell is a pair of remote-code-execution bugs in PHP itself: CVE-2026-109618 (OOM corruption) and CVE-2026-109619 (stale global state). Patches landed on 21 October in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Most coverage since then has been web-hosting-centric: WordPress estates, PHP-FPM fleets, WAF rules, reverse-proxy detections. Those are the right priorities for most exposed PHP.

But this is not only a web-server problem. Palo Alto Networks confirmed that PAN-OS and Panorama are affected by both CVEs, with no special configuration required to be affected. The appliance ships its own embedded PHP. You cannot fix it by updating a PHP package or a container. It moves when Palo Alto ships a maintenance release, and only then.

What is actually exposed on PAN-OS

  • In scope: the management web interface and the management XML API, which serve the browser UI and API on the firewall's management plane.
  • Not in scope: GlobalProtect portal and gateway, clientless VPN, and Captive Portal are not impacted. The data-plane PHP services (Path A and Path B) are also unaffected.
  • Reachability is the deciding factor. An internet-reachable management interface on an affected build is a high-risk asset. An internal-only management interface remains vulnerable, but the attack surface is much smaller.

Palo Alto rates the product impact CVSS-B 8.7 (HIGH) with suggested urgency MODERATE. That is lower than the upstream PHP ratings: NVD scores CVE-2026-109618 9.8 and CVE-2026-109619 8.1, and the PHP project rates each at 9.2. Quote the per-CVE numbers rather than a blanket "critical". The same care applies to the PAN-OS advisory: 8.7 is the product score, not a statement that the bugs are mild.

Fix status by branch, 26 October

Seven maintenance releases are available now. Thirteen more are scheduled between 27 and 30 October. Panorama, and the WildFire WF-500 and WF-500-B appliances, have no announced fix date.

BranchReleasedPending (ETA)
PAN-OS 10.210.2.18-h13 (25 Oct)10.2.13-h27 (27 Oct) · 10.2.16-h12 (28 Oct) · 10.2.10-h42 (29 Oct) · 10.2.7-h39 (30 Oct)
PAN-OS 11.111.1.16-h4 (25 Oct) · 11.1.4-h38, 11.1.6-h40, 11.1.10-h36, 11.1.13-h16 (26 Oct)11.1.7-h12 (30 Oct)
PAN-OS 11.211.2.10-h16 (25 Oct)11.2.13-h4 (27 Oct) · 11.2.16-h1 (28 Oct) · 11.2.7-h23 (29 Oct) · 11.2.4-h23 (30 Oct)
PAN-OS 12.1not yet released12.1.7-h11 (28 Oct) · 12.1.4-h13 (29 Oct) · 12.1.10-h3 (30 Oct)
PAN-OS 12.2not yet released12.2.4-h1 (28 Oct)
Panorama, WF-500, WF-500-Bnot yet releasedno fix date announced

Always confirm against Palo Alto's advisory rather than this table: security.paloaltonetworks.com/CVE-2026-109618. Read its Timeline section, because that is where "released" and "ETA removed" statements live. The Solution text can lag behind reality.

If your branch has a release: upgrade, then re-check exposure

The patch closes the vulnerability. It does not undo a compromised management plane. After upgrading, re-verify the management interface's exposure and review whether anything reached it. PAN-OS is a security control, so a compromise here has a different consequence class from a compromised web host.

If your branch is still pending: interim controls

  1. Restrict management-plane access to trusted networks. This is the single most useful control while you wait, and Palo Alto frames risk as highest when the management interface is exposed.
  2. Route management traffic through a data-plane port, replace the inbound management certificate, and decrypt inbound traffic to the management interface. Then enable Threat Prevention on management services. Without that chain, the signatures cannot see the traffic they are meant to inspect.
  3. Enable Threat Prevention IDs 543004 and 97622 to 97678 (25 IDs in total). On PAN-OS 12.2.4 and later, Frontier Virtual Patching via Threat ID 543004 gives earlier coverage.
  4. Panorama and WF-500: there is no fix date, so keep management access tightly restricted and treat these appliances as exposed until a release lands.

Industrial knock-on. Siemens published SSA-566512 on 23 October. RUGGEDCOM APE1808 devices hosting PAN-OS are affected across all listed branches, and remediation is through customer support rather than self-service. That is the route by which an IT appliance CVE reaches OT estates.

Detection: the boundary is the signal

There is no payload string to match. The exploit is a condition, not a signature. Fastly's analysis of roughly 250,000 requests found the most reliable discriminator is the fixed or patterned multipart boundary in the Content-Type header, because each kit hardcodes its own. User-Agent, IP blocklists and body-size thresholds are demonstrably unreliable. A third of PHP2Shell-named traffic is defensive scanning, and circulating IP lists include VPN and Tor exits.

That matters more on PAN-OS than on a busy web farm. Management-plane HTTP traffic is low-volume and predictable, so a multipart POST of the wrong shape stands out. Our detection package ships boundary-first Suricata rules (kit boundary B7kQpoc618, and fixed single-character boundaries such as the public tool's CCCCCCCCCC), plus look-alike exclusions and hunting queries keyed on the same logic.

Remember that a successful attempt and a failed one look identical at the edge. Confirmation lives on the origin: PHP error logs, Apache worker crashes such as AH00051, and unexpected outbound connections from web workers.

What we can and cannot tell you

Calibrated status, as of 26 October:

  • Verified: PAN-OS and Panorama are affected; the affected and not-affected product split above; the released and pending builds; the Threat Prevention IDs; the Siemens advisory.
  • Unconfirmed: any public report of in-the-wild exploitation of the PAN-OS management plane through these CVEs. We are not aware of one, and absence is not safety.
  • Retracted claim: the widely reported "European government intrusion tied to PHP2Shell" was retracted by its publisher on 25 October. An attack occurred in a vulnerable PHP-application context, but attribution to these CVEs could not be confirmed. Treat single-source victim claims as unverified.
  • Directional, not per-host: EPSS for both CVEs is near-certain, which reflects broad exploitation likelihood. It is not a verdict on your estate.

Where to get the material

Detection rules, hunting queries, the PAN-OS exposure and patch-availability detail, and the full source-cited dossier are at github.com/CypherSecurity/php2shell-detection. The continuously updated advisory is at f4n6.co.uk/php2shell.

Status as of 26 October 2026. For current patch status see the continuously updated advisory at f4n6.co.uk/php2shell. Written and maintained by f4n6, independent security research. Corrections welcome.

Post this to LinkedIn
Formatting is converted automatically — headings, bullets, a link back & hashtags. Paste straight in.
J
Jeff Davies