Two critical PHP flaws, one of them found by an OpenAI model, force an emergency web-wide patch as attacks begin and agencies take sites offline
The maintainers of PHP, the programming language behind an estimated 70% of the world's websites, released emergency fixes on 21 October for two critical remote code execution vulnerabilities, Investing.com reported. Known together as PHP2Shell (CVE-2026-109618 and CVE-2026-109619), the flaws carry a CVSS v4.0 rating of 9.2 and affect every web server running PHP 5.4 or later. Fixes shipped in four releases at once – 8.5.12, 8.4.27, 8.3.36, and 8.2.35 – while PHP 8.1 and earlier get no official fix. The report singles out shared-hosting setups running WordPress, Drupal, Joomla, or Magento as particularly exposed.
AI sits at the center of the story on both sides. OpenAI said its GPT-5.6 Sol model found CVE-2026-109618 in August through its Patch the Planet initiative, and Wiz Research separately discovered and reported both flaws. The coordinated release did not hold to plan: details leaked publicly on 20 October, and Cloudflare recorded the first attacks on PHP sites at 07:43 UTC on 21 October, hours before the official patch window opened at about 14:00 UTC. Reuters reported that cybersecurity agency websites in the Netherlands and Finland went dark, and agencies in Europe, Australia, Japan, and Britain told operators to update immediately or take sites offline. Cloudflare CTO Dane Knecht said the company's firewall rules for known attack routes are live for all customers, including free ones, but described them as "a STOPGAP only." Cloudflare shares were up 5.52% in Wednesday trading.
Within the next 48 hours, the CISO should have a complete list of internet-facing PHP instances – including marketing sites, vendor-hosted portals, and shadow IT – and each one either upgraded to a fixed release or taken offline. Treat firewall rules as a bridge, not a fix, and put any system on PHP 8.1 or older on an isolation-and-migration plan, since no official patch is coming.
This week, third-party risk teams should send a written attestation request to every hosting provider, agency, and SaaS vendor that may run PHP on the company's behalf, asking for the patched version and the date it was applied. At the next renewal, add contractual patch deadlines for critical vulnerabilities and a right to suspend service when they are missed.
This quarter, the Chief Risk Officer should ask management for time-to-patch metrics on critical vulnerabilities and test them against a scenario in which exploitation begins within hours of disclosure. With AI models now finding flaws at internet scale, patch windows measured in weeks are a risk-appetite decision, not an IT default.