PHP2Shell Exploitation Shows the Web Risk Inside Firewall Management

Palo Alto Networks confirmed that attackers exploited the PHP2Shell vulnerabilities, CVE-2026-109618 and CVE-2026-109619, against PAN-OS management interfaces exposed to the internet. The campaign ultimately gained root access on 25 systems: 24 firewalls and one management server in the United States, Japan, Taiwan and South Korea.
Both vulnerabilities allow unauthenticated code execution on the PHP web server. Although reliable exploitation requires skill and detailed knowledge of a target, the incident demonstrates why network appliances can be especially attractive targets: systems on the same software version commonly run the same binaries and can be studied in advance.
Predictable appliance software changes the exploitation equation
Address space layout randomization, or ASLR, makes exploitation harder on ordinary web servers by changing the memory locations of code and data. VulnCheck found the PHP flaws exploitable on ARM64 systems and on x86 systems without ASLR; its own ASLR-enabled exploit used a memory leak before achieving code execution.
PAN-OS did not simply lack mitigations. In the observed attack, the exploit leaked the libphp.so base address through a Set-Cookie header to work around ASLR, while SELinux confined the initial shell. But the software’s consistency still offered an advantage to a determined attacker. Dream, which investigated with Palo Alto Networks, found that the actor obtained and decrypted PAN-OS firmware, extracted PHP libraries, and created precise memory profiles for nine versions.
The affected PAN-OS software also includes end-of-life PHP releases, specifically PHP 8.0.30 and PHP 7.4.33. After gaining code execution, the actor chained PHP2Shell with the Fragnesia Linux kernel vulnerability, CVE-2026-46300, to obtain root privileges.
HTTP parsing is part of the defensive problem
PHP2Shell is triggered during request parsing, before application code executes. A crafted multipart upload can push PHP beyond its memory limit and leave behind uninitialized request memory in CVE-2026-109618 or a pointer to freed memory in CVE-2026-109619.
The request need not be large. Deeply nested, empty file fields can cause PHP to allocate substantially more memory than the body itself contains, allowing a request below the default 8 MB post_max_size threshold to exhaust the default 128 MB memory limit. This makes protocol-level understanding important when teams assess logs or attempt to build detection signatures.
Intermediary systems can also affect exploit behaviour. Intruder found that nginx placed in front of PAN-OS buffered chunked request bodies, disrupting public exploit chains. That does not make a web application firewall a complete control: uploads are necessary to many applications, and inspection depends on how the intermediary is configured and what it can parse.
Exposure and prioritisation remain the immediate tasks
Risk scoring initially offered inconsistent signals. The PHP project assigned both flaws a CVSS 4.0 score of 9.2, Fortinet PSIRT listed 9.8 under CVSS v3, and Palo Alto first rated the issue 8.7 and moderate urgency before raising it to 9.2 Critical with its highest urgency on October 27. Palo Alto confirmed exploitation a week after its advisory was issued.
Palo Alto’s guidance was to remove internet access from management interfaces and limit them to trusted internal IP addresses. For businesses, the practical implication is to identify every HTTP-based administrative interface on firewalls and other equipment, restrict its exposure, maintain supported software, and validate the real inspection limits of any web application firewall protecting it.

