PHP fixes two remote code execution flaws after AI-assisted research
OpenAI says its models helped researchers in its Patch the Planet initiative discover critical security flaws in PHP, an open-source language used to run an estimated 70% of websites. PHP’s security advisory says both flaws can allow unauthenticated remote code execution.

Key takeaways · 4
- 01
PHP issued fixed releases 8.5.12, 8.4.27, 8.3.36 and 8.2.35.
- 02
PHP says installations serving web requests are at risk, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed.
- 03
Wiz says every PHP version released in the last decade is affected by at least one flaw, going back to version 5.4.
- 04
PHP urges users to update immediately and says there are no complete mitigations.
What the advisories describe
The PHP advisory identifies the vulnerabilities as CVE-2026-109618 and CVE-2026-109619, and says both can enable remote code execution without authentication.[3] One flaw is tied to out-of-memory corruption; the other to stale global state.[3] OpenAI says the flaws are in PHP itself rather than in applications built on the language.[2] The distinction matters for triage: teams should check their PHP runtime, not only review individual PHP applications.[2]
Which systems are in scope
PHP says installations serving web requests are at risk, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed.[3] PHP considers the risk highest for mod_php, where it demonstrated that an unauthenticated request could trigger an attack before application code runs.[3] Wiz says every PHP version released in the last decade is affected by at least one of the two vulnerabilities, reaching back to version 5.4.[4] Wiz also demonstrated unauthenticated remote code execution on WordPress, Drupal and Joomla deployments.[4]
Fixes and response
PHP released fixes in versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35; its advisory is dated 21 October 2026.[3] The PHP team urged all users to update immediately and said updating is the only safe choice because there are no complete mitigations.[3] OpenAI says sites using PHP can also apply mitigations from security vendors.[1] For administrators, the advisory makes upgrading the central response, rather than relying on a workaround alone.[3]
How the discovery was coordinated
OpenAI says it led a two-month coalition of maintainers, researchers and security providers to prepare fixes and protections before disclosure.[1] It says PHP maintainers led the fixes and release, with Wiz and Cloudflare contributing research, technical support and coordination.[2] OpenAI says Calif identified a critical flaw using GPT-5.6 Sol as part of Patch the Planet, while Wiz independently discovered and reported both PHP vulnerabilities.[2] Wiz says frontier models helped researchers develop and adapt working exploits across multiple applications in hours.[4]
For teams that operate PHP services, the advisory points to a direct runtime upgrade task, not just an application-level review. The reported scope and lack of complete mitigations make it useful to prioritize inventory and patch planning around the PHP versions and web-serving configurations in use.
Why it matters
Bring this to your team — one session a day, built for your industry.
kju.ai is built for teams: daily sessions, team analytics, and rollout support for your organization.
For teamsHow this developed
21 October 2026
PHP fixes two remote code execution flaws after AI-assisted research
Sources
- OpenAI on X: \"OpenAI models helped researchers—operating as part of our Patch the Planet initiative—discover critical security flaws in PHP, an open-source programming language used to run an estimated 70% of websites. Over the past two months, we led a coalition of maintainers, researchers, and s… / Xx.com
- Patch the Planet: global response coordination as agents uncover critical vulnerabilities | OpenAIopenai.com
- PHP: News Archive - 2026php.net
- PHP2Shell: AI uncovers critical RCE vulnerabilities affecting 70% of the Internet | Wiz Blogwiz.io
- GPT‑5.6 Sol was used to identify critical PHP flaw. | The Vergetheverge.com