PHP's November Patch Drop Fixes 18 Flaws — and the Worst One Hides in Connection Reuse, Not Your Code
PHP's November Patch Drop Fixes 18 Flaws — and the Worst One Hides in Connection Reuse, Not Your Code
For the second time in six weeks, PHP's weekly cycle has turned into an emergency-response drill. On November 19, the PHP dev team shipped security updates for all supported branches — PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 — fixing a set the PHP Foundation had flagged in advance as containing multiple critical vulnerabilities exploitable "under specific conditions, including non-default configuration or uncommon setups." Aikido counts 18 CVEs across the core engine, session handling, PHP-FPM, CGI and other components; SecurityWeek's tally puts seven of them at critical RCE grade. The project had warned users on Monday that successful exploitation could mean remote code execution, session corruption, denial-of-service, memory corruption or local privilege escalation — and told maintainers to reserve patching time.
The headline flaw is CVE-2026-129289 (CVSS 9.2), and it is unusual: an inconsistent-interpretation bug — in plain terms, request smuggling between a front-end proxy and PHP-FPM over a reused backend connection. An unauthenticated attacker who can influence request framing can get the worker to execute attacker-controlled PHP code, with no other user interaction and no application bug required. Crucially, exposure is a front-end configuration question: only setups that keep FastCGI connections alive are vulnerable — nginx with fastcgi_keep_conn on, Apache mod_proxy_fcgi with enablereuse=on, HAProxy FastCGI setups that retain backend connections, and LSAPI. Standard nginx and Apache configurations that open a fresh connection per request are not affected.
That is not the only path to pre-auth code execution. CVE-2026-115560 (CVSS 9.2) lives in the session upload progress feature: a mismatched decoder can interpret part of session data as serialized objects, so an application with a suitable gadget chain executes code with the worker's privileges — the flaw was publicly disclosed last month, two days after the PHP2Shell fixes landed. CVE-2026-129474 is a use-after-free in magic-method backtraces that reaches RCE when the attacker can influence memory allocation and trigger a fatal error at the right point. CVE-2026-126714 (CVSS 9.2) is a TOCTOU race in partial session writes: with control over session data, an interruption at a useful point and a reachable deserialization gadget chain, it executes code as the PHP worker. Two further use-after-frees, CVE-2026-129182 and CVE-2026-129496 (timezone cache), round out the RCE-capable set. The common thread is sobering: none of these require a bug in your application logic — the runtime itself is the attack surface.
What Should You Do?
- Update now: move to PHP 8.5.13, 8.4.28, 8.3.37 or 8.2.36 depending on your branch. If you're on PHP 8.1 or earlier, you are out of security coverage entirely — treat this as the migration deadline, not a suggestion.
- Check your front-end for connection reuse. If nginx runs
fastcgi_keep_conn on, Apache mod_proxy_fcgi runs withenablereuse=on, or HAProxy/LSAPI keeps FastCGI connections alive, you are in the affected class for CVE-2026-129289 — patch the runtime before anything else. - Audit what session upload progress does for you. CVE-2026-115560 rides a rarely used feature; if your application doesn't need
session.upload_progress, disable it and remove one gadget-delivery path. - Re-check custom gadgets and deserialization. TOCTOU and UAF flaws chain through application gadget classes — review unserialize() usage and magic-method exposure as the durable mitigation.
The WAF Angle
A compromised runtime is why the WAF is an additional layer, not the layer. Request-smuggling flaws like CVE-2026-129289 are the classic WAF blind spot — the front end and the PHP worker disagree about where one request ends and the next begins, so the smuggling payload can slide past a rule engine that parses the front end's view of the stream. Two lessons from earlier coverage hold here: the PHP2Shell engine flaw showed how a runtime bug can be reachable without any application bug; the Apache mod_http2 flaw showed the same for front-end proxies. The practical takeaway is the opposite of comforting: in front of a PHP-FPM origin, terminate and re-canonicalize requests rather than blindly forwarding — and keep your runtime patched, because the WAF can't parse what the worker parses.