PHP2Shell exposes the web's vulnerability to AI-enhanced flaws

Two critical vulnerabilities in PHP were urgently patched after being discovered with AI model assistance. The episode shows that the time between discovery and exploitation is shrinking, even for software that powers much of the web.

On October 21, PHP released patches for two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, affecting the engine used by about 70% of websites according to the cited source. Versions 8.5.12, 8.4.27, 8.3.36, and 8.2.35 are covered by the update, while reports already describe exploitation attempts and tensions over coordinated disclosure. The issue goes far beyond PHP: if AI models find flaws faster, the window to react shrinks, sometimes abruptly.

Quand la découverte accélère plus vite que la parade

The two vulnerabilities, nicknamed PHP2Shell, allow remote code execution without authentication, each with a CVSS v4.0 score of 9.2. Wiz indicated it demonstrated unauthenticated code execution on WordPress, Drupal, and Joomla, while OpenAI explained that the security team Calif found one of the flaws via GPT-5.6 Sol as part of its Patch the Planet program. According to Wiz, the exploitation chain was "at the edge of what human researchers could practically achieve," and advanced models have "substantially reduced that barrier."

This shift matters because the flaw is not in an isolated application but in the PHP runtime itself. In short, patching the site is not enough if the underlying engine remains vulnerable. For operations teams, the message is harsh but clear: update PHP, then restart all workers, or the fix remains incomplete.

Une divulgation coordonnée qui a mal tenu

The joint publication was scheduled for October 22 but slipped. TechTarget reported that CVE identifiers were already circulating on forums as early as October 20, prompting PHP to move the release up by one day. Chainguard then published fixed images earlier than planned, a decision criticized by the PHP Foundation and defended by its CEO, citing reports of active exploitation [to be verified on exact exchange details].

Amazon claims its honeypots detected exploitation attempts as early as October 17, before the public announcement. Meanwhile, Matthew Prince, CEO of Cloudflare, said attempts on his network reached "millions" after disclosure. The scenario reminds us that disclosure remains fragile when technical clues circulate too early. The confidentiality mechanism then resembles a swinging door, not a safe.

Pourquoi les anciens environnements sont les plus exposés

Matthew Weier O’Phinney, author of the source analysis, estimates about 40% of PHP users remain on unsupported versions. Older community versions, down to PHP 5.4, are affected by at least one of the two flaws, and teams that have not migrated rely on patches provided by LTS vendors like Zend [to be verified by distributions]. In this context, the argument "we never had an incident" weighs little against a vulnerability beneath the application.

OpenAI proposed a five-step response plan for AI-discovered flaws affecting many products simultaneously: validate and patch, allow time for affected organizations, coordinate with authorities, prepare updates across multiple products, then publish recommendations. The lab also stresses that such cases should multiply in the coming months. In other words, reaction time becomes a scarce resource, almost a capacity variable.

Key points

  • CVE-2026-109618 and CVE-2026-109619 were patched on October 21.
  • Patches cover PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35.
  • Wiz and OpenAI link discovery to GPT-5.6 Sol and Gemini 4 Argon.
  • Wiz says all versions since PHP 5.4 are affected.
  • Cloudflare reports "millions" of attempts after announcement.
  • OpenAI expects a "sharp" increase in such discoveries in coming months.

By the numbers

  • 2 vulnerabilities — CVE-2026-109618 and CVE-2026-109619, source PHP / October 2026.
  • 9.2/10 — CVSS v4.0 score for each, according to cited sources.
  • 4 versions — PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35 patched on October 21.
  • 70% — approximate share of the web relying on PHP, according to source text.
  • 40% — estimated share of PHP users remaining on unsupported versions.

To read