The PHP project has shipped security updates fixing 17 vulnerabilities across every supported branch, and seven of them are rated critical. According to an analysis by Wiz's Merav Bar, those seven offer direct paths to remote code execution without a login, meaning an attacker could run their own commands on a vulnerable server.
The release, published on November 19, lands a month after the PHP2Shell emergency fixes, and it matters for anyone who treated that episode as closed. Wiz warns that the mitigations many teams put in place in October do not protect against all of the new attack paths. Wiz says it has not seen any of the new flaws exploited in the wild, and it found no public reports of exploitation either.
phpAfterShell slips past the October fixes
The headline bug, nicknamed phpAfterShell and tracked as CVE-2026-126714, was reported by the security firm depthfirst. It sits in PHP's default file-based session handler. When PHP records upload progress into a session file, for example during an unauthenticated file upload, the write is not atomic. If the PHP worker is killed partway through, by a memory limit or a timeout, it can leave a malformed session file behind. The next request that calls session_start() deserializes that file, and Wiz says carefully structured contents can turn this into an object deserialization primitive.
That is not automatically game over. Wiz notes that turning the primitive into code execution depends on the application containing a usable gadget chain, which is not guaranteed. But the vulnerable handler is PHP's default, which is what puts this one at the top of the list.
The second notable flaw, CVE-2026-129289, is a PHP-FPM request smuggling issue. Where a front-end server such as Nginx or Apache keeps FastCGI connections to PHP-FPM open, an unauthenticated user can hide a second FastCGI request inside a request body. Because the backend does not discard the leftover bytes, the next request on that connection runs the smuggled instructions, bypassing front-end routing rules and running with the privileges of the FPM worker.
Most of the critical bugs need unusual settings
All seven critical flaws are rated 9.2. Beyond phpAfterShell and the FPM smuggling bug, they are:
- CVE-2026-115560, a session serializer mismatch on a shared session store with upload progress enabled, which PHP first warned about in October before a fix was ready.
- CVE-2026-129481, a use-after-free during interrupted session shutdown, which Wiz describes as an incomplete fix for PHP2Shell's CVE-2026-109619.
- CVE-2026-129182, a fatal error backtrace use-after-free affecting PHP 8.5.
- CVE-2026-129474, a magic method backtrace use-after-free affecting PHP 8.5 when exception arguments are enabled.
- CVE-2026-129496, a timezone cache use-after-free triggered by startup warnings written to a file-based error log on non-thread-safe builds.
The release also fixes four high-severity bugs, led by CVE-2026-129291 (8.8), a use-after-free that lets a local user escalate from an FPM worker to the FPM master process, which often runs as root. The others are an HTTP denial of service (CVE-2026-127960, 8.7), stream wrappers that send data unencrypted when protocol schemes are capitalized (CVE-2026-128064, 8.2), and a Phar signature downgrade (CVE-2026-128090, 7.7). Six medium-severity issues round out the list.
Wiz stresses that most of the critical flaws other than phpAfterShell require non-default configurations, such as runtime-mixed session serializers or zend.exception_ignore_args = 0 on PHP 8.5, so default installations are insulated from many of them. PHP powers approximately 70% of websites with known server-side languages, according to Wiz, so the installed base is large even where the conditions are narrow.
Update to 8.5.13, 8.4.28, 8.3.37 or 8.2.36
The fixed versions are PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36. PHP 8.1 and earlier are end of life and get no fix. After upgrading, rebuild container images and restart the PHP-FPM master or web server so the patched binaries are actually loaded.
If patching has to wait, Wiz recommends three stopgaps:
- Set session.upload_progress.enabled = 0 in php.ini if the application does not need upload progress tracking. This blocks the main path for phpAfterShell.
- Disable FastCGI connection reuse (fastcgi_keep_conn off in Nginx, enablereuse=off in Apache) to close off the FPM smuggling bug.
- On PHP 8.5, keep zend.exception_ignore_args = 1 to mitigate CVE-2026-129474.
Teams that applied the October PHP2Shell updates (our coverage of that release) should not assume they are covered. PHP's session handling code has now produced a second round of critical fixes in four weeks, and the cheapest protection against a third is switching off features the application never uses.
This briefing is provided by IntelFusions for informational and defensive purposes only. It is based on sources assessed to be reliable at the time of writing, and analytic judgments carry the confidence levels indicated. Indicators of compromise are defanged; re-arm them only in controlled environments. IntelFusions is not affiliated with the organizations named and makes no warranty as to completeness or accuracy.