OpenAI and the Patch the Planet Initiative Fix Critical PHP Flaws Affecting Most of the Web
AI-assisted researchers turned a persistent two-year-old code flaw into working exploits, forcing a rapid patch cycle for the language that powers the majority of websites.
By Mei Lin ·

For the vast majority of website visitors and administrators, the immediate implication of recent events is a necessary software update. Because PHP powers an estimated 70% of the internet, the discovery of critical security flaws means that sites running specific versions of the language are now vulnerable to remote attacks. Users do not need to change their browsing habits, but site owners must ensure their servers are updated to the latest patched versions to maintain security.
The situation came to light on October 21, 2026, when OpenAI announced that its GPT-5.6 Sol model, used within the “Patch the Planet” cybersecurity initiative, had identified serious vulnerabilities in the PHP engine. These flaws, which had stumped human developers for two years, were turned into practical exploits by AI-assisted researchers in just two weeks. The discovery triggered a coordinated response involving PHP maintainers, security providers, and government agencies, resulting in the release of patched versions 8.2.35, 8.3.36, 8.4.27, and 8.5.12.
The technical core of the issue lies in how PHP manages computer memory and handles errors. The first vulnerability occurs when the engine runs out of allocated memory, potentially leaving behind incomplete data that is later misinterpreted as valid. The second involves a fatal error that leaves the system pointing to memory that has already been freed. Both flaws, tracked as CVE-2026-109618 and CVE-2026-109619, allow attackers to remotely execute malicious code without needing login credentials, potentially leading to full control of a website.
The timeline of the discovery was accelerated by external pressure. Researchers from Calif, a California-based cybersecurity firm and founding partner of Patch the Planet, began auditing the code in late July 2026. While the PHP Foundation had known about the underlying flaw since 2024, they lacked a method for exploitation or a fix. On August 11, Calif researcher Ryan A. identified the exploitable path, with OpenAI researchers confirming it that same day. The coordinated patch release was originally planned for October 22 but was moved up to October 21 after premature disclosures on October 20 sparked public outcry.
OpenAI frames this incident as a prime example of the “Defender's Window,” a concept introduced following previous AI-driven security events. This refers to the narrow timeframe during which organizations can use advanced AI models to find and patch defenses before those same capabilities become widely available to malicious actors. The company argues that because powerful technology will inevitably be used by bad actors, it is a collective responsibility to proactively address exploitable flaws, a stance supported by recent findings from Anthropic’s Claude Mythos regarding zero-day vulnerabilities in major operating systems.
The severity of the flaws is underscored by their location in the core PHP engine, meaning websites can be affected even if their specific application code is secure. Both vulnerabilities received a critical severity score of 9.2 out of 10. While some may argue that the flaws would have remained harmless without AI to exploit them, OpenAI maintains that the proactive approach is essential. The company highlights this as one of the most significant cybersecurity discoveries of 2026, given the ubiquity of the language and the speed at which AI tools transformed a static bug into an active threat.
For California-based businesses and tech firms, the incident serves as a reminder of the shifting landscape in cybersecurity. The collaboration between private AI firms, specialized security companies like Calif, and foundational open-source projects illustrates a new model for maintaining digital infrastructure. As AI models continue to evolve, the ability to detect and fix complex code flaws may become a standard part of the defensive toolkit, shortening the gap between vulnerability discovery and remediation.
Source: Tom's Hardware


