PHP November 2026 Security Release Deep Dive: Mitigating CVE-2026-129289 PHP-FPM Request Smuggling and CVE-2026-115560 Serializer Mismatch (8.5.13 · 8.4.28 · 8.3.37 · 8.2.36)
A technical deep dive into the November 19, 2026 PHP security releases (8.5.13, 8.4.28, 8.3.37, 8.2.36) patching 18 CVEs including seven Critical (CVSS 9.2) vulnerabilities. Examines CVE-2026-129289 PHP-FPM FastCGI request smuggling via unread php://input streams, CVE-2026-115560 session upload progress serializer mismatch RCE, and administrative mitigations for the five Critical Use-After-Free and session flaws without WAF coverage.
PHP November 19, 2026 Critical Security Release (8.5.13, 8.4.28, 8.3.37, 8.2.36) Architecture: CVE-2026-129289 PHP-FPM FastCGI Request Smuggling via unread php://input, CVE-2026-115560 Session Upload Progress Serializer Mismatch, and the 5 Unfilterable Critical CVEs
The defining takeaway of the November 19, 2026 PHP security release (8.5.13, 8.4.28, 8.3.37, 8.2.36) is that neither a perimeter WAF rule group nor a standalone session.upload_progress.enabled=0 toggle can block all seven Critical (CVSS 9.2) remote code execution and memory corruption paths—making an immediate binary upgrade paired with FastCGI connection-reuse auditing and shared session store isolation mandatory.
On November 19, 2026, the PHP Foundation published urgent security updates across every supported branch—PHP 8.5.13, 8.4.28, 8.3.37, and 8.2.36—in the official PHP 2026 News Archive. The release patches 18 CVEs, including seven Critical vulnerabilities rated CVSS 9.2 (Aikido Security Analysis, AWS Security Bulletin 2026-190-AWS). At the center of this release are CVE-2026-129289 (GHSA-qc49-hpvq-g2w6), a critical PHP-FPM request smuggling vulnerability triggered by unread php://input body bytes over persistent FastCGI connections, and CVE-2026-115560 (GHSA-658j-r8rw-q6mx), the engine-level fix for the session upload-progress serializer mismatch RCE first previewed in late October.
This deep dive cross-verifies the official php/php-src GitHub Security Advisories, AWS Security Bulletin 2026-190-AWS, the KISA KrCERT security notice, and Classmethod's Amazon Linux 2023 package verification report. We did not execute live exploit payloads against production clusters; all architectural boundaries and mitigation steps below are derived directly from the upstream advisories and verified vendor bulletins.
1. Why the October PHP2Shell Patch and Perimeter WAF Rules Are Not Enough
Engineering teams evaluating the November 19 release frequently run into two dangerous misconceptions:
- "We already patched
PHP2Shellin late October and setsession.upload_progress.enabled=0, so we are covered": The October 21, 2026 releases (8.5.12,8.4.27,8.3.36,8.2.35) fixedPHP2Shell(CVE-2026-109618andCVE-2026-109619), notCVE-2026-115560or the 17 new CVEs introduced in the November release (Aikido Security). Disablingsession.upload_progress.enabledremoves the published attack path forCVE-2026-115560and hardens againstCVE-2026-126714, but it provides zero protection against PHP-FPM request smuggling (CVE-2026-129289) or the core, session, and date Use-After-Free vulnerabilities.
- "Enabling AWS WAF Managed Rules gives us a complete shield until our next quarterly maintenance window": According to AWS Security Bulletin 2026-190-AWS, version 2.6 of the AWS WAF PHP Managed Rule Group adds two rules—
PHPFPMSmuggling_BODYandPHPUploadProgressSerializedObject_BODY—covering onlyCVE-2026-129289andCVE-2026-115560. For the remaining five Critical (CVSS 9.2) vulnerabilities (CVE-2026-126714,CVE-2026-129481,CVE-2026-129474,CVE-2026-129182, andCVE-2026-129496), AWS explicitly states that no high-confidence WAF rule is viable because the triggering requests look identical to normal serialized session writes, valid JSON payloads, or standard oversized uploads.
Put simply, filtering binary FastCGI frames or serialized object strings at an HTTP edge proxy and eliminating socket-drain bugs and post-shutdown Use-After-Free conditions inside the PHP worker lifecycle are two completely separate security boundaries.
2. Inside CVE-2026-129289 (CVSS 9.2): Lazy php://input Streams and PHP-FPM Request Smuggling
Detailed in GHSA-qc49-hpvq-g2w6, CVE-2026-129289 (CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N, score 9.2, CWE-444 / CWE-670) allows an unauthenticated attacker to cross the HTTP-to-FastCGI trust boundary and execute arbitrary PHP code with worker privileges in a single HTTP request—without requiring memory corruption, ASLR bypasses, or race conditions.
2.1 Root Cause: Why Opening php://input Skipped Socket Buffer Cleanup
FastCGI and LSAPI connections can multiplex or carry multiple sequential requests over a single persistent TCP or Unix socket. Before PHP accepts a new request on the same connection, it must either consume the previous HTTP request body in full or close the socket.
The flaw originated in PHP 5.6.0 when lazy php://input stream handling was introduced (GHSA-qc49-hpvq-g2w6):
- Opening
php://inputcreates a request-body stream wrapper, but PHP reads the underlying socket bytes lazily on demand.
- During request shutdown, vulnerable PHP versions mistakenly treated the mere existence of an opened
php://inputstream as proof that the request body had already been consumed, skipping the normal shutdown drain routine that discards unread input bytes.
- An attacker can send a crafted, malformed
multipart/form-datarequest body designed to make PHP's multipart parser stop at a predictable byte offset. If the application—or a request framework/middleware that instantiates an input stream prior to routing or authentication—opensphp://inputwithout reading it toEOF, attacker-controlled bytes remain queued in the backend connection buffer.
- When
FCGI_KEEP_CONN(persistent backend connection reuse) is enabled on the reverse proxy, PHP-FPM preserves the socket and immediately starts reading the next FastCGI record. Because the vulnerable FPM implementation discarded its state tracking that it was still inside an incompleteFCGI_STDINrecord, a forged FastCGI frame placed at that exact body offset is accepted and executed as a brand-new FastCGI request that never passed through front-end routing or authentication.
2.2 Exploitation Mechanics: Forged PHP_ADMIN_VALUE and Persistent Worker Poisoning
Because the smuggled payload is parsed as a raw FastCGI request, the attacker gains full control over FastCGI environment parameters including SCRIPT_FILENAME, REMOTE_ADDR, and PHP_ADMIN_VALUE (GHSA-qc49-hpvq-g2w6):
- By pointing
SCRIPT_FILENAMEto any known PHP script on disk (such as/var/www/html/index.php) and injectingallow_url_include=1andauto_prepend_file=php://inputviaPHP_ADMIN_VALUE, the forged request forces PHP-FPM to execute the smuggled request's own body as PHP code.
- Even worse, administrator settings altered via
PHP_ADMIN_VALUEcan remain active in that FPM worker process for subsequent legitimate requests served by the same worker.
- For LiteSpeed LSAPI environments, the shared cleanup bug can also leave unread body bytes on a persistent connection and desynchronize the request stream, though LSAPI does not use the FastCGI
PHP_ADMIN_VALUEparameter mechanism.
2.3 Exposed Proxy Configurations vs. Safe Defaults
Exploitation of CVE-2026-129289 requires both (1) a front end configured for persistent backend connection reuse and (2) an application code path that opens php://input without reading it to the end:
- Exposed Front-End Configurations:
- Nginx with
fastcgi_keep_conn on; - Apache HTTP Server
mod_proxy_fcgiwithenablereuse=on - HAProxy FastCGI backends retaining persistent connections
- LSAPI persistent backend connections (stream desynchronization impact)
- Unexposed Default Configurations: Standard Nginx (
fastcgi_keep_conn offby default) and Apache (enablereuse=offby default) setups that close the FastCGI socket after every request are not vulnerable to the demonstrated attack.
- Why Application-Level
stream_get_contents()Is Not Enough: While readingphp://inputtoEOFprevents the unread-body condition on the happy path, PHP's official advisory warns that exception handling paths, memory exhaustion, and early shutdown can still leave unread bytes on the socket. The patch in8.5.13,8.4.28,8.3.37, and8.2.36drains input based on whether the body was actually consumed (independently of whether aphp://inputstream exists) and forces PHP-FPM to close the connection whenever the prior FastCGI input record is incomplete.
3. Inside CVE-2026-115560 (CVSS 9.2): Session Upload Progress Serializer Mismatch and Cross-Pool Contamination
Published in full detail in GHSA-658j-r8rw-q6mx, CVE-2026-115560 is a configuration-dependent deserialization vulnerability present since session upload progress was introduced in PHP 5.4.0 (and distinct from the stale global state vulnerability CVE-2026-109619 fixed in October).
3.1 How Pipe (|) Delimiter Injection Triggers Guzzle and Monolog Gadget Chains
When session.upload_progress.enabled is active (PHP's historical default prior to this release), PHP intercepts multipart/form-data uploads during request input parsing, appends the user-supplied PHP_SESSION_UPLOAD_PROGRESS field to an upload-progress session key, and persists the session record immediately.
- Format Asymmetry: PHP's legacy
phpsession serializer separates each session key from its serialized value using a pipe character (|). In contrast,php_serializeandphp_binaryencode keys structurally without treating|as a field boundary.
- Cross-Serializer Confusion: If an attacker submits a multipart upload to a context whose
session.serialize_handlerisphp_serializeorphp_binary, they can inject a|delimiter followed by a serialized PHP object payload inside thePHP_SESSION_UPLOAD_PROGRESSkey. (Even the 127-byte key limit inphp_binarydoes not stop payloads split across multiple session records.)
- Gadget Execution Before Record Rejection: When a subsequent or concurrent request reads that same session ID using the
phpserializer, the decoder splits on the attacker's|and feeds the trailing bytes inside the key directly into PHP'sunserialize()engine. Even if trailing data later causes the session decoder to reject the record, candidate objects have already been instantiated and their__wakeup()or__destruct()magic callbacks invoked. The official advisory confirms full command execution reproduced with Guzzle and Monolog 2.11.1 gadget chains on PHP8.2.35,8.3.36,8.4.27, and8.5.12(GHSA-658j-r8rw-q6mx).
3.2 The Post-Patch Architectural Gotcha: Shared Session Stores Across Separate FPM Pools
The November 19 releases harden the engine in two ways (AWS Security Bulletin 2026-190-AWS, GHSA-658j-r8rw-q6mx):
- New Safe Default:
session.upload_progress.enabledis now disabled (0) by default.
- Runtime Swap Rejection: PHP now rejects runtime changes to
session.serialize_handler(such asini_set('session.serialize_handler', 'php')) while upload progress is active.
However, GHSA-658j-r8rw-q6mx explicitly warns that the upstream patch does NOT enforce matching serializers across separate configurations. If an installation explicitly re-enables session upload progress, an application that never calls ini_set() at runtime can still be exploited if two separate PHP-FPM pools, virtual hosts, or CLI cron jobs share the same session storage directory (/var/lib/php/sessions) or Redis/Memcached cluster with mismatched session.serialize_handler settings.
4. Complete 18-CVE Technical Matrix and WAF Coverage Boundaries
The table below synthesizes all 18 CVEs fixed in PHP 8.5.13, 8.4.28, 8.3.37, and 8.2.36, mapping their affected components, CVSS severity ratings, AWS WAF PHP Managed Rule Group v2.6 coverage, and pre-patch administrative mitigations (Aikido Security, AWS Security Bulletin 2026-190-AWS).
| CVE ID | Component | Severity (CVSS) | Vulnerability Mechanism & Impact | AWS WAF v2.6 Rule & Interim Mitigation |
| CVE-2026-129289 | FPM / LSAPI | Critical (9.2) | Unread php://input HTTP body bytes left on a persistent FastCGI socket (FCGI_KEEP_CONN) are parsed as a smuggled FastCGI request, enabling single-request unauthenticated RCE | Covered by PHPFPMSmuggling_BODY · Disable backend connection reuse (fastcgi_keep_conn off / enablereuse=off) |
| CVE-2026-115560 | Session | Critical (9.2) | Upload-progress session data written via php_serialize/php_binary and read via php triggers object deserialization RCE (Guzzle/Monolog gadgets) via | key delimiter injection | Covered by PHPUploadProgressSerializedObject_BODY · Set session.upload_progress.enabled=0 in php.ini or FPM pool |
| CVE-2026-126714 | Session | Critical (9.2) | Partially overwritten session files from interrupted server-side writes can lead to remote code execution upon subsequent session reads | No WAF rule available (resembles normal traffic) · Upgrade PHP binary and set session.upload_progress.enabled=0 |
| CVE-2026-129481 | Session | Critical (9.2) | Use-After-Free memory corruption when a stale worker handles subsequent requests after an interrupted session shutdown (affects PHP 8.3, 8.4, 8.5) | No WAF rule available · Set pm.max_requests=1 and restart FPM workers until patched (incurs performance overhead) |
| CVE-2026-129474 | Core | Critical (9.2) | Use-After-Free in magic-method backtraces leading to remote code execution (affects PHP 8.5) | No WAF rule available · Set zend.exception_ignore_args=1 (recommended production value) or fatal_error_backtraces=0 |
| CVE-2026-129182 | Core | Critical (9.2) | Use-After-Free via repopulation of the last fatal error backtrace global after request shutdown | No WAF rule available · Set fatal_error_backtraces=0 in administrative configuration and restart workers |
| CVE-2026-129496 | Date | Critical (9.2) | Timezone cache Use-After-Free triggered when formatting diagnostic log timestamps on requests exceeding input limits or malformed uploads | No WAF rule available · Fix startup diagnostic warnings and route logs to syslog to avoid the timestamp formatting path |
| CVE-2026-129291 | FPM | High / Medium | PHP-FPM epoll Use-After-Free leading to local privilege escalation (LPE) | Upgrade to PHP 8.5.13 / 8.4.28 / 8.3.37 / 8.2.36 and restart FPM master and workers |
| CVE-2026-129292 | FPM | Medium | Cross-site scripting (XSS) on the PHP-FPM status endpoint via unescaped user and script fields | Restrict external access to FPM status page and upgrade PHP |
| CVE-2026-129538 | CGI | High | PHP-CGI out-of-bounds read and write during PATH_INFO correction | Upgrade PHP and audit legacy CGI execution endpoints |
| CVE-2026-129501 | DOM | High / Medium | Double free memory corruption during DOM XML serialization | Upgrade to patched PHP release |
| CVE-2026-128090 | Phar | High / Medium | OpenSSL signature verification bypass in Phar archives via algorithm downgrade | Block untrusted Phar archives and upgrade PHP |
| CVE-2026-15353 · 129506 | SOAP | High / Medium | Information disclosure through malformed array dimensions ( 15353) and Use-After-Free when processing DTD entity references (129506) | Validate external SOAP payloads and upgrade PHP |
| CVE-2026-128064 · 127960 | Standard | Medium | Mixed-case HTTPS/FTPS URLs exposing data in plaintext (128064) and DoS via folded HTTP response headers (127960) | Normalize stream wrapper URL schemes to lowercase and upgrade PHP |
| CVE-2026-129438 · 48841 | URI | Medium | Incorrect RFC 3986 URI serialization for oversized input ( 129438) and upgrade to uriparser 1.0.3 (48841) | Upgrade to PHP 8.5.13 or later |
Note the lifecycle exposure as well: PHP 8.1 and earlier have reached End of Life (EOL) and receive no upstream fixes from the PHP Foundation, even though CVE-2026-129289 (present since PHP 5.6.0) and CVE-2026-115560 (present since PHP 5.4.0) affect them directly (AWS Security Bulletin 2026-190-AWS). Furthermore, PHP 8.2 reaches EOL on December 31, 2026, so teams patching to 8.2.36 should schedule their migration to PHP 8.4 or 8.5 immediately.
5. Verification Script and Administrative Hardening Snippets
Use the diagnostic script and configuration templates below to verify your fleet before and after applying the November 19 security update.
5.1 One-Step CLI, FPM Pool, and Reverse-Proxy Audit Script
This script checks the active PHP version against the November 19 patched builds, inspects effective INI values for the Critical CVEs, scans Nginx/Apache configs for FastCGI connection reuse, and flags runtime serializer overrides or php://input usage in application code:
5.2 Hardened PHP-FPM Pool & Nginx FastCGI Configuration
As emphasized in GHSA-658j-r8rw-q6mx, session.upload_progress.enabled=0 must be enforced administratively before request input is parsed—calling ini_set() inside application code or relying on an FPM .user.ini file is too late. Apply the hardening directly in php.ini or your FPM pool definitions:
In Nginx, ensure fastcgi_keep_conn remains disabled until every upstream PHP-FPM worker is patched:
5.3 Amazon Linux 2023 Repository Pinning Gotcha
As verified in Classmethod's Amazon Linux 2023 testing report, freshly launched AL2023 instances using the latest AMI install the fixed PHP packages (8.5.13, 8.4.28, 8.3.37, 8.2.36) out of the box, whereas existing AL2023 instances locked to an older repository release version will install pre-fix builds (such as 8.4.24) if updated without advancing --releasever. Always specify --releasever=latest and restart php-fpm:
6. Operational Remediation Checklist
- Step 1 (Upgrade Binaries & Restart Workers): Have all production and staging workloads been upgraded to PHP 8.5.13, 8.4.28, 8.3.37, or 8.2.36, and have all
php-fpmmaster/worker processes been restarted (or container images rebuilt and redeployed)?
- Step 2 (Audit FastCGI Connection Reuse —
CVE-2026-129289): On any unpatched or legacy EOL hosts, have you disabled Nginxfastcgi_keep_conn on, Apachemod_proxy_fcgi enablereuse=on, and HAProxy FastCGI backend keep-alive, and confirmed that FPM/LSAPI listeners are never exposed directly to untrusted networks?
- Step 3 (Verify Session Serializer Uniformity —
CVE-2026-115560): Have you enforcedsession.upload_progress.enabled=0inphp.ini/ FPM pool configs, and confirmed that any FPM pools, virtual hosts, or CLI workers sharing a session directory or Redis/Memcached store use the exact samesession.serialize_handler?
- Step 4 (Transition AWS WAF v2.6 Rules Safely): If you use AWS WAF, have you pinned the PHP Managed Rule Group to version 2.6, evaluated
PHPFPMSmuggling_BODYandPHPUploadProgressSerializedObject_BODYinCountmode against your legitimate upload traffic, and promoted them toBlock?
- Step 5 (Accelerate EOL Branch Migrations): Have you scheduled immediate upgrades for unpatched PHP 8.1 and older workloads, and finalized your migration plan off PHP 8.2 before its December 31, 2026 End of Life?
References
Korean version:
PHP 11월 긴급 보안 패치 해부: CVE-2026-129289 PHP-FPM 요청 스머글링과 CVE-2026-115560 직렬화 불일치 대응 가이드 (8.5.13 · 8.4.28 · 8.3.37 · 8.2.36)