🔍 Read the full analysis: How PHP2Shell Took Over Palo Alto Servers—and What AI Had To Do With It on ThorstenMeyerAI.com
Get business pricing on monitors, keyboards and dev gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
Dream says an attacker used two PHP2Shell vulnerabilities and a previously disclosed Linux kernel flaw to gain root access to 24 Palo Alto Networks firewalls, then reached a government-affiliated network’s firewall management server. Dream found AI tools on the attacker’s infrastructure but says it has no direct evidence that AI wrote the exploit or scripts. Palo Alto’s fixes for the affected PAN-OS branches shipped between October 27 and 29, according to the supplied report.
Dream, an Israeli AI security company, says an attacker gained root access to 24 Palo Alto Networks firewalls after chaining two newly fixed PHP flaws with a previously disclosed Linux kernel vulnerability. The activity began on October 23, about two days after the PHP project released fixes; Dream says the attacker later used compromised firewalls to reach a US government-affiliated network and take control of an internal server managing its firewalls.
Dream published its account on October 26 and updated it on October 29. It says the attacker ran an automated batch against 240 selected firewalls and rooted 24. The targets were in the United States, Japan, Taiwan and South Korea. Dream reports that 22 of the compromised firewalls were left with hidden web shells, while two belonged to the government-affiliated organization. The account describes a further compromise inside that organization, bringing the reported total to 25 servers: 24 firewalls and one internal management server.
According to Dream, the attacker combined PHP2Shell vulnerabilities CVE-2026-109618 and CVE-2026-109619 with Fragnesia, a Linux kernel privilege-escalation flaw identified as CVE-2026-46300. Dream says PHP2Shell provided command execution under a low-privilege account on the firewall’s management web server; Fragnesia was then used to gain root access. The company says the chain, including installation of a persistent back door, took less than 15 minutes. These are reported findings, not a general claim that every vulnerable firewall was compromised.
Palo Alto Networks said its Unit 42 researchers independently verified the attacker’s tools and results. The supplied account says the company issued an advisory on October 21, while fixed builds for the affected PAN-OS 12.1 and 12.2 branches arrived between October 27 and 29. Until those builds were available, Palo Alto’s stated protective measure was to keep the management interface off the public internet. The US Cybersecurity and Infrastructure Security Agency added both PHP2Shell vulnerabilities to its Known Exploited Vulnerabilities catalog on October 26 and gave federal agencies three days to address them, according to the source material.
Infographic 01 · PHP2Shell on Palo Alto firewalls
Two days from patch to root.
PHP fixed the bug on 21 October. Fixed firewall software for the attacked branches arrived almost a week later. The attack ran in between.
- 13–23 MayFragnesia goes public, kernel fix followsLinux privilege-escalation bug with a public exploit; CVE-2026-46300.
- 8 OctAttacker sets up an AI platformaiscan configured with DeepSeek and Kimi, per Dream’s timeline.
- 21 OctPHP fixes PHP2ShellPHP 8.5.12, 8.4.27, 8.3.36, 8.2.35. Palo Alto advisory the same day; PAN-OS fixes “upcoming”.
- 23 Oct, evening UTCBatch run: 240 targets, 24 rootedFound via device search engine, filtered to US, Japan, Taiwan, South Korea.
- 24 OctInto a government-affiliated networkTunnel, persistence, internal management server rooted (no. 25), Active Directory attacked.
- 26 OctDream publishes · CISA lists PHP2ShellFederal deadline 29 Oct.
- 27–29 OctFixed PAN-OS builds for 12.2 and 12.1CISA lists Fragnesia on 28 Oct; Unit 42 confirms Dream’s results on 29 Oct.
The fix for PHP existed. The fix for the firewall did not, yet. The open management page was the only door that mattered.Thorsten Meyer · my reading
Sources: Dream Research, 26 Oct 2026 (updated 29 Oct); php.net, 21 Oct 2026; Palo Alto Networks advisory (updated 29 Oct 2026); CISA KEV catalog, version 29 Oct 2026; oss-security, 13 May 2026; Unit 42, 29 Oct 2026. Day count: Thorsten Meyer.
Powered by Thorsten Meyer AI
Exposed Management Interfaces Enabled Access
The report shows how an internet-accessible firewall management interface can turn a software vulnerability into a route toward broader organizational systems. Firewalls are designed to control network traffic, but their administrative interfaces carry powerful access. Compromising one can give an intruder a foothold from which to target internal infrastructure, as Dream says happened when the attacker reached the organization’s central firewall management server.
The timing also matters. The PHP project had released fixes, but according to the supplied account, PAN-OS builds incorporating the fixes for the affected branches were not available until several days later. During that gap, limiting access to management pages was the stated protection. Organizations using affected systems should check vendor guidance, update to applicable fixed builds and restrict administrative access to trusted networks. Dream’s report does not establish that all exposed devices were vulnerable or that all vulnerable devices were attacked.
Products Worth Considering

Samsung Odyssey OLED G8 34-Inch Curved Ultra WQHD Gaming Monitor

LG 27GS60QC-B Ultragear 27-inch Curved Gaming Monitor (QHD, 180Hz, 1ms, 1000R)

LG UltraGear 34-Inch Curved QHD Gaming Monitor, 160Hz, FreeSync Premium
As an affiliate, we earn on qualifying purchases.
From PHP Fixes to Firewall Patches
PHP2Shell refers here to two vulnerabilities in PHP components included with PAN-OS. Dream says the firewalls used a vendor-shipped copy of PHP 8.0.30, so updating a separate PHP installation would not necessarily update the component inside PAN-OS. The PHP project released updates on October 21; Palo Alto published its advisory that day and described PAN-OS fixes as forthcoming, according to the supplied material.
The second flaw, Fragnesia, was disclosed in May 2026 with a public exploit and a kernel fix, the source says. Dream’s timeline says the attacker set up an offensive-security platform called aiscan on October 8, with the models DeepSeek and Kimi configured. Before the firewall attacks, the attacker reportedly identified about 19,000 PAN-OS devices with internet-facing management pages, obtained version information from roughly 5,000, then narrowed the pool to 240 targets. Those counts describe Dream’s account of the attacker’s reconnaissance, not confirmed compromises.
“It has “no direct evidence” that AI tools wrote the exploit or the scripts.”
— Dream
AI’s Role Remains Unproven
Dream found the coding assistant Claude Code installed on the attacker’s servers and DeepSeek and Kimi configured in aiscan. It says, however, that it has no direct evidence AI wrote the exploit or scripts and that the operation did not appear fully autonomous. The available evidence therefore supports saying AI tools were present, not that AI created or independently executed the attack.
The supplied account does not identify the attacker or establish the full extent of activity after the Active Directory systems were targeted. It also does not say whether the attacker successfully changed directory accounts or accessed particular government data. The impact on the organization, the status of its systems, and whether other victims were affected remain unclear in the material provided.
Patch Status and Investigation Updates
Organizations running affected PAN-OS branches should follow Palo Alto Networks’ current advisories, install the fixed builds applicable to their systems and keep management interfaces restricted from public access. Federal agencies were given a three-day remediation deadline after CISA added the vulnerabilities to its catalog, according to the source. The supplied report does not provide a later compliance figure or a complete list of systems still exposed.
Further public reporting from Dream, Palo Alto Networks or the affected organization could clarify whether the Active Directory attack succeeded, what information or systems were accessed, and whether the attacker’s infrastructure used AI tools during any specific part of the operation. Until such details are available, the confirmed distinction is between AI tools found on the attacker’s servers and an unproven claim that AI built or ran the exploit chain.
Key Questions
What was PHP2Shell used for in this attack?
Dream says the attacker used the two PHP2Shell vulnerabilities to run commands on affected firewall management servers, then chained them with the Fragnesia Linux kernel flaw to gain root access.
How many servers were compromised?
Dream reports 24 compromised Palo Alto firewalls and one internal firewall management server reached through a government-affiliated organization’s network, for a reported total of 25 servers.
Did AI create the exploit?
That has not been established. Dream found Claude Code, DeepSeek and Kimi on or configured in the attacker’s environment, but said it had no direct evidence that AI wrote the exploit or scripts.
What should organizations do?
Organizations should apply the fixed PAN-OS builds specified in Palo Alto Networks’ advisories and restrict firewall management interfaces to trusted networks. The source account says keeping those interfaces off the internet was the protection advised while fixes were pending.
Source: ThorstenMeyerAI.com
