🔍 Read the full analysis: What AI Assistance Means In The PHP2Shell Palo Alto Server Incident on ThorstenMeyerAI.com
Get business pricing on tech for your team
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
Dream reported that an attacker chained PHP2Shell flaws with a known Linux kernel vulnerability to gain root access on 24 Palo Alto Networks firewalls, then reached a server inside a U.S. government-affiliated network. The company found AI tools on the attacker’s infrastructure but said it has no direct evidence they wrote the exploit or scripts. Palo Alto’s fixes for affected PAN-OS branches shipped October 27–29, after the attacks began.
An attacker exploited PHP2Shell flaws in Palo Alto Networks firewalls and a previously disclosed Linux kernel bug to gain root access on 24 firewalls, according to Israeli security company Dream. The campaign also reached an internal server at a U.S. government-affiliated organization; Dream found AI tools on the attacker’s infrastructure but said it has no direct evidence they were used to write the exploit.
Dream’s account, published October 26 and updated October 29, says the attacker ran an automated batch against 240 firewalls on October 23, about two days after fixes for the underlying PHP flaws were released by the PHP project. The campaign targeted systems in the United States, Japan, Taiwan and South Korea. Dream said 24 firewalls were rooted, and 22 were left with a hidden web shell. Palo Alto Networks said its Unit 42 researchers independently verified the attacker’s tools and results.
The attack combined PHP2Shell vulnerabilities CVE-2026-109618 and CVE-2026-109619 with Fragnesia, a Linux kernel privilege-escalation flaw, CVE-2026-46300, disclosed in May. Dream says PHP2Shell enabled command execution on the firewall’s management web server, while Fragnesia was used to gain administrator-level, or root, access. Dream estimates the chain could be completed in under 15 minutes.
Dream says the attacker used two compromised firewalls belonging to the government-affiliated organization to reach its internal firewall-management server, the 25th server compromised. The attacker then targeted the organization’s Active Directory, which manages access and user accounts. Dream’s report describes the attack sequence; the supplied material does not establish what data, if any, was accessed or removed.
Dream also reported finding Claude Code installed on the attacker’s servers and DeepSeek and Kimi configured in an offensive-security platform called aiscan. The company said those findings do not prove the tools generated the exploit or scripts, and characterized the operation as not appearing to be fully autonomous.
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 Pages Enabled Access
The incident shows how internet-accessible management interfaces can turn a newly disclosed software flaw into a rapid compromise. A firewall is meant to control network access, but its administration page can itself become an entry point if exposed to the public internet and left vulnerable. Dream said it identified about 19,000 PAN-OS firewalls with internet-facing management pages before narrowing its scan to the 240 systems attacked. That figure describes exposed devices observed in Dream’s research, not confirmed victims.
The reported move from firewalls into an organization’s internal management server and Active Directory raises the potential impact beyond the perimeter device. Those systems can affect access to other infrastructure, though Dream’s account does not specify the extent of any resulting access or damage. The presence of AI tools is relevant to how investigators assess attacker capability, but the evidence described so far supports a more limited conclusion: tools were present, while their contribution to the operation is unknown.
Products Worth Considering
Samsung 27-inch Odyssey OLED G6 QD-OLED QHD Gaming Monitor
DJI Mic 3 Wireless Microphone System (2 Transmitters, 1 Receiver, Charging Case)
LG UltraGear 32GX850A-B 32-Inch 4K UHD Glossy OLED Gaming Monitor
As an affiliate, we earn on qualifying purchases.
Patches Followed the Initial Disclosure
The PHP project released updates on October 21 for the PHP2Shell flaws. Palo Alto Networks published an advisory the same day, but Dream said fixed PAN-OS builds for the affected 12.1 and 12.2 branches were not available until October 27–29. Dream reported that PAN-OS included its own copy of PHP, identified in its research as version 8.0.30. Until fixed builds were available, Palo Alto’s stated protection was to keep the management interface off the internet.
The second vulnerability in the chain, Fragnesia (CVE-2026-46300), was disclosed in May with a public exploit and a kernel fix, according to the source material. Dream’s timeline says the attacker set up aiscan with DeepSeek and Kimi on October 8. It also says the attacker identified exposed firewalls using FOFA, a search engine for internet-connected devices, then filtered a larger set of possible systems by version and country before launching the batch.
On October 26, the U.S. Cybersecurity and Infrastructure Security Agency added both PHP2Shell CVEs to its Known Exploited Vulnerabilities catalog and set a three-day deadline for federal agencies, according to the supplied account. The reported attacks began before Palo Alto’s fixed builds for the affected branches shipped, underscoring the gap between a vulnerability disclosure and a vendor patch becoming available for a particular product.
““We have no direct evidence” that AI tools wrote the exploit or scripts.”
— Dream
AI Use and Intrusion Impact Remain Unknown
The key unresolved issue is what the AI tools actually did. Dream found Claude Code and configurations for DeepSeek and Kimi, but said it had no direct evidence that they produced the exploit, attack scripts or other components. Their presence alone does not show that AI generated the attack chain, nor that the operation was autonomous.
The supplied account also does not establish what information or systems were accessed after the attacker reached the internal management server and targeted Active Directory. It is not clear whether data was taken, whether additional accounts or systems were compromised, or whether all hidden web shells and other persistence mechanisms have been removed. The number of organizations affected beyond the 24 rooted firewalls and the one internal server described by Dream is also not stated.
Dream’s findings are a company’s incident report, while Palo Alto said its researchers independently verified the attacker’s tools and results. The material provided does not include a detailed public forensic account from the government-affiliated organization or a complete vendor assessment of the campaign’s impact.
Patch, Restrict, and Review Access
Organizations using affected PAN-OS branches should check Palo Alto Networks’ current security guidance and install the fixed builds applicable to their systems. Where updates cannot be applied immediately, the reported interim measure is to prevent public access to the management interface and limit administration to trusted networks. Teams should also check whether their devices ran vulnerable versions during the campaign window.
Security teams should review firewall logs and administrative activity for signs of unauthorized access, and investigate whether an exposed firewall could have provided a route to internal management systems or identity services. A patch does not by itself establish that a previously compromised device is clean; affected organizations need to assess persistence and account integrity using their incident-response procedures.
Further updates from Dream, Palo Alto Networks, CISA or the affected organization may clarify the scope of the intrusion and whether AI tools contributed to the attack. For now, the clearest confirmed lesson is operational: the campaign exploited known flaws on devices with exposed management access, while the claimed AI connection remains an inference rather than proof.
Key Questions
What happened in the PHP2Shell incident?
Dream reported that an attacker combined two PHP2Shell vulnerabilities with the Linux kernel flaw Fragnesia to gain root access on 24 Palo Alto firewalls. The attacker also reached an internal firewall-management server at a U.S. government-affiliated organization.
Has it been proven that AI wrote the attack tools?
No. Dream found AI tools on the attacker’s infrastructure, including Claude Code and configurations for DeepSeek and Kimi, but said it had no direct evidence they wrote the exploit or scripts.
How did the attacker gain root access?
According to Dream, PHP2Shell allowed command execution on the firewall’s management web server, and the Fragnesia kernel vulnerability was then used to escalate privileges. The reported targets had management pages accessible from the internet.
What should organizations using PAN-OS do?
Organizations should install the fixed PAN-OS builds for their affected branches, restrict management interfaces from public internet access, and review devices for signs of compromise. They should also investigate whether firewall access could have led to internal systems.
How many systems were reported compromised?
Dream reported 24 rooted firewalls and one internal management server, for 25 servers in total. It said the targets were in four countries; the supplied report does not give a broader confirmed count of affected organizations or systems.
Source: ThorstenMeyerAI.com
