"The issues rated CRITICAL require either non-default configuration or uncommon setups," the PHP security team warned on Wednesday, as it pushed urgent updates on Thursday, November 19, to close a set of vulnerabilities affecting all supported PHP versions.
CVE-2026-129289: PHP-FPM request smuggling and remote code execution
The most serious fix in the November release is CVE-2026-129289, a PHP-FPM request smuggling vulnerability given a CVSS score of 9.2. Security firm Aikido reported that, under certain conditions, the flaw allows unauthenticated attackers to remotely execute PHP code on vulnerable servers that reuse connections to PHP-FPM. The issue specifically affects configurations of nginx, Apache, HAProxy, and LSAPI that reuse backend connections to PHP-FPM; standard nginx and Apache setups that do not reuse backend connections are not vulnerable to this attack.
Other critical remote-code-execution and privilege-escalation fixes
The PHP development team released fixes addressing 18 CVEs that touch PHP's core engine, session handling, PHP-FPM, CGI, and other components. Notable CVEs singled out by Aikido include:
- CVE-2026-129474 — a use-after-free involving magic method backtraces that could lead to remote code execution.
- CVE-2026-129496 — a timezone cache use-after-free that could lead to remote code execution.
- CVE-2026-126714 — a vulnerability involving partially overwritten session files that could lead to remote code execution.
- CVE-2026-115560 — a session serializer mismatch vulnerability that could lead to remote code execution; this issue was previously disclosed in an October 23 informational advisory.
- CVE-2026-129291 — a PHP-FPM epoll use-after-free that could enable local privilege escalation.
- CVE-2026-128090 — a PHAR OpenSSL signature bypass involving an algorithm downgrade.
Beyond these, the updates also address memory corruption, information disclosure, cross-site scripting, denial-of-service problems, and potentially unsafe handling of HTTPS and FTPS URLs.

Your scanner finds 4,000 vulns. Which 12 matter?
Nubivance is a Rapid7 Registered Partner delivering vulnerability management as a service - scanning, risk-based prioritization, and remediation follow-through across IT and OT.
Fix the backlogMitigations recommended by PHP and Aikido
For administrators who cannot immediately install the official security updates, the PHP project and Aikido provided temporary mitigations. To reduce risk from CVE-2026-115560 and related session-handling issues, PHP recommended disabling session upload progress by setting session.upload_progress.enabled=0 and restarting PHP workers; that same setting was previously recommended to mitigate recent PHP2Shell flaws.
For CVE-2026-129289, administrators who cannot apply the November patches were advised to disable persistent backend connections between web servers and PHP-FPM so that connections are closed after each request. Aikido cautioned that these mitigations do not cover all vulnerabilities in the release and further recommended ensuring that PHP-FPM and LSAPI listeners are not directly exposed to untrusted networks.
Third-party backports and hardened images from Ondrej Surý and Aikido
While the official security updates apply only to supported PHP branches, third parties moved quickly to help users running older, unsupported releases. Maintainer Ondrej Surý released patched packages for unsupported PHP versions dating back to PHP 5.6. Aikido published hardened PHP container images that include backported security fixes for unsupported versions, listing PHP 5.6, 7.0, 7.1, 7.2, 7.4, and 8.1 among those covered.
What this means for administrators, technologists, and adversaries
- Administrators: The PHP dev team urged upgrades to the patched supported branches — PHP 8.5.13, 8.4.28, 8.3.37, or 8.2.36 — depending on which branch an environment is running. Where immediate upgrades are not feasible, the published mitigations (disabling session.upload_progress and disabling persistent backend connections) are stopgaps, not full fixes.
- Technologists and security teams: Teams should audit web server–to–PHP-FPM connection reuse, review exposure of PHP-FPM and LSAPI listeners to untrusted networks, and plan rapid deployment of the official updates or trusted backports. Systems using non-default or uncommon configurations should be treated with particular urgency, as the PHP security team identified those setups as enabling the critical issues.
- Adversaries and threat actors: According to Aikido, several of the patched flaws permit unauthenticated remote code execution if configurations reuse backend connections to PHP-FPM; those conditions present an exploitable path where the mitigations or patches are not applied.
On November 19 the PHP project published the fixes across all supported branches; administrators and maintainers now have a choice between applying official updates, using vetted third-party backports and hardened container images, or deploying the recommended mitigations. Given that some of the highest-rated issues rely on uncommon or non-default configurations, inventorying those setups and closing exposed PHP-FPM and LSAPI listeners will be an immediate priority for teams that cannot patch at once.




