Unit 42 retracts PHP2Shell agentic AI link: patch anyway
Unit 42 walked back its claim tying a government breach with agentic AI activity to PHP2Shell. The PHP RCE is still real: patch to 8.4.27 or 8.5.12.
The scariest PHP2Shell headline of the week just lost its main source. On October 23, Palo Alto Networks' Unit 42 added an update tying an intrusion at a European government agency, which included what it called agentic-AI-style activity, to the PHP2Shell remote code execution flaws. On October 25 it retracted that update, saying it is "unable to confirm that initial access is associated with the specific PHP2Shell CVEs." The flaws are still critical. The story attached to them changed.
What actually happened
- The bugs: CVE-2026-109618 and CVE-2026-109619 are memory-safety flaws in PHP that allow unauthenticated remote code execution. PHP fixed them on October 21 in 8.2.35, 8.3.36, 8.4.27, and 8.5.12. We covered the patch then.
- The claim: Unit 42's October 23 update described attackers getting password hashes and MFA secrets within two hours, with command patterns that looked like an AI agent was running them, and linked that to PHP2Shell.
- The retraction: The October 25 update withdrew the October 23 update. The intrusion involved a vulnerable PHP application, but the link to these two CVEs is unconfirmed.
- What still stands: The Hacker News reports Cloudflare saw "millions" of exploitation attempts after disclosure, and an independent researcher's honeypots recorded successful exploitation in the wild. Unit 42 says Cortex Xpanse sees over 22.6 million exposed instances that are potentially vulnerable.
Social posts still repeat the October 23 version as "confirmed." It isn't.
Why the PHP2Shell retraction matters for your business
Patch on the CVE, not on the narrative. Your decision to update PHP should never depend on whether a vendor can attribute a specific breach. An unauthenticated RCE with active scanning is a patch-today item either way.
Threat intel is a draft until it settles. Early reports get revised, and an attribution can disappear in 48 hours. Read the vendor's own page and its update log before you brief your team or a client.
The agentic-attacker question is still open. The retraction covers the PHP2Shell link, not the idea of AI-run intrusions. Faster attackers mean the time between a patch and an exploit keeps shrinking, so your update window should too.
Key takeaways
- Unit 42 retracted its link between PHP2Shell and a government intrusion with agentic-AI-style activity
- The PHP RCE flaws remain critical, with exploitation attempts seen in the wild
- Fixed versions: PHP 8.2.35, 8.3.36, 8.4.27, 8.5.12
- Check your host's actual PHP version; don't assume managed hosting patched it
- Cite the vendor's primary page and its update log, not a screenshot of a social post
Know what runtime versions you run, without guessing. We set up dependency inventory, patch alerts, and staged update pipelines so a critical CVE means one deploy, not an all-hands. See our maintenance work, or ask us to check your stack.
Sources: Unit 42 threat brief, The Hacker News.
- #php2shell
- #php
- #threat-intelligence
- #security
- #patching
Tommy Rush — Founder, Rush Commerce
Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More
Get The Rush Report weekly — one email, zero fluff.
Keep reading
AWS capacity largely sold out through 2027, says Jassy
Andy Jassy says AWS capacity is largely sold out through 2027, with a good chunk of 2028 gone. What that means for small-business AI and cloud budgets.
Read itMeta's $25B privacy penalty: audit what your apps collect
A New Mexico judge ordered Meta to pay $25 billion for misleading users about third-party app data sharing. Your privacy policy makes the same kind of promise.
Read it