The Agentic Post
Breaking
Black October 2026: Every Major AI Security Incident, Explained  ·  ARTEX: The Open-Source AI Hacking Tool Behind October’s Biggest Attacks  ·  Chinese Hackers Used AI Agents to Hit 2,250 Microsoft 365 Accounts  ·  PHP2Shell Is Now Being Exploited, and Attacks Began Before the Patch  ·  OpenAI-Backed Thrive Buys ADT for $15.3 Billion to Rebuild It With AI  ·  The AI Data Center Backlash Hits Minnesota and Australia in One Week  ·  
Home/AI Safety
PHP2Shell: AI Found Critical Flaws in 70% of the Web. Update Now.

PHP2Shell: AI Found Critical Flaws in 70% of the Web. Update Now.

AI Safety

PHP released emergency fixes for two critical PHP2Shell flaws that let attackers run code on most PHP servers. Found with OpenAI and Google AI models. Update to PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35.

PHP shipped emergency security updates on October 21, 2026 for two critical flaws, nicknamed PHP2Shell, that let an attacker with no login run code on almost any server running PHP. PHP powers roughly 70% of websites, including everything built on WordPress, Drupal and Joomla. The bugs had sat in the code for more than a decade. They were found with AI models from OpenAI and Google. The fixed versions are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. If you run a PHP site, update now.

What exactly are the flaws?

Two memory-safety bugs, tracked as CVE-2026-109618 and CVE-2026-109619, each rated 9.2 out of 10 on the CVSS v4 scale. In plain terms, a specially crafted web request can confuse how PHP manages memory and let the attacker run their own commands on the server. Wiz said attackers could also read passwords, tokens and API keys straight out of PHP’s memory.

PHP says every installation that serves web requests is at risk. The highest risk is Apache with mod_php, where the malicious request triggers the flaw before any of the website’s own code even runs. Calif, Wiz and Cloudflare put the reach at PHP 5.4 and later, more than ten years of releases. PHP also published fixes for the old 7.4, 8.0 and 8.1 branches because of the severity, and warned that no configuration change fully replaces updating.

How did AI find it?

Security firm Calif found the first bug in August during an audit of PHP’s source code funded by OpenAI, using OpenAI’s GPT-5.6 Sol. Google-owned Wiz found the flaws independently weeks later using its Wiz Atlas tool, Google’s Gemini 4 Argon and GPT-5.6 Sol. PHP’s advisory credits Calif, Wiz and OpenAI together.

The important part is not that AI found a bug. It is that AI made the bug usable. These are "notoriously complex" memory flaws that need different exploits for different PHP versions and setups, which is why almost nobody could weaponise them for a decade. "With AI, this is no longer a barrier," Wiz wrote. Calif struck a more careful note, saying it used only generally available models and that knowing PHP’s history mattered more than the model.

Why did websites go dark before the patch?

Because the news leaked early. Someone posted about the coming fix on Hacker News on Tuesday, so PHP pulled its release forward. The EU’s cyber agency CERT-EU and Britain’s NCSC advised taking systems offline if they could not be patched immediately, and the US NSA issued its own alert. Government sites in the Netherlands and elsewhere went offline. Pinboard, the GrapheneOS forum and OBS took parts of their sites down, and Laravel paused its cloud deployments.

A proof-of-concept exploit circulated online before the patch existed. Cloudflare switched on firewall rules for all customers, free accounts included, about nine hours before disclosure, and said it watched attackers adjusting their payloads against those rules in real time. Calif’s CEO warned that anyone can now run AI against the published patch and produce a working exploit.

What should site owners do right now?

  • Check your PHP version. In WordPress, go to Tools, then Site Health, then Info, then Server.
  • Update to a fixed release: 8.5.12, 8.4.27, 8.3.36 or 8.2.35 or later. On shared hosting this is usually in cPanel under "Select PHP Version" or "MultiPHP Manager", or your host may update it for you.
  • If you are on PHP 8.1 or older, move to a supported version. WordPress notes that versions before 8.2 no longer get regular security fixes.
  • Put a firewall in front (Cloudflare or your host’s WAF) to buy time, but treat it as a stopgap, not a fix.
  • Rotate secrets such as API keys and database passwords if your server was exposed, since the flaw can leak memory.

What does this mean for the AI security race?

It is the clearest example yet of what Microsoft warned about when it said vulnerabilities now get weaponised in under 24 hours. OpenAI called it "one of the most impactful security issues in recent memory" and said it expects "similar findings to increase sharply in the coming months." This time defenders found it first. The same tools will find the next one for attackers, which is exactly the case labs make for giving vetted defenders early access to their strongest cyber models.

Read PHP’s official advisory and The Next Web’s full report.

Part of our coverage of Black October 2026, every major AI security incident this month.

Up Next
How to Prepare for an Interview With AI

How to Prepare for an Interview With AI

How-To

A practical guide to using AI for interview preparation, covering research, practice, and feedback, without relying on it live during the interview.

AI interview prep genuinely works best as a practice partner and research tool, not as something to lean on during the actual interview itself.

Paste in the job description and ask what specific skills it seems to prioritize, or what kinds of questions are typical for a role like this. This kind of research-heavy task is exactly where AI assistance is genuinely strong.

Ask the AI to play interviewer and ask you questions one at a time, then answer out loud before checking its feedback. This builds actual practice articulating your answer under mild pressure, which reading a pre-written answer doesn’t.

Paste in your own draft answer to a common question and ask for specific feedback, what’s vague, what’s missing, rather than asking it to write the answer from scratch. Keeps the answer genuinely yours while improving it.

Never use it live during an actual interview, most interviewers can tell when an answer sounds read rather than spoken naturally, and getting caught undermines trust far more than an imperfect but authentic answer would. See our prompt engineering guide for more on getting useful feedback.

See Anthropic’s own prompt engineering documentation for more depth.