Could “AI-Assisted” Describe The PHP2Shell Attack? What The Evidence Says
AIThis post was created with the assistance of artificial intelligence (AI).

🔍 Read the full analysis: Could “AI-Assisted” Describe The PHP2Shell Attack? What The Evidence Says on ThorstenMeyerAI.com

Before you orderOffer from Amazon

Get smart everyday buys delivered free with Prime

  • Fast, free delivery on millions of items
  • Prime Video, Amazon Music and more included
  • Member-only deals all year
Start your free Prime trial Free trial for eligible customers · Cancel anytime
As an affiliate, we earn on qualifying purchases.

TL;DR

Dream reported that an attacker used two PHP2Shell flaws and a known Linux kernel bug to gain root access on 24 Palo Alto Networks firewalls and reach a 25th server. Dream found AI tools in the attacker’s environment, but said it has no direct evidence they wrote the exploit or scripts; Palo Alto Networks’ Unit 42 independently verified the attacker’s tools and results.

An attacker used two newly disclosed PHP2Shell flaws and a previously public Linux kernel vulnerability to gain root access on 24 Palo Alto Networks firewalls and compromise a 25th server inside a U.S. government-affiliated organization, according to a Dream report published October 26 and updated October 29. Dream found AI tools on the attacker’s servers, but said it has no direct evidence that AI wrote the exploit or attack scripts, leaving “AI-assisted” a qualified description rather than a proven account of how the intrusion was conducted.

Dream’s account says the attacker scanned and filtered exposed firewall management pages, then selected 240 targets across the United States, Japan, Taiwan and South Korea. An automated batch run on October 23 gained root access on 24 firewalls. Dream says the attacker chained PHP2Shell vulnerabilities CVE-2026-109618 and CVE-2026-109619 with Fragnesia, a Linux kernel privilege-escalation flaw identified as CVE-2026-46300. The PHP flaws provided a route to run code on the firewall; Fragnesia was then used to raise privileges, according to Dream.

The report says 22 of the rooted firewalls were left with a hidden web shell. Two affected devices belonged to a U.S. government-affiliated organization. The attacker used one firewall as a route to an internal server used to manage the organization’s firewalls, then targeted its Active Directory system, which controls access to accounts and services. Palo Alto Networks said its Unit 42 researchers independently verified the attacker’s tools and results. The source account does not specify the extent of any data access or operational impact at the organization.

Dream also reported finding Claude Code installed and the Chinese AI models DeepSeek and Kimi configured in an offensive-security platform called aiscan. Dream said the evidence does not establish that those tools generated the exploit or scripts, and that the operation did not appear fully autonomous. The available account therefore supports the presence of AI tools in the attacker’s environment, not a definitive claim that AI created or directed the attack.

At a glance
reportWhen: Attack reported October 23–24, 2026; Dr…
The developmentA Dream report, updated October 29, describes a late-October attack chain against PAN-OS firewalls and documents AI tools in the attacker’s environment without establishing that AI generated the attack.
Thorsten Meyer AI
Timeline

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.

~2 daysfrom PHP’s fix (21 Oct) to the first rooted firewall (23 Oct), my count from the dates
24 +1firewalls rooted, plus one internal management server (Dream)
<15 minfor the whole chain, up to a root back door (Dream)
22rooted firewalls left “parked” with a hidden web shell (Dream)
  • 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 Became Entry Points

The reported intrusions show how a recently disclosed software flaw can become an immediate risk when an administrative interface is reachable from the public internet. Management pages are meant to control firewall rules and access; compromise can give an intruder a foothold in systems that protect a wider network. In this case, Dream says that foothold led from firewalls to an internal management server and an attempted move against Active Directory.

The AI question matters because it affects how organizations interpret an attacker’s speed and capabilities. But the evidence Dream describes does not establish AI-generated code or an autonomous operation. The concrete security lesson is less speculative: exposure of administrative interfaces, a known kernel vulnerability and delayed availability of fixed firewall builds combined to create risk. Organizations should act on those documented weaknesses rather than assume the attack depended on a novel AI capability.

Bose QuietComfort True Wireless Earbuds with Active Noise Cancellation, Black

Bose QuietComfort True Wireless Earbuds with Active Noise Cancellation, Black

Bose QuietComfort Wireless Bluetooth Headphones with Active Noise Cancellation, Mic, USB‑C Charging, Deep Bass, 24‑Hour Battery – White Smok

