PHP Fixes Two Critical Flaws That Can Let an Attacker Run Code Without a Login
1Two Flaws in PHP Can Let a Request With No Login Run Code on the Server
The PHP project maintains PHP, a programming language for web applications. It released fixes for two critical flaws on October 21, 2026 and told everyone running PHP to update immediately. Both flaws sit in the PHP interpreter, the software that executes a web application's PHP code on the server. One concerns how PHP handles running out of memory, the other data that survives from one request to the next. Either flaw can let an attacker run their own code on that server without logging in. The project says every installation that serves web requests is at risk, most of all mod_php, the setup that runs PHP as a module inside the Apache web server. For teams that cannot update at once, it lists stopgap settings. It asks for several of them in php.ini, the FPM pool or the Apache configuration, where applications cannot override them.
We consider the risk highest for mod_php, with a demonstrated exploit where an unauthenticated request can trigger the attack before any application code runs.
PHP, Security advisory: Critical remote code execution vulnerabilities, update now, October 21, 2026
The fixed versions are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Because Linux distributions and long-term support vendors received the patches in advance, the project tells their users to check with the vendor for updated packages. PHP 8.1 and older no longer get updates from the project. Given the severity, the project's security team still published minimal source backports for PHP 7.4, 8.0 and 8.1.
2The Stopgap Settings Leave Attack Paths Open
Each flaw comes with its own settings for teams that cannot update yet. For the memory flaw, CVE-2026-109618, PHP recommends removing PHP's per-request memory limit, which takes away the memory failure an attacker can trigger, and keeping the maximum POST body size low. For the stale-state flaw, CVE-2026-109619, which lets data left over from one request carry into a later one handled by the same worker process, the stopgaps are turning off session upload progress, a feature that tracks a file upload in the visitor's session, and on PHP 8.5 turning off fatal error backtraces, then restarting every worker. The project says these measures reduce exposure to specific attack paths and do not make an installation safe.
There is no complete generic configuration mitigation as an application, extension or server path may publish stale state or consume it without a predictable log entry.
PHP, GHSA-6wmf-4rv5-p3rp: RCE via stale global state, October 21, 2026
Two days later, the project followed up with an informational advisory. It recommends keeping session upload progress off even after the update, until the next regular release. That closes a third, unlikely variant, which needs an unusual combination of configuration and application code.
Source: PHP, Security advisory: Critical remote code execution vulnerabilities, update now, October 21, 2026.

