Threat Advisories

Critical PHP Security Release: PHP-FPM Request Smuggling (CVE-2026-129289) and Multiple Remote Code Execution Vulnerabilities

Written by Integrity360 | Nov 20, 2026, 8:10:45 AM

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.

Key Findings

  • PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 were released on 19 November 2026 as security releases.
  • CVE-2026-129289 is rated Critical by PHP with a CVSS v4.0 score of 9.2.
  • Exploitation of CVE-2026-129289 requires no authentication, no memory corruption and no non-default PHP configuration, but does depend on how the web server connects to PHP-FPM.
  • Standard NGINX and Apache setups that close the FastCGI connection after each request are not affected by the demonstrated attack.
  • Four further vulnerabilities are described by PHP as able to lead to remote code execution.
  • PHP 8.1 and older no longer receive fixes from the PHP project.
  • No exploitation in the wild has been reported, and none of the vulnerabilities is in CISA's Known Exploited Vulnerabilities (KEV) catalogue.

Technical Overview

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 web server reuses connections to PHP-FPM, for example NGINX with fastcgi_keep_conn on or Apache mod_proxy_fcgi with enablereuse=on.
  • The application opens the request body (php://input) without reading it to the end. PHP notes that some frameworks do this before routing or authentication.
  • The attacker knows the path to an existing PHP script on the server.

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.

Affected Versions

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 

Threat Assessment

Likelihood: Moderate

Several factors influence the likelihood of exploitation:

  • Very broad deployment of PHP across internet-facing websites and applications.
  • No authentication requirement for the most severe vulnerability.
  • Public exploit code already available for CVE-2026-115560.
  • Heightened attacker interest in PHP following exploitation of PHP2Shell.
  • Exploitation is limited by the need for specific, non-default configurations.

Potential Impact: Critical

Successful exploitation may result in:

  • Remote code execution on web and application servers.
  • Bypass of access controls through a spoofed client address.
  • Persistent changes to PHP settings affecting later requests.
  • Data theft, web shell deployment and lateral movement.

Indicators of Potential Exploitation

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:

  • PHP-FPM worker processes spawning unexpected child processes.
  • Malformed multipart/form-data requests sent to endpoints that do not accept uploads.
  • PHP scripts being executed that are not reachable through normal web server routes.

Recommended Mitigations

Immediate Actions

  1. Identify PHP systems. Inventory PHP versions across web servers, containers and hosting platforms, and note which use PHP-FPM.
  2. Apply vendor patches. Upgrade to PHP 8.5.13, 8.4.28, 8.3.37 or 8.2.36, or to a distribution package that includes these fixes.
  3. Restart PHP after upgrade. Restart PHP-FPM and web server workers so the new version is in use.

Temporary Mitigation

Where patching is not immediately possible, PHP recommends the following:

  • Disable connection reuse between the web server and PHP-FPM. Keep NGINX fastcgi_keep_conn off and Apache enablereuse off. This addresses CVE-2026-129289 only.
  • Do not expose PHP-FPM listeners directly to untrusted networks.
  • Disable session upload progress and restart PHP workers. This addresses CVE-2026-115560.

References

session.upload_progress.enabled=0

 
If you are worried about any of the threats outlined in this bulletin or need help in determining what steps you should take to protect yourself from the most material threats facing your organisation, please contact your account manager, or alternatively get in touch to find out how you can protect your organisation.