The PHP project has swiftly released fixes for two vulnerabilities that allow unauthorized access to web servers, following a leak that expedited their disclosure. Both French and European cybersecurity centers are urging the isolation of servers that cannot be promptly updated. However, identifying where PHP runs, including in third-party products that may not disclose its use, poses an additional challenge.
PHP powers a significant portion of the web, from content management systems like WordPress, Drupal, and Joomla to various custom applications. Consequently, vulnerabilities within PHP itself can impact all these applications, regardless of the software layered on top. On October 21, the PHP project addressed this issue by releasing versions 8.5.12, 8.4.27, 8.3.36, and 8.2.35 of its interpreter, which corrected vulnerabilities CVE-2026-109618 and CVE-2026-109619. Both are critical remote code execution vulnerabilities rated 9.2 out of 10 on the CVSS v4 scale.
The first vulnerability stems from poorly handled memory overflow, which disrupts PHP during query preparation, leaving half-initialized data that cleanup routines then mistakenly consider valid. The second is related to an internal state that persists after memory has been freed, allowing the next request processed by the same instance to reuse it. All web server execution modes are affected, including PHP-FPM, Apache’s mod_php, php-cgi, FrankenPHP, and LiteSpeed. PHP maintainers view mod_php as the highest risk environment, where a single unauthenticated request can trigger an attack before the application even begins executing.
The Blind Spot: PHP Embedded in Third-Party Products
The CERT-FR, France’s governmental cybersecurity incident response team, recommends isolating affected systems and migrating to a maintained version in its alert CERTFR-2026-ALE-014. Similarly, the European CERT has echoed this advice in its advisory 2026-018, urging that exposed applications be severed from public networks until the patch is applied and verified. This isolation directive assumes that an inventory of systems is maintained, which many organizations struggle to keep current, as PHP is not limited to servers managed directly by IT departments. The language is also present in appliances, administration consoles, and products from other vendors that do not disclose its inclusion. CERT-EU has referred organizations to the php2shell repository created by the Dutch National Cyber Security Centre (NCSC-NL) for assistance in identifying affected products.
According to Palo Alto Networks’ Unit 42, there are approximately 22.6 million potentially vulnerable PHP instances exposed on the internet. This figure was derived from telemetry from their Cortex Xpanse service, although the methodology was not disclosed. Containers and serverless environments further complicate the situation, as an image built with a PHP version retains it until rebuilt. Google Cloud illustrates this with its services; while recent standard App Engine environments have been automatically updated, flexible App Engine and Cloud Run, lacking automatic updates for base images, require manual rebuilding and redeployment by users.
A Leak and Exploitation Attempts the Same Day
On October 20, the PHP project announced a forthcoming release for the next day at 14:00 UTC, reserving the right to move it up if details leaked beforehand. According to watchTowr, a company specialized in attack surface management, such details indeed surfaced online on October 20, prior to the coordinated disclosure. In response, Cloudflare deployed application firewall rules to counter the vulnerabilities before their public release.
Active exploitation attempts targeting the two CVEs began on October 21, as reported by watchTowr, though specific volumes of such attempts were not provided. It is essential to note that a failed attempt is distinct from a successful compromise, and Huntress, a provider of detection services for SMEs, reported no successful exploitation among its clients as of the evening of October 21. The time between the publication of a critical patch and its first exploitation is now measured in hours. The PHP project has suggested temporary mitigations, such as disabling session upload progress or raising configurable memory limits. Nevertheless, it emphasizes that only a proper update fully addresses the vulnerabilities, with these adjustments merely blocking confirmed attack vectors.
A Known Flaw Since 2004, Now Exploitable with AI
The root of these vulnerabilities lies in long-standing research that recent tools have finally brought to fruition. Calif, a security research firm invited by OpenAI as part of its Patch the Planet initiative, claims to have identified the memory overflow vulnerability on August 1, with assistance from an AI agent and code analysis tool. Calif reported the issue to the PHP project on August 11. This finding builds on earlier work by Stefan Esser, a German researcher who first detailed an attack exploiting PHP’s memory limits back in 2004, as well as a bug reported in the project’s issue tracker in 2020. In 2024, Quarkslab also identified a related issue during an audit funded by OSTIF, a fund that supports the security of open-source software, though no fix followed as no exploitation was demonstrated.
Wiz Research, the research team from cloud security vendor Wiz, confirmed on August 19 that their Gemini 4 Argon and GPT-5.6 Sol models could achieve unauthorized code execution on Drupal, followed by WordPress within two days. These independent discoveries indicate that AI can significantly lower the cost of demonstrating exploit validity on longstanding flaws. For IT departments, the implications are twofold: older vulnerabilities are being exposed and addressed by maintainers, but critical fixes are emerging at a pace that quarterly maintenance cycles can no longer accommodate.
PHP 8.1 Unpatched, PHP 8.2 Approaching End of Life
Updating remains the only comprehensive remedy, yet the issue persists with older versions. The PHP project no longer issues patches for PHP 8.1 and earlier versions, directing users to Linux distributions and extended support vendors that have received the fixes in advance. Minimal backports of source code for PHP 7.4, 8.0, and 8.1 have been published solely for those who compile their own versions. Notably, the community repository rpms.remirepo.net, popular among Red Hat-family distributions, had not been updated by the time of the patch’s release, prompting the project to recommend switching to official distribution packages.
The next deadline is fast approaching, as PHP 8.2 will no longer receive security patches after December 31, 2026. Any application still running on PHP 8.2 at the time of the next critical vulnerability will face a fate similar to what environments on PHP 8.1 currently contend with. Thus, the urgent inventory established this week also serves as a crucial starting point for migration planning, which remains the only sustainable protection against future vulnerabilities within the language.