Bose QuietComfort Wireless Bluetooth Headphones with Active Noise Cancellation, Mic, USB‑C Charging, Deep Bass, 24‑Hour Battery – White Smok

As an affiliate, we earn on qualifying purchases.

Patches Followed the Attack Window

The PHP project released fixes on October 21 for the two vulnerabilities now referred to as PHP2Shell. Palo Alto Networks published an advisory the same day, while fixed PAN-OS builds for the affected 12.1 and 12.2 branches arrived between October 27 and 29, according to the source report. Dream says the firewalls use a bundled copy of PHP, so updating the general PHP release alone did not necessarily fix the vulnerable PAN-OS installations.

Dream’s timeline places the main automated attack on October 23, about two days after the disclosures. The report says the attacker had identified about 19,000 PAN-OS devices with internet-facing management pages, obtained version information from about 5,000, and narrowed its list to 240 targets. Those figures describe Dream’s account of the attacker’s discovery and filtering process; they do not establish how many devices remain vulnerable overall.

Fragnesia had been disclosed publicly in May 2026, with a public exploit, according to the source material. CISA added both PHP2Shell CVEs to its Known Exploited Vulnerabilities catalog on October 26 and gave federal agencies three days to act. That timeline places a known privilege-escalation bug alongside newly disclosed flaws and a period before fixed PAN-OS versions were available.

““No direct evidence” that AI tools wrote the exploit or scripts.”

— Dream

AI’s Role Is Still Unproven

The available evidence does not show whether Claude Code, DeepSeek, Kimi or aiscan contributed to vulnerability research, exploit development, target selection or attack execution. Dream’s finding that the tools were installed or configured is not proof they were used for any of those tasks. The report also does not establish whether a person directed each stage or how much automation was involved beyond describing an automated batch against the selected targets.

The full impact on the government-affiliated organization remains unclear in the supplied account. It says the attacker reached an internal firewall-management server and attacked Active Directory, but does not report whether accounts were taken over, what information may have been accessed, or whether the intrusion was contained. The status of all targeted systems and the number still exposed are also not specified.

Patch Status and Impact Need Tracking

Organizations using affected PAN-OS branches should check Palo Alto Networks’ advisory and apply the fixed builds appropriate to their installations. Until a management interface can be restricted, the source report identifies keeping it off the public internet as a protective measure. Defenders should also review firewall logs and systems for signs of compromise, including persistent access, and assess whether internal identity systems were reached.

Further confirmation would need to clarify the government-affiliated organization’s impact, the attacker’s use of the AI tools, and whether additional victims were identified. The vendor’s fixed-build releases and CISA’s required federal response provide immediate milestones, but the supplied source material does not give a final incident-resolution update.

Key Questions

What were the PHP2Shell flaws used in the attack?

They are CVE-2026-109618 and CVE-2026-109619, for which the PHP project released fixes on October 21, 2026. Dream says the attacker chained them with the Linux kernel flaw Fragnesia to gain elevated access on targeted firewalls.

Did AI write the attack?

That has not been established. Dream found AI tools installed or configured in the attacker’s environment, but said it had no direct evidence those tools wrote the exploit or scripts.

How many systems did Dream say were compromised?

Dream reported root access on 24 firewalls and a separate internal firewall-management server, bringing the reported total to 25 servers. It said the systems were in the United States, Japan, Taiwan and South Korea.

What should organizations using PAN-OS do?

Check Palo Alto Networks’ advisory for the applicable fixed build and update affected systems. The source report also recommends keeping firewall management pages off the public internet and reviewing systems for signs of persistence or related access.

Source: ThorstenMeyerAI.com

This content is for general information only and is not financial, tax or legal advice. Consult a qualified professional for decisions about your money.
You May Also Like

Best AI Mobile Workstation Laptops To Boost Your Workflow In 2026

Discover the best AI-capable mobile workstations in 2026, featuring top models like Dell Precision 7680 and Lenovo ThinkPad P14s for demanding workflows.

Desktop Workflow Hacks: Using Watch-Once Voice Commands

New desktop automation approach enables users to record workflows once and trigger them via voice commands, promising increased efficiency for power users.

Could Canada Help Europe Lead In Artificial Intelligence?

European Commission’s proposal to deepen ties with Canada could position Europe as a leader in artificial intelligence, leveraging Canada’s advanced AI ecosystem.

Your Coding Agent Is an Attack Surface: The Claude Code Security Reckoning

Recent vulnerabilities in Claude Code reveal critical attack surfaces, risking token theft and code execution, with patches underway but some risks remain.