🔍 Read the full analysis: 25 Palo Alto Servers, One PHP2Shell Chain: What Happened In Two Days on ThorstenMeyerAI.com
Get hardware and tech essentials 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 says an attacker used PHP2Shell alongside a previously disclosed Linux kernel flaw to gain root access on 24 Palo Alto Networks firewalls, then compromise an internal firewall-management server. The activity followed PHP fixes by about two days, but Dream says it has no direct evidence that AI tools found on the attacker’s systems wrote the exploit or scripts.
Twenty-four Palo Alto Networks firewalls and an internal server at a US government-affiliated organization were compromised in an attack that began about two days after PHP released fixes for two critical flaws, according to Israeli security company Dream. The attacker chained the PHP vulnerabilities, known as PHP2Shell, with a previously disclosed Linux kernel flaw to gain root access, then moved from the firewalls into the organization’s network.
Dream’s account says the attacker selected 240 firewalls and ran an automated attack against them on October 23. The operation produced root access on 24 devices, using the PHP flaws for initial command execution and the kernel vulnerability, called Fragnesia (CVE-2026-46300), to raise privileges. Dream says the full chain, including installing a persistent back door, took less than 15 minutes.
On October 24, the attacker compromised a second firewall belonging to the government-affiliated organization and used it to reach an internal firewall-management server. Dream counts that machine as the 25th compromised server. The attacker then targeted the organization’s Active Directory, which manages identities and access. Dream’s published account does not establish what data, if any, was taken or whether the Active Directory attack succeeded.
Dream said 22 of the 24 firewalls were left with hidden web shells. The targets were in the United States, Japan, Taiwan and South Korea. Palo Alto Networks said its Unit 42 researchers independently verified the attacker’s tools and results, according to the source report. CISA added both PHP2Shell vulnerabilities to its catalog of exploited vulnerabilities on October 26 and set a three-day deadline for federal agencies.
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
Internet-Facing Management Put Networks at Risk
The report shows how a flaw in a firewall’s management software can become a route into the organization behind it. Once the attacker obtained control of two firewalls at the government-affiliated organization, Dream says they reached the internal server used to manage the wider firewall estate. That makes the incident relevant beyond the individual devices: management systems can provide a path to broader network access.
The timing also put defenders in a difficult position. PHP had released fixes on October 21, but the source says Palo Alto’s patched builds for the affected PAN-OS 12.1 and 12.2 branches did not ship until October 27–29. Until those builds were available, Palo Alto’s stated protection was to keep the management interface off the public internet. The case underlines the value of restricting administrative access and applying vendor updates promptly, while avoiding the assumption that the presence of AI tools proves AI generated the attack.
Products Worth Considering
DJI Mic 3 Wireless Microphone System (2 Transmitters, 1 Receiver, Charging Case)
Amazon Kindle Paperwhite (12th Generation, 2024), 16 GB, 7-inch Display, Jade
Amazon Kindle Scribe Colorsoft 64GB (1st Generation)
As an affiliate, we earn on qualifying purchases.
From PHP Fixes to Firewall Patches
PHP released updated versions on October 21, addressing the two PHP2Shell flaws, identified in the source as CVE-2026-109618 and CVE-2026-109619. Palo Alto Networks issued an advisory that day, but fixed PAN-OS builds were still forthcoming. Dream says the firewalls use a vendor-supplied copy of PHP, version 8.0.30, which meant the PHP project’s releases did not themselves patch the affected firewall installations.
The second flaw in the chain, Fragnesia, had been publicly disclosed in May with an available exploit, according to Dream’s timeline and the cited security records. Dream says the attacker had prepared an offensive-security platform called aiscan on October 8, with DeepSeek and Kimi models configured. Before the attack, the operator reportedly found about 19,000 PAN-OS devices with internet-facing management pages, gathered version information from about 5,000, and narrowed the list to 240 targets. These figures describe Dream’s account of the attacker’s selection process, not the number of devices compromised.
““no direct evidence” that AI tools wrote the exploit or scripts”
— Dream
AI’s Role and Intrusion Damage
How AI was used remains unconfirmed. Dream found Claude Code installed on the attacker’s servers and DeepSeek and Kimi configured in aiscan, but said it had no direct evidence that those tools produced the exploit or attack scripts. Their presence does not establish how much, if any, of the operation was AI-assisted.
The source account also leaves open the full impact inside the government-affiliated network. It says the attacker targeted Active Directory, but does not specify whether credentials were stolen, whether access to the directory was achieved, what information was accessed, or whether the organization contained or removed all persistence. The supplied report does not identify the organization or detail how many vulnerable firewalls remain exposed.
Patch Rollout and Incident Response
Palo Alto’s fixes for the affected PAN-OS 12.1 and 12.2 branches shipped between October 27 and 29, according to the source material. Organizations using those versions should consult the vendor’s advisory for the applicable fixed release and exposure guidance. Where updates have not yet been applied, the source identifies restricting public access to the management interface as the interim protection.
Federal agencies were given three days after CISA listed the PHP2Shell flaws on October 26 to address them under the agency’s catalog process. The next public developments to watch are further findings from Dream, Palo Alto Networks or government responders about the affected organization, the status of compromised systems, and whether investigators establish the extent of the Active Directory intrusion. The account available so far does not provide those outcomes.
Key Questions
How many systems were compromised?
Dream reported 24 Palo Alto firewalls with root access and one internal firewall-management server, for 25 servers in total.
What vulnerabilities did the attacker chain?
The reported chain combined the two PHP2Shell vulnerabilities with Fragnesia, a Linux kernel privilege-escalation flaw identified as CVE-2026-46300.
Did AI write the exploit?
That has not been established. Dream found AI-related tools and model configurations on the attacker’s systems but said it had no direct evidence that AI wrote the exploit or scripts.
What protection was available before PAN-OS fixes shipped?
The source says Palo Alto recommended keeping the firewall’s management page off the internet while fixed builds for the affected branches were pending.
Source: ThorstenMeyerAI.com
