PHP2Shell Plus Kernel Bug Rooted 24 Firewalls in 15 Minutes
Dreamgroup detail a campaign that chained PHP2Shell on PAN-OS with Fragnesia LPE to root 24 firewalls in 15 minutes. Scanning filtered 19,000 down to 24 hits.
A Dreamgroup team detailed a campaign that chained PHP2Shell with the Fragnesia kernel flaw to take root on 24 firewalls plus one management box in under 15 minutes. The scan started with 19,000 firewalls, filtered to 240 candidates, then 24 hits across the United States, Japan, Taiwan and South Korea. Forensic traces point to DeepSeek, Kimi and Claude Code sessions, and a reverse SSH tunnel may still be live.
The details here come from AI News Today on 31 October 2026 summarizing Dreamgroup research, CrowdStrike's broader ARTEX reporting, and Palo Alto Networks advisories on PAN-OS and PHP2Shell.
What was chained?
| Property | Detail |
|---|---|
| First flaw | PHP2Shell CVE-2026-109618 and CVE-2026-109619 on PAN-OS management web server, unauthenticated remote code execution |
| Second flaw | Fragnesia kernel LPE CVE-2026-46300, local privilege escalation to root on the same host |
| Chain | Remote code execution as web worker, then local escalation to root on the firewall appliance |
| Time | Under 15 minutes for 24 firewalls plus one internal management box |
| Scan scale | 19,000 firewalls scanned, 240 candidates after fingerprinting, 24 hits |
| Geography | United States, Japan, Taiwan, South Korea, including two United States government affiliated targets |
| Attribution traces | DeepSeek, Kimi and Claude Code sessions |
| Persistence | Reverse SSH tunnel into United States government infrastructure, may still be live per Dreamgroup |
The PAN-OS management web server runs PHP to serve the management interface. PHP2Shell is a flaw in the interpreter itself, so when the interface is reachable, the flaws give code execution as the web worker. Fragnesia then gives root. According to Palo Alto Networks, PAN-OS, Panorama and WildFire were already confirmed as affected.
How did the scan narrow 19,000 to 24?
The campaign filtered before it exploited.
First, it scanned 19,000 firewalls for a PAN-OS management web server fingerprint. That step is cheap and unauthenticated.
Second, it probed the 19,000 for the PHP2Shell pre conditions. About 240 survived that filter, which suggests those hosts were both PAN-OS and on a vulnerable PHP branch with a reachable management interface.
Third, it launched the chain against the 240. Twenty four yielded root plus one internal management box, which is a 10 percent hit rate against the filtered set and a 0.12 percent hit rate against the initial scan. That ratio is why the same researchers describe the tooling as AI assisted but not AI magic. The AI did not invent a new vulnerability class. It automated the filtering that lets a small hit rate still produce 24 hosts in 15 minutes.
I ran a similar filter chain in a lab with a PAN-OS front end. The time from first probe to a filtered candidate list was minutes once the fingerprint was tuned.
Why does this matter beyond PAN-OS?
The same PHP2Shell flaws affect any web server that runs PHP, which is roughly 70 percent of websites, but the firewall chain matters for a different reason. A firewall compromised at root gives an attacker control of network policy, not just a web server. Controlling the management interface means controlling what can pass.
According to Dreamgroup, traces point to DeepSeek, Kimi and Claude Code sessions, plus a reverse SSH tunnel that may still be live in United States government infrastructure.
What should teams check this week?
The checklist is the same one that applies to every PHP2Shell host, plus the firewall specific step.
First, inventory every host that serves PHP, including PAN-OS management interfaces, and confirm whether the management interface is internet facing. If it is, treat it as the primary exposure. The PHP flaws give code execution before application login code runs, especially with mod_php style handling.
Second, patch PAN-OS to the fixed train per the Palo Alto Networks advisory, not just the underlying PHP package. Update to the fixed PHP branches where you control the interpreter: 8.5.12, 8.4.27, 8.3.36 or 8.2.35, then restart php-fpm, Apache, FrankenPHP or LiteSpeed workers and verify worker age after restart.
Third, hunt for the persistence that a web flaw does not usually leave. Look for reverse SSH tunnels from the firewall management network to external hosts, especially any tunnel that would survive a reboot. The Dreamgroup note that a tunnel into United States government infrastructure may still be live is the warning to check the management network, not just the web logs.
Fourth, rotate any secrets that lived in the same worker as PHP, even without confirmed code execution, because CVE-2026-109619 can leak memory without a full compromise.
The same isolation thinking I use at Krova Cloud applies to management interfaces, as described in container vs microVM isolation.
What is the verdict and what remains uncertain?
According to AI News Today, Dreamgroup researchers detailed the chain and the 19,000 to 240 to 24 filter, plus the reverse tunnel that may still be live. According to Palo Alto Networks, PAN-OS was already confirmed as affected by PHP2Shell, which makes the chain plausible without a new vulnerability.
The verdict is that PHP2Shell plus Fragnesia turns a web flaw into a firewall root in under 15 minutes when the management interface is internet facing. The scan is the weapon, not the chain alone.
The limitations are threefold. First, the 19,000 to 24 numbers are from Dreamgroup, not from a vendor advisory, so the exact scope should be treated as reported rather than independently confirmed. Second, the DeepSeek, Kimi and Claude Code traces are forensic attribution to development sessions, not proof that those models were used to launch the scan. Third, the reverse SSH tunnel may still be live per Dreamgroup, but that is a single report and the tunnel's current status is not confirmed by the affected government.
FAQ
Are we affected if our PAN-OS management interface is not internet facing?
No. The chain requires the management web server to be reachable. If it is only reachable from a management network, the scan of 19,000 internet facing firewalls would not include you.
Do we need to patch the firewall and PHP?
Yes, both. The firewall needs the Palo Alto fixed train for PAN-OS. Any other host that runs PHP needs the PHP fixed branch and a worker restart.
What is the first indicator to hunt for?
A reverse SSH tunnel from the management network to an external host, plus PHP2Shell probes around the time the scan would have hit your fingerprint.
Published on debugly.dev by Rohit Bhadani | Founder of Krova Cloud
Published on debugly.dev by Rohit Bhadani | Founder of Krova Cloud