🔍 Read the full analysis: Two Days From Patch To Root: How A PHP2Shell Chain Took Over 25 Palo Alto Servers, And What “AI-Assisted” Really Means on ThorstenMeyerAI.com
Get privacy and security gear delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
TL;DR
Dream reported that an attacker used PHP2Shell and a previously disclosed Linux kernel flaw to gain root access to 24 Palo Alto Networks firewalls, then reached a 25th server on a U.S. government-affiliated network. Palo Alto Networks says its Unit 42 researchers independently verified the tools and results. AI tools were found on the attacker’s systems, but Dream says there is no direct evidence they created the exploit.
An attacker gained root access to 24 Palo Alto Networks firewalls and used access to a U.S. government-affiliated network to compromise a 25th server, according to Israeli security company Dream. The reported attacks began about two days after fixes for two PHP vulnerabilities were released; Palo Alto Networks says its Unit 42 researchers independently verified the attacker’s tools and results.
Dream’s account says the attacker targeted 240 firewalls on October 23 and successfully obtained root privileges on 24. The targets were in the United States, Japan, Taiwan and South Korea. Dream says 22 of the compromised firewalls were left with hidden web shells, while two belonged to a U.S. government-affiliated organization. Access to those devices was then used to reach an internal firewall-management server, bringing the reported total to 25 compromised servers.
The attacker combined the PHP vulnerabilities known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619) with Fragnesia (CVE-2026-46300), a previously disclosed Linux kernel vulnerability. Dream says PHP2Shell provided initial command execution on the firewall, while Fragnesia enabled the attacker to raise privileges to root. The report says the attacker then established persistent access and targeted the organization’s Active Directory, which controls access to accounts and systems.
PHP released fixes on October 21, and Palo Alto Networks published an advisory that day. However, Dream says fixed PAN-OS builds for the affected 12.1 and 12.2 branches did not ship until October 27–29. Until those builds were available, Palo Alto’s stated mitigation was to keep the firewall management interface off the public internet. Dream estimates that the attack chain, including establishing a persistent back door, could take under 15 minutes; that timing is the company’s assessment.
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 Raised Risk
The reported intrusions show how quickly newly disclosed flaws can be used against devices that expose their administrative interfaces to the internet. A firewall is intended to control network access, but compromise of its management system can give an attacker a route to persistent access and, as Dream reports in this case, a path toward internal infrastructure.
The incident also highlights the risk of combining a fresh vulnerability with an older, already disclosed flaw. Fragnesia had been made public months earlier, according to Dream’s timeline. The chain’s reported success depended not just on the PHP fixes, but on reachable management pages and a second vulnerability that could raise privileges. For organizations, keeping management interfaces restricted and applying vendor fixes promptly can limit exposure when patches are not yet available.
Dream says the attacker attempted to access Active Directory after reaching the internal management server. The report does not establish the full impact on the organization’s identity systems or whether data was taken. The known server count and the attempt to reach identity infrastructure make the incident a warning about the potential reach of a firewall compromise, not proof that every downstream system was breached.
Products Worth Considering
LG UltraGear 27G640A-B 27-Inch QHD IPS Gaming Monitor, 300Hz, 1ms, G-SYNC Compatible, FreeSync Premium, DisplayHDR 400
LG 24G414B-B 24-Inch UltraGear Full HD IPS Gaming Monitor
LG UltraGear 32GX850A-B 32-Inch 4K UHD Glossy OLED Gaming Monitor
As an affiliate, we earn on qualifying purchases.
Patches Followed October 21 Disclosure
PHP published updated releases on October 21, 2026, addressing the two PHP2Shell vulnerabilities. Palo Alto Networks issued an advisory on the same date, but the fixed PAN-OS builds for the affected 12.1 and 12.2 branches arrived later, between October 27 and 29, according to Dream’s account. Dream says the firewalls use a Palo Alto-distributed copy of PHP, rather than relying solely on an administrator updating a separate PHP installation.
Fragnesia, the kernel vulnerability used for privilege escalation, had been disclosed in May with a public exploit, according to the source account. Dream says its researchers identified the attacker’s artifacts on October 25 and published their findings the following day. The U.S. Cybersecurity and Infrastructure Security Agency added both PHP2Shell vulnerabilities to its Known Exploited Vulnerabilities catalog on October 26 and set a three-day remediation deadline for federal agencies, according to the supplied material.
Dream describes a funnel from roughly 19,000 internet-facing management interfaces identified through the FOFA search engine, to about 5,000 devices that responded to a custom scanner, and then to 240 targets selected by country and software version. These are figures in Dream’s account, not a count of all vulnerable or compromised firewalls worldwide.
“The company said it had “no direct evidence” that AI tools wrote the exploit or scripts.”
— Dream
AI Role and Full Impact Unclear
The presence of Claude Code and configurations for the DeepSeek and Kimi models on attacker systems does not show that those tools wrote or tested the exploit. Dream explicitly says it has no direct evidence of AI-generated attack code and does not characterize the operation as fully autonomous. The label “AI-assisted” should therefore be understood as a description of tools found, not a confirmed account of how the attack was developed or run.
The supplied reporting does not establish whether information was exfiltrated, how much of the organization’s Active Directory was affected, or whether the attacker accessed other internal systems. It also does not say whether all 24 firewall owners were identified or whether every compromised device was cleaned and restored. The reported 25 servers are the devices Dream says were compromised in this campaign, not a verified global total.
Dream reports that Palo Alto firewalls did not receive fixed builds for the affected branches until October 27–29. The source material does not provide a complete inventory of devices still exposed, nor does it confirm the patch status of each targeted organization. Those details remain important to judging the incident’s continuing risk.
Patch, Restrict, and Investigate
Organizations running affected PAN-OS versions should follow Palo Alto Networks’ current security advisory, install the applicable fixed release, and keep management interfaces inaccessible from the public internet. Where a device may have been exposed during the attack window, administrators should treat patching as only one part of response: they should investigate for persistence, review access to management systems, and assess whether connected identity services were reached.
Federal agencies were given three days after the October 26 CISA listing to address the PHP2Shell vulnerabilities, according to the source material. Further clarity is expected from vendor advisories, incident investigations and any additional updates from Dream or Palo Alto Networks. The available account does not say whether law-enforcement agencies are investigating or whether the affected government-affiliated organization will disclose more about the impact.
Key Questions
What is PHP2Shell?
PHP2Shell is the name used for two PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619. Dream says the attacker used them to gain initial command execution on targeted Palo Alto firewalls.
How many servers were reported compromised?
Dream reported 24 firewalls with root access compromised, plus an internal firewall-management server reached through a U.S. government-affiliated network: 25 servers in the account overall.
Did AI create the exploit?
That has not been established. Dream found Claude Code and configurations for DeepSeek and Kimi on attacker systems, but said it had no direct evidence that AI tools wrote the exploit or scripts.
What should Palo Alto firewall operators do?
Follow Palo Alto Networks’ advisory and install the fixed PAN-OS release that applies to the device. The reported interim mitigation was to keep the management interface off the public internet; organizations that may have been exposed should also investigate for persistent access.
Source: ThorstenMeyerAI.com
