🔍 Read the full analysis: How A PHP2Shell Chain Reached Root On 25 Palo Alto Servers In Two Days 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 used two PHP2Shell flaws and a Linux kernel vulnerability to gain root access on 24 Palo Alto Networks firewalls, then compromised an internal management server in a US government-affiliated network. Palo Alto Networks says Unit 42 independently verified the tools and results. Dream found AI tools on the attacker’s servers but says it has no direct evidence they wrote the exploit or scripts.
An attacker gained root access to 24 Palo Alto Networks firewalls and then compromised an internal firewall-management server in a US government-affiliated network, according to a report by Israeli security firm Dream. The campaign, carried out on October 23 and 24, chained the PHP2Shell vulnerabilities with a previously disclosed Linux kernel flaw; Palo Alto Networks says its Unit 42 researchers independently verified the attacker’s tools and results.
Dream’s account describes an automated attack against 240 selected PAN-OS firewalls. The attacker reportedly rooted 24 of them, then used two firewalls belonging to the same government-affiliated organization as a route into its network. An internal server used to manage the organization’s firewalls was compromised on October 24, bringing the reported total to 25 affected servers. Dream says the attacker subsequently targeted Active Directory, the system organizations use to manage accounts and access.
The chain combined PHP2Shell, CVE-2026-109618 and CVE-2026-109619, with Fragnesia, a Linux kernel privilege-escalation vulnerability tracked as CVE-2026-46300. Dream says PHP2Shell provided command execution under a restricted account on the firewall’s management web server, while Fragnesia enabled the attacker to gain root privileges. The firm says the full chain, including installation of a persistent back door, took less than 15 minutes. That duration is Dream’s finding, not a general measure of how quickly the vulnerabilities can be exploited.
Dream says 22 of the 24 rooted firewalls were left with a hidden web shell. The targets were in the United States, Japan, Taiwan and South Korea. The report also describes a funnel from roughly 19,000 internet-visible management interfaces identified through the FOFA device-search service, to about 5,000 that returned version information, and then to the 240 selected targets. These figures describe the stages Dream reported; they do not establish how many systems were vulnerable overall.
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 incident shows how an internet-facing administrative interface can turn a newly disclosed software flaw into a rapid route to deep network access. A firewall is designed to enforce network rules, but its management interface carries authority to change those rules. In the reported case, access to that interface was followed by a privilege escalation to root, then movement to a server that controlled firewalls inside a government-affiliated network.
The risk extends beyond the initial firewall. Compromise of a central management server can expose or affect multiple devices, while attempts against Active Directory may put user accounts and wider network access at stake. Dream’s report does not establish that the attacker successfully took over the directory, but the reported targeting underscores why defenders need to investigate beyond the perimeter device itself.
The timing also matters. PHP announced fixes on October 21, but Dream says fixed PAN-OS builds for the affected 12.1 and 12.2 branches arrived between October 27 and 29. That left a period when the upstream PHP fixes existed but corresponding firewall updates were not yet available. Palo Alto’s advisory recommended limiting access to management interfaces; restricting those pages from the public internet reduces exposure while organizations track and apply vendor updates.
Products Worth Considering

LG UltraGear 27-inch QHD OLED Gaming Monitor, 240Hz, 0.03ms, G-SYNC Compatible, FreeSync Premium Pro, HDR True Black 400

LG 27GR83Q-B 27-inch Ultragear QHD IPS Gaming Monitor

Samsung 32 Odyssey G5 QHD Gaming Monitor
As an affiliate, we earn on qualifying purchases.
Two Vulnerabilities, One Attack Chain
PHP2Shell refers in this report to two critical PHP flaws. The PHP project released updates on October 21, including PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, and urged users to update. Dream says the affected PAN-OS systems contained their own copy of PHP, identified in its analysis as version 8.0.30. The existence of an upstream PHP fix did not itself update that embedded component in Palo Alto’s firewall software.
The second step used Fragnesia (CVE-2026-46300), a Linux kernel flaw publicly disclosed in May 2026, according to Dream’s timeline and the cited vulnerability records. Its role in the reported chain was to raise privileges after initial code execution. The attacker did not need to rely on a new, previously unknown kernel vulnerability, the report says.
Dream published its findings on October 26 and updated the report on October 29. The US Cybersecurity and Infrastructure Security Agency added both PHP2Shell CVEs to its Known Exploited Vulnerabilities catalog on October 26, according to the source material. Palo Alto’s advisory was issued on October 21; fixed versions for the attacked 12.1 and 12.2 branches were reported as shipping from October 27 through October 29.
““no direct evidence””
— Dream
AI Involvement Is Not Established
Dream found Claude Code installed and DeepSeek and Kimi configured in an offensive-security platform called aiscan on infrastructure it associated with the attacker. That is evidence the tools were present, but Dream said it had no direct evidence that AI generated the exploit or attack scripts. The report also says the operation did not appear fully autonomous. The label “AI-assisted” should therefore be treated as an inference, not a confirmed description of how the attack was built or run.
Some operational details remain based on Dream’s account. The source material says Unit 42 independently verified the tools and results, but does not provide a separate public account from the affected government-affiliated organization. It is not clear whether the attacker obtained data, how far the Active Directory activity progressed, whether all 25 systems were cleaned, or whether any further systems were accessed.
The report says 22 firewalls were left with hidden web shells, but it does not establish whether those systems were the only devices compromised or whether the attacker retained access elsewhere. The reported counts also reflect Dream’s identified targets and findings, not a complete inventory of vulnerable internet-connected firewalls.
Patch, Restrict Access, Investigate
Organizations using affected PAN-OS branches should check Palo Alto Networks’ security advisory for applicable fixed releases and apply updates, while restricting management interfaces to trusted networks rather than leaving them open to the public internet. Those steps address both the immediate exposure and the underlying patch gap described in the report.
Administrators should also review firewall and network-management logs for suspicious access, check for unauthorized persistence, and investigate connections from perimeter devices to internal systems. Because Dream reports that the attacker reached a firewall-management server and targeted Active Directory, incident response should include review of those systems and relevant account activity, not only replacement or patching of the initial devices.
Further reporting from Palo Alto Networks, Dream or the affected organization may clarify the extent of the intrusion, the outcome of the Active Directory activity and whether data was accessed. The public account does not yet answer those questions.
Key Questions
What does PHP2Shell mean in this incident?
PHP2Shell is the name used for two PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619. Dream says they gave the attacker a way to run commands on the affected firewalls’ management web servers.
How did the attacker gain root access?
According to Dream, the attacker combined PHP2Shell with Fragnesia (CVE-2026-46300), a previously disclosed Linux kernel vulnerability. The PHP flaws enabled initial command execution; Fragnesia was used to escalate privileges to root.
Did AI create the exploit?
That has not been established. Dream found AI-related tools on the attacker’s servers but said it had no direct evidence that they wrote the exploit or scripts. The firm said the attack did not appear fully autonomous.
What should PAN-OS administrators do?
Check Palo Alto Networks’ advisory for the fixed release that applies to your software branch, install the update, and restrict the management interface to trusted networks. Review logs and investigate for unauthorized persistence or access to internal management systems.
Was Active Directory taken over?
Dream reported that the attacker went after the organization’s Active Directory, but the supplied account does not confirm a successful takeover. The outcome of that activity remains unclear.
Source: ThorstenMeyerAI.com
