Black October: AI found decade-old PHP flaws and the world rushed to patch
Direct answer
On October 21, 2026, the PHP project released emergency patches for two critical flaws, CVE-2026-109618 and CVE-2026-109619, known together as PHP2Shell. Each carries a severity score of 9.2 out of 10 and lets an attacker run code remotely without logging in on an affected server. The flaws affect the PHP language itself, which powers about 70% of websites whose server-side technology is known, and had gone undetected for more than a decade until researchers using frontier models found them in August 2026.
What happened, in order
- August 2026, the discovery: researchers at Calif reported the first flaw on August 11 using OpenAI's GPT-5.6 Sol, inside the Patch the Planet initiative. Wiz, Alphabet's security firm, reported the second on August 24 using models including Google's Gemini 4 Argon.
- Two months of quiet coordination: OpenAI, Wiz, Cloudflare and the PHP project prepared the patches before disclosure, per Computer Weekly and Dig.watch coverage.
- October 20, the leak: basic details and a demonstration video leaked on social media before the patch, which moved the release forward.
- October 21, the patches: the fixed versions are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Versions 8.1 and older no longer receive official support from the PHP project, although some distributions published their own patches.
- The government response: agencies including the U.S. NSA, the U.K. NCSC and CERT-EU urged immediate patching or taking offline any site that could not be updated. France, the Netherlands, Finland and Denmark took government sites offline as a precaution while applying fixes.
What it means for your business
- Inventory comes first: the first task is knowing which PHP version runs on every site, server and hosting provider you use. Without that inventory, patching becomes guesswork.
- The same advance defends and attacks: the AI that helped find the flaw also speeds up exploit creation. The window between disclosure and active attack is measured in hours, and CISA confirmed active exploitation in the following week.
- Old versions stay exposed: if your site runs PHP 8.1 or older, the official project publishes no patch. That site needs a migration plan or a distribution patch, with a date, not a promise.
- Temporary mitigation helps and has a limit: PHP maintainers warn that mitigations reduce exposure to certain attack paths, and only the update provides the complete fix.
- Ask your provider in writing: request the exact version running your site, the date the patch was applied and the evidence. A provider that answers vaguely about a 9.2 flaw is describing its own risk.
Note: this article summarizes Computer Weekly, Dig.watch, HackerOne and BBC coverage from October 21 to 26, 2026, plus advisories from PHP, CERT-EU, NCSC and NSA. Severity scores and versions come from the official advisories cited.
Want AI that works for your business?
Message us on WhatsApp and let's talk about automation and AI agents for your business.
WhatsApp inicIARelated articles
- OpenAI expanded agent monitoring: in the incident replay, the alert would have come 30 hours earlier
- Google launched Gemini 4 Carbon: the model that hunts vulnerabilities
- What to do when your AI agent makes a mistake
Frequently asked questions
What is PHP2Shell?
The joint name for two critical PHP flaws, CVE-2026-109618 and CVE-2026-109619, rated 9.2, allowing unauthenticated remote code execution on affected servers.
Which versions fix the flaw?
PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, released October 21, 2026. Versions 8.1 and older receive no official patch from the PHP project.
How were the flaws found?
With help from frontier models: Calif used OpenAI's GPT-5.6 Sol and Wiz used models including Google's Gemini 4 Argon, inside a two-month coordinated disclosure.
What should a business do today?
Inventory every PHP site and server, apply the patch for its version or migrate if it runs an unsupported version, and ask its provider for the exact version and the date the patch was applied.
