The PHP project has released security updates for all supported versions of PHP, fixing 17 security advisories. The most severe, CVE-2026-129289, is a critical request smuggling vulnerability in PHP-FPM that can allow an unauthenticated attacker to execute PHP code on the server.
The releases also fix several other vulnerabilities that can lead to remote code execution (RCE), including CVE-2026-115560, the session upload progress flaw PHP first warned about in October 2026 and for which public exploit code already exists.
PHP states that the critical issues require either non-default configuration or uncommon setups, so not every PHP installation is exposed. However, PHP is one of the most widely deployed web technologies, and this release follows last month's PHP2Shell vulnerabilities, which have seen active exploitation. Organisations should patch promptly.
CVE-2026-129289 affects PHP-FPM, the process manager used by most NGINX-based PHP deployments. According to PHP's advisory, an attacker can send a single request whose unread body is then interpreted as a second, forged FastCGI request on a reused connection. The forged request can choose which script runs and change administrator-level PHP settings, which can lead to execution of attacker-controlled PHP code.
The main conditions PHP lists for the attack are:
The other notable vulnerabilities fixed in this release are:
|
CVE |
Component |
Issue |
Fixed in |
|
CVE-2026-115560 |
Session |
Serializer mismatch can lead to RCE |
All branches |
|
CVE-2026-126714 |
Session |
Partially overwritten session files can lead to RCE |
All branches |
|
CVE-2026-129496 |
Date |
Timezone cache use-after-free can lead to RCE |
All branches |
|
CVE-2026-129474 |
Core |
Use-after-free in magic method backtraces can lead to RCE |
8.5 only |
|
CVE-2026-129538 |
PHP-CGI |
Out-of-bounds read and write during PATH_INFO correction |
All branches |
|
CVE-2026-129291 |
PHP-FPM |
Use-after-free can lead to local privilege escalation |
8.3, 8.4, 8.5 |
NOT VENDOR-CONFIRMED. Only the severity of CVE-2026-129289 has been verified against PHP's own advisory. Third-party reporting describes CVE-2026-115560, CVE-2026-126714, CVE-2026-129496 and CVE-2026-129474 as also rated Critical, each requiring specific conditions.
|
PHP Branch |
Status |
Fixed In |
|
8.5.0 - 8.5.12 |
Vulnerable |
8.5.13 |
|
8.4.0 - 8.4.27 |
Vulnerable |
8.4.28 |
|
8.3.0 - 8.3.36 |
Vulnerable |
8.3.37 |
|
8.2.0 - 8.2.35 |
Vulnerable |
8.2.36 |
|
8.1 and older |
Unsupported |
No fix from the PHP project |
PHP states that the flaw behind CVE-2026-129289 dates back to PHP 5.6.0, so unsupported versions should be assumed vulnerable. Some Linux distributions and long-term support vendors provide backported fixes. Distribution, container and hosting-panel packages may become available later than the official PHP release. PHP 8.2 reaches end of life on 31 December 2026
Several factors influence the likelihood of exploitation:
Successful exploitation may result in:
No vendor-published indicators of compromise are available. The following are general hunting leads based on how the vulnerabilities behave, and should not be treated as confirmed indicators:
Where patching is not immediately possible, PHP recommends the following:
References
session.upload_progress.enabled=0