The PHP development team and the PHP Foundation have released scheduled security updates resolving 18 vulnerabilities across all actively supported branches. The updates, published on November 19, include multiple critical vulnerabilities that could allow unauthenticated attackers to execute arbitrary code remotely on affected web servers.

The releases arrive four weeks after patches for the heavily exploited PHP2Shell vulnerabilities, as reported by SecurityWeek. Ahead of the rollout, the PHP maintainers warned that several of the flaws carried critical ratings, though triggering the highest-severity defects generally requires non-default configurations or uncommon application designs.

Critical Vulnerabilities in PHP-FPM and Core Components

According to security firm Aikido, as cited by BleepingComputer, the update covers 18 Common Vulnerabilities and Exposures (CVEs) spread across PHP's core engine, PHP FastCGI Process Manager (PHP-FPM), session handling, and CGI modules.

Among the most severe issues is CVE-2026-129289, a critical HTTP request smuggling vulnerability carrying a CVSS score of 9.2. The bug stems from inconsistent interpretation of HTTP requests between front-end proxies and backend workers. Exploitation allows an attacker to execute PHP code remotely without user interaction if an application path opens php://input without fully reading it, and the front-end environment reuses backend connections.

Additional vulnerabilities with a 9.2 CVSS rating addressed in this release include:

  • CVE-2026-115560: An improper input validation and session serializer mismatch flaw where changing the serialize handler at runtime before starting a session can allow remote code execution when upload progress is enabled.
  • CVE-2026-126714: A time-of-check time-of-use (TOCTOU) flaw in session handling dubbed "phpAfterShell" by security firm Depthfirst, detailed by The Hacker News.
  • CVE-2026-129496: A timezone cache use-after-free issue that allows an unauthenticated remote attacker to crash workers or execute code.
  • CVE-2026-129474: A use-after-free defect involving magic method backtraces in PHP 8.5 and later.
  • CVE-2026-129481: A session cleanup use-after-free flaw that can corrupt memory or lead to code execution.
  • CVE-2026-129182: A core engine use-after-free vulnerability leading to memory corruption and potential code execution.

The patch batch also resolves CVE-2026-129291, a CVSS 8.8 use-after-free bug in PHP-FPM epoll backends that permits local privilege escalation when catch_workers_output is enabled, alongside OpenSSL signature downgrade risks in PHAR archives (CVE-2026-128090).

Mechanism of the phpAfterShell Vulnerability

Research published on CVE-2026-126714 reveals how file-based session handling can be manipulated to trigger unsafe deserialization. When an application process updating session storage via pwrite() or ftruncate() is interrupted—such as through an intentional worker crash or timeout—a partially written session file remains on disk.

This state creates a hybrid file containing the beginning bytes of a new session payload spliced with remaining tail bytes from an older session. By controlling the byte lengths in the prefix, an attacker forces PHP's session parser to interpret arbitrary leftover strings as active serialized objects when session_start() is subsequently called. When paired with native deserialization gadgets, the issue creates an arbitrary code execution vector.

Impact and Affected Configurations

The request smuggling bug (CVE-2026-129289) impacts deployments using web servers or load balancers configured to reuse persistent connections to PHP-FPM or LSAPI. This includes Nginx instances with fastcgi_keep_conn on, Apache environments using mod_proxy_fcgi with enablereuse=on, and HAProxy configurations that retain FastCGI connections. Standard Nginx and Apache setups that close backend connections after each request are not vulnerable to this vector.

The vulnerabilities affect all supported PHP releases: 8.2, 8.3, 8.4, and 8.5. While official support is restricted to these branches, maintainer Ondrej Surý and security firm Aikido have created backported security fixes and hardened containers covering legacy, unsupported versions including PHP 5.6, 7.0 through 7.4, and 8.1.

What You Should Do

System administrators and security teams should apply the latest official releases immediately:

  • Upgrade supported installations to PHP 8.2.36, 8.3.37, 8.4.28, or 8.5.13 (or 8.6.0 where applicable).
  • If patching must be delayed, mitigate CVE-2026-115560 and CVE-2026-126714 by disabling session upload progress. Set session.upload_progress.enabled = 0 in php.ini and restart all PHP-FPM worker pools.
  • To mitigate the PHP-FPM smuggling flaw (CVE-2026-129289), disable persistent backend connections in the front-end web server configuration, forcing FastCGI connections to close after each transaction.
  • Ensure that PHP-FPM and LSAPI listening ports or Unix sockets are isolated and never directly reachable from untrusted external networks.