AivexaNewsSearch
AI news for builders and product teamsChecked every hour

PHP Armageddon: OpenAI, Google’s Wiz find ancient holes, panicking the internet

Collected Oct 21, 2026

The U.S. National Security Agency issued an alarming warning on Wednesday that two critical vulnerabilities had been discovered in PHP, the server-side language behind a large share of the web. The PHP Foundation has already released patches. According to the NSA, the flaws are severe enough that any site unable to patch right away should be taken off the internet until it can be. The vulnerabilities let an attacker break into a server's file system or into a database a web application uses.

The two holes have sat unnoticed in every version of PHP since 5, which shipped in 2004. PHP is used so broadly for web applications that it is commonly said to power about 70% of websites, which by some counts is more than 33 million sites. Popular content management systems, WordPress among them, run on it. Because the affected code dates back two decades, sites on older branches face more than routine patching: PHP 8.1 and earlier are no longer supported. The recommended move is to bring the web server up to the current PHP release, 8.5.12.

The discovery came out of AI-assisted security research. Security testing firm Calif was working under OpenAI's "Patch the Planet" initiative, which targets flaws in open source software, and found one of the two bugs using GPT-5.6 Sol, OpenAI said in a blog post. Separately, the Wiz team found multiple PHP vulnerabilities using its own AI: the Wiz Atlas security agent, Gemini 4 Argon and GPT-5.6 Sol.

Both organizations followed responsible disclosure practice, coordinating with PHP on fixes before going public, then jointly working through the findings and testing the patches. Wiz credited Automattic, Akamai, AWS, Cloudflare, Fastly, Imperva, Microsoft and Vercel for help. WordPress has said the flaw is not specific to its CMS, but that sites running it must still patch their servers and coordinate with their hosting providers to make sure they are covered.

OpenAI says researchers reached the flaws before attackers did, so there have been no reports of exploitation in the wild. That is partly because, before AI, these bugs were too difficult to exploit. Wiz's blog put it directly: AI removes that barrier, and LLMs can help adapt an exploit to different PHP versions, configurations and memory layouts. In practice, that means the same class of tooling that found the bugs can also help weaponize them. This suggests the disclosure window is tighter than usual: once details are public, the effort of turning a proof of concept into a working attack against a specific host drops sharply.

Two pieces of technical context help explain the severity. First, a flaw sitting in PHP itself affects every application layered on top of it, so the blast radius is set by how many servers run the language rather than by any one product. Second, file-system and database access are the two resources a web application most needs to protect, so a bug that reaches either one can lead to data theft, code execution or full server compromise. Anyone operating a PHP stack, whether directly or through a CMS on shared hosting, is in scope until their version is confirmed current.

The FAQ-style worry is depth of exposure. Running an unsupported branch such as 8.1 or earlier does not just mean missing this week's patch; it means future ones may not arrive either. Upgrading across major versions is rarely a one-line change, though. Extension compatibility, framework versions and custom code often need review, which is why some teams may find the NSA's advice to go offline temporarily more practical than an emergency upgrade. Sites behind a CDN or WAF can lean on those providers' mitigations as a stopgap, which is likely why so many infrastructure vendors were involved in the coordinated response.

Why it matters: this is a high-stakes patching sprint for anyone running PHP, and the deadline is set by attackers who can now read the same public details. Teams should confirm their PHP version, plan the move to 8.5.12, and treat unsupported installs as urgent. The wider lesson, and this is my inference, is that AI-assisted discovery will surface more long-dormant bugs in foundational open source, so maintaining current dependencies is becoming a security requirement rather than housekeeping.

Read at TechCrunch · AI

Based on reporting from the original publisher. Visit the source for full context and later updates.

Publisher excerpt

This is the kind of security issue that was found and prevented by AI, but is also a high risk because of AI.