Eighteen New PHP Flaws Including a Critical Request Smuggling Bug Put Web Admins on Alert
The PHP project has shipped fixes for 18 security vulnerabilities across every supported branch, landing in PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36. The headline issue is CVE-2026-129289, a request smuggling flaw rated 9.2 on CVSS that affects PHP-FPM, the FastCGI process manager that executes PHP code behind high-traffic websites and applications. Under certain conditions it can allow an unauthenticated, remote attacker to execute PHP code on an affected server. The remaining fixes touch PHP's core engine, session handling, the process manager and the CGI protocol that bridges web servers to external programs, and cover further remote code execution bugs as well as information disclosure, memory corruption, denial-of-service conditions, unsafe handling of HTTPS and FTPS URLs, and cross-site scripting. The release follows PHP2Shell, the pair of 9.2-rated flaws disclosed in October that forced some government websites offline and attracted what have been estimated at millions of exploit attempts.
CVE-2026-129289 is reachable only where a front-end reuses backend connections to PHP-FPM, and specific nginx, Apache, HAProxy and LSAPI configurations are named as affected. In that setup an attacker can smuggle a request across a reused connection and, when the flaw is paired with a code execution bug, move from the web worker outward toward the rest of the server. The wider batch returns to familiar ground: session upload progress handling, fatal error backtraces, and how the interpreter behaves when it runs out of memory. One of the lower-rated issues turns on a single capital letter, where a URL written as HTTPS:// or FTPS:// with an uppercase S can drop encryption entirely and send passwords, tokens, form data and files in plaintext across the network, including through a redirect. PHP 8.5 is the only branch exposed to the new backtrace flaw, and fatal error backtraces are enabled by default on that branch.
The practical consequence of any PHP code execution flaw is that the attacker inherits whatever the PHP worker can reach, which in most deployments is close to everything the application depends on: the database password, API keys, cloud credentials and live session data. A realistic path runs from entry through the web application, to reading the configuration file, to dumping the customer database, to planting a web shell for later return. Issues that look minor in isolation, such as information disclosure or memory corruption, become materially worse when a determined attacker chains them, and the plaintext URL-scheme bug is a straightforward credential exposure for anyone positioned on the network. Several of the critical items require particular configurations or less common deployment scenarios, which tempers the immediate blast radius, but they still sit inside one of the most widely deployed web runtimes in the world. FIRST's EPSS model currently puts CVE-2026-129289 at a 16.2 percent probability of exploitation within the next 30 days; there is no confirmed in-the-wild exploitation of any of these 18 flaws at the time of writing, and none are listed in CISA's Known Exploited Vulnerabilities catalogue. Exposure assessment is complicated by the fact that a PHP version string alone does not establish risk, because Linux distributions routinely backport fixes without changing it, and because PHP is quietly bundled inside containers, hosting control panels and network appliances that are rarely inventoried. Timing is a further pressure point: PHP 8.2 reaches end of security support on 31 December 2026, making this release potentially one of the last it will receive, while PHP 8.1 and older branches already receive no fixes from the project.
Attack Surface
Web Application, Infrastructure, Server OS
Tactics
Initial Access, Execution, Persistence, Credential Access, Impact
Techniques
- T1190 – Exploit Public-Facing Application
- T1059 – Command and Scripting Interpreter
- T1505.003 – Web Shell
- T1552.001 – Credentials In Files
- T1040 – Network Sniffing
- T1499 – Endpoint Denial of Service
SuperPRO's Threat Countermeasures Procedures
- Upgrade to PHP 8.5.13, 8.4.28, 8.3.37 or 8.2.36 from the 18 November 2026 PHP release, which carries fixes for all 18 vulnerabilities including CVE-2026-129289.
- Treat internet-facing PHP 8.5 servers as first in the queue: it is the only branch exposed to the new fatal error backtrace flaw and backtraces are enabled by default there, so disable argument inclusion in error backtraces on 8.5 workers until the upgrade is complete.
- Audit nginx, Apache, HAProxy and LSAPI front-ends for configurations that reuse or keep alive backend connections to PHP-FPM, since CVE-2026-129289 request smuggling is only reachable in those setups; disable upstream connection reuse to the FastCGI pool as an interim measure where patching is delayed.
- Set session.upload_progress.enabled to Off in php.ini on hosts that do not need it, and review any deployment where several applications share a single session store, as these are the configurations most directly implicated in this release.
- Confirm that php-cgi is not exposed to the internet and that the PHP-FPM status endpoint defined by pm.status_path is unreachable from outside, restricting both to localhost or an explicit administrative IP allow-list.
- Grep application source, libraries and configuration for URL schemes written as HTTPS:// or FTPS:// with an uppercase S, which can disable encryption and send passwords, tokens, form data and files in plaintext, including across redirects.
- Build a true PHP inventory rather than relying on version strings: check distribution package changelogs because backported fixes leave the version unchanged, and enumerate PHP bundled inside containers, hosting control panels and appliances. Plan migration off PHP 8.2 before its 31 December 2026 security support cut-off, and off PHP 8.1 and earlier, which already receive no fixes.