🔍 Read the full analysis: A Closer Look At “AI-Assisted” In The Palo Alto PHP2Shell Incident on ThorstenMeyerAI.com
Prime made for students and young adults
- Fast, free delivery for dorm and study essentials
- Prime Video and Amazon Music included
- Member-only deals
TL;DR
Dream says an attacker used PHP2Shell and a Linux kernel flaw to gain root access on 24 Palo Alto Networks firewalls, then reached a government-affiliated network and compromised another server. Dream found AI tools on the attacker’s infrastructure but says it has no direct evidence they generated the exploit or scripts, and the attack did not appear fully autonomous.
Attackers used two vulnerabilities to gain root access on 24 Palo Alto Networks firewalls and compromise a further server inside a US government-affiliated network, according to Israeli security company Dream. Palo Alto Networks said its Unit 42 researchers independently verified the attacker’s tools and results. Dream found AI tools on the attacker’s servers, but said it has no direct evidence that AI wrote the exploit or scripts.
Dream’s report describes a campaign on October 23 and 24 against internet-accessible management interfaces on PAN-OS firewalls. The attacker combined PHP2Shell, identified as CVE-2026-109618 and CVE-2026-109619, with Fragnesia, a Linux kernel privilege-escalation flaw, CVE-2026-46300. Dream says PHP2Shell allowed command execution under a restricted account; Fragnesia was then used to obtain root privileges. The report says the chain could be completed in under 15 minutes.
Dream says the attacker selected 240 firewalls after scanning exposed devices and narrowing results by country and software version. It reports that 24 were compromised, with 22 left in a parked state containing a hidden web shell. The targets were in the United States, Japan, Taiwan and South Korea. Two affected firewalls belonged to a US government-affiliated organization. The attacker used them to reach that organization’s internal firewall-management server, which Dream counts as the 25th compromised server, and then targeted Active Directory.
The timing left a gap between disclosure and fixes for the affected firewall software branches. PHP released fixes on October 21, and Palo Alto Networks published a security advisory that day, but fixed builds for PAN-OS 12.1 and 12.2 shipped between October 27 and 29, according to the source report. Until those builds were available, Palo Alto’s guidance was to keep the management interface off the public internet.
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 the Risk
The report highlights how an internet-facing management page can turn a software flaw into a route to broader network access. A firewall is intended to control traffic, but its administrative interface can itself become an entry point when exposed and vulnerable. In this campaign, Dream says the attacker moved from firewall access to an internal management server and then targeted Active Directory, a system used to control accounts and access across an organization.
The reported sequence also shows why patch timing and exposure controls matter together. PHP’s upstream fixes were available before Palo Alto’s affected PAN-OS builds, but Dream says the firewall software bundled its own PHP version. Organizations relying on those firewall branches therefore needed vendor updates or protective configuration, not simply an update to PHP on a separate server. The report’s account does not establish that AI was necessary to the intrusion; the access path depended on vulnerable software and reachable management interfaces.
Popular right now
Ninja Flip Toaster Oven and Air Fryer, 8-in-1, Stainless Steel, SP151
De'Longhi 15-Bar Pump Espresso Machine with Milk Frother & Temperature Control
Roborock F25 Ultra Steam Wet Dry Vacuum Mop
As an affiliate, we earn on qualifying purchases.
From Disclosure to Firewall Patches
Fragnesia was disclosed in May 2026, according to the supplied report, and had a public exploit. Dream says the attacker configured the offensive-security platform aiscan with DeepSeek and Kimi on October 8. That setup predates the PHP fixes and the reported campaign, but timing alone does not show how the tools were used.
On October 21, PHP released updates and Palo Alto Networks issued an advisory describing fixes as forthcoming. Dream says it identified about 19,000 PAN-OS firewalls with exposed management interfaces, obtained version information from about 5,000, and narrowed the potential targets to 240. The campaign followed two days later. Dream published its findings October 26 and updated them October 29. On October 26, the US Cybersecurity and Infrastructure Security Agency added both PHP2Shell vulnerabilities to its Known Exploited Vulnerabilities catalog and set a three-day deadline for federal agencies, according to the source material.
““We have no direct evidence” that AI tools wrote the exploit or scripts.”
— Dream
AI’s Role Remains Unproven
Dream found Claude Code installed and DeepSeek and Kimi configured in aiscan on attacker infrastructure. Those observations do not establish that any of the tools generated the exploit, selected targets, or ran the campaign. Dream explicitly says it has no direct evidence of AI authorship and does not assess the operation as fully autonomous. The precise contribution, if any, of the AI tools remains unknown.
The supplied account also does not identify the attacker or explain the full extent of any access to the government-affiliated organization. It says Active Directory was targeted, but does not establish whether the directory was successfully compromised or what information, if any, was accessed or taken. Palo Alto’s reported verification concerns the tools and results; the source material does not describe the scope of its independent review.
Patch Deployment and Incident Review
Organizations using affected PAN-OS 12.1 and 12.2 branches should check Palo Alto Networks’ advisory for the applicable fixed build and update systems. The immediate protective measure cited in the report is to keep management interfaces off the public internet. Security teams should also review access logs and investigate affected devices for signs of compromise, while treating Dream’s account as a reason to check systems rather than as confirmation that every exposed device was attacked.
Further clarity depends on updates from Dream, Palo Alto Networks and the affected organization. The supplied material does not give a public account of the government-affiliated organization’s response or confirm the final scope of the Active Directory activity. Those details, along with evidence about whether AI tools contributed to the attack, remain open.
Key Questions
What happened in the PHP2Shell incident?
Dream says an attacker combined PHP2Shell vulnerabilities with the Fragnesia Linux kernel flaw to gain root access on 24 PAN-OS firewalls, then reached an internal management server in a US government-affiliated network.
Did AI write the exploit?
That has not been established. Dream found AI coding and model tools on attacker infrastructure but said it had no direct evidence they wrote the exploit or scripts.
How many systems were reported compromised?
Dream reports root access on 24 firewalls and access to one internal firewall-management server, for 25 servers in total. The report also says Active Directory was targeted but does not confirm the outcome.
What should organizations do?
Apply the relevant fixed PAN-OS build identified by Palo Alto Networks and keep firewall management interfaces off the public internet. Review devices and logs for evidence of unauthorized access.
Source: ThorstenMeyerAI.com
