News
Attackers took root on 25 Palo Alto systems with PHP2Shell.
An attacker used two unauthenticated PHP bugs on internet-facing PAN-OS management interfaces, then a Linux kernel flaw, to get root on 24 firewalls and one management server.

Impact
- What was impacted
- PAN-OS management interfaces that embed end-of-life PHP 8.0.30 and 7.4.33, hit through PHP2Shell. CVE-2026-109618 is uninitialized request memory. CVE-2026-109619 is a pointer to freed memory. Both can run code on the web server with no login, while PHP is still parsing the request. Dream, working with Palo Alto Networks, says the actor then used the Linux kernel flaw Fragnesia, CVE-2026-46300, to get root on 25 systems: 24 firewalls and one management server, in the United States, Japan, Taiwan, and South Korea.
- Who was impacted
- Operators of those PAN-OS firewalls and management servers, especially where the management interface is reachable from the internet. The same PHP bugs matter on other appliances that ship one fixed, often outdated PHP build an attacker can study offline. The PHP project rated both flaws 9.2 under CVSS 4.0. Fortinet’s PSIRT listed 9.8 under CVSS v3. Palo Alto first scored its issue 8.7 at moderate urgency, then 9.2 Critical at the highest urgency on October 27, and confirmed exploitation on October 28.
- What you need to do
- Take PAN-OS management interfaces off the internet and limit them to trusted internal addresses. That is Palo Alto’s guidance for this issue. Apply the vendor’s PHP2Shell fixes. Do not treat turning off session upload progress as a fix; PHP core developer Gina Peter Banyard said that workaround is not enough on its own. The report does not name a fixed PAN-OS build or a fixed kernel build, so take those version numbers from the vendor advisories.
Palo Alto Networks confirmed on October 28 that attackers were using CVE-2026-109618 and CVE-2026-109619 against PAN-OS management interfaces exposed to the internet. Both flaws let someone run code on the web server with no account. Details leaked on October 20, ahead of the coordinated release, and the PHP project shipped an emergency patch the next day. The bugs are hard to exploit reliably on an ordinary server. They are more practical on appliances, where every device on a given software version runs the same binaries and an attacker can study them in advance.
Dream, the Israeli firm that investigated alongside Palo Alto Networks, says the attacker got hold of PAN-OS firmware, decrypted it, pulled out the PHP libraries, and prepared memory layouts for nine software versions. The PAN-OS builds in this incident ship end-of-life PHP 8.0.30 and 7.4.33. Address-space randomization still applied. The exploit learned where libphp.so was loaded by reading that base address back from a Set-Cookie header, and SELinux confined the shell it got. The actor then combined PHP2Shell with a Linux kernel flaw called Fragnesia, CVE-2026-46300, and got root on 25 systems: 24 firewalls and one management server, in the United States, Japan, Taiwan, and South Korea.
PHP hits these bugs while it is parsing the request, before any of the application’s own code runs. What trips them is a multipart upload built to exhaust memory. CVE-2026-109618 is request memory PHP never initialized after it aborted. CVE-2026-109619 is a pointer that still refers to memory already freed. Empty file fields nested many levels deep make PHP reserve much more memory than the upload body holds. A request smaller than the default 8 MB post_max_size can still reach the default 128 MB memory limit. VulnCheck’s early look found the bugs usable on ARM64 and on x86 when address-space randomization is off. Few public exploits got past that protection on x86-64, and the one VulnCheck confirmed worked against only one PHP build. Plenty of public proofs of concept failed, so a burst of attempts in the logs does not by itself mean a given server was hit.
Intruder found that nginx in front of PAN-OS buffered chunked request bodies and broke public exploit chains. That is not a control to rely on. A web application firewall is a weak fit, and file upload is normal behavior, so blocking uploads outright is often not an option. Palo Alto’s guidance is to remove internet access to management interfaces and limit them to trusted internal addresses. Turning off session upload progress, an early workaround, is not enough on its own. Scoring moved around: PHP rated both flaws 9.2 under CVSS 4.0, Fortinet’s PSIRT listed 9.8 under CVSS v3, and Palo Alto went from 8.7 at moderate urgency to 9.2 Critical with the highest urgency on October 27, then confirmed exploitation on October 28.
For your AI agent
Agent instructions — copy paste to Claude
You are helping me respond to confirmed exploitation of two unauthenticated PHP flaws, called PHP2Shell, against Palo Alto Networks PAN-OS management interfaces. Do not write or run an exploit or a proof of concept. Facts from the report: - CVE-2026-109618 is uninitialized request memory left when PHP aborts a request. CVE-2026-109619 is a pointer to freed memory. Both can let an unauthenticated attacker run code on the web server. They fire while PHP is parsing a multipart upload, before application code runs. - Details leaked on October 20, 2026. The PHP project shipped an emergency patch the next day. The report does not name the fixed PHP version numbers. - On October 28, 2026, Palo Alto Networks confirmed attackers were using both bugs against PAN-OS management interfaces exposed to the internet. - PAN-OS in this incident ships end-of-life PHP 8.0.30 and 7.4.33. - Dream, working with Palo Alto Networks, says the attacker obtained PAN-OS firmware, decrypted it, extracted the PHP libraries, and built memory profiles for nine software versions. The actor chained PHP2Shell with the Linux kernel flaw Fragnesia, CVE-2026-46300, and got root on 25 systems: 24 firewalls and one management server, in the United States, Japan, Taiwan, and South Korea. SELinux confined the web-server shell before that kernel step. - Palo Alto's guidance: remove internet access to management interfaces and limit them to trusted internal IP addresses. - PHP core developer Gina Peter Banyard said turning off session upload progress is not enough on its own. - The PHP project rated both flaws 9.2 under CVSS 4.0. Fortinet's PSIRT listed 9.8 under CVSS v3. Palo Alto first scored its issue 8.7 at moderate urgency, then 9.2 Critical at the highest urgency on October 27, and confirmed exploitation on October 28. - The report does not name a fixed PAN-OS build or a fixed kernel build. Do not invent those version numbers. - VulnCheck found the bugs usable on ARM64 and on x86 without address-space randomization. Few public exploits bypassed that protection on x86-64. Many public proofs of concept did not work. A flood of attempts in logs does not by itself prove a given host was compromised. - Intruder found that nginx in front of PAN-OS buffered chunked request bodies and broke public exploit chains. Do not treat that buffering as a control that replaces taking the management interface off the internet. Context: - What was impacted: PAN-OS management web interfaces running those PHP builds, and then the host via CVE-2026-46300. - Who should care: operators of PAN-OS firewalls and management servers, especially with management interfaces reachable from the internet, and operators of other appliances that embed a fixed outdated PHP. - What to do: restrict management access as Palo Alto directed, apply the vendor's PHP2Shell fixes, and do not rely on the session-upload-progress workaround. Do this in order. Ask before changing firewall access rules, rebooting devices, or installing updates. Prefer read-only inventory first. Do not write or run an exploit, a proof of concept, or a crafted upload meant to trigger these bugs. 1. Inventory - List PAN-OS firewalls and management servers. Record whether the management interface is reachable from the internet. - Record the PAN-OS and embedded PHP versions if you can read them without changing the device. Flag PHP 8.0.30 and 7.4.33, and any other end-of-life PHP on an appliance. - Note whether Palo Alto's advisory for this issue is already applied. If the advisory in front of you names a fixed PAN-OS build, use that number. If it does not, say the report did not name one. - Do not treat log noise from failed public proofs of concept as proof of compromise, and do not treat a quiet log as proof of safety. 2. Contain - Propose removing internet access to management interfaces and limiting them to trusted internal addresses. Ask before applying the change. - State that disabling session upload progress is not a sufficient workaround. 3. Remediate - Plan the vendor's PHP2Shell fixes for PAN-OS and for any other product in the inventory that the vendor has patched. Ask before installing. - For CVE-2026-46300, use the kernel advisory if you have it. The report names the CVE and does not name a fixed kernel version. Do not invent one. 4. Verify - Confirm management interfaces are no longer reachable from the internet, and that the running PAN-OS build matches the vendor fix you installed. 5. Report back - Devices found, which management interfaces were exposed, what you changed, and anything still unpatched or still internet-facing. Do not invent CVEs, product versions, or exploit conditions. If a check needs access I have not given you, say what you need and stop.