Cybersecurity Research

PHP Patches 17 Flaws, Seven Critical, and October's PHP2Shell Fixes Don't Cover Them All

Wiz Research · 20 Nov 2026
Key Takeaway Update PHP to the latest patched version for your branch and restart the services, then check that risky optional settings are switched off.

On 19 November 2026, the PHP group published security updates for 17 vulnerabilities across all supported branches (PHP 8.2, 8.3, 8.4 and 8.5). Seven are rated Critical (CVSS 9.2) and offer direct routes to unauthenticated remote code execution. Wiz Research says the mitigations put in place during October's PHP2Shell response do not protect against all of these new vectors. No exploitation in the wild has been seen by Wiz or mentioned in public reporting so far.

One flaw, dubbed phpAfterShell (CVE-2026-126714), sits in PHP's default file-based session handler. Session writes during actions such as unauthenticated file uploads are not atomic. If a PHP worker is stopped mid-write, for example by memory limits or timeouts, a malformed session file can be left behind. When a later request calls session_start(), PHP tries to deserialize that file, and carefully crafted contents can trigger an object deserialization problem. This bypasses the earlier PHP2Shell patch parameters.

Another issue affects PHP-FPM. When a web server such as Nginx or Apache keeps FastCGI connections open to the backend, an unauthenticated user can hide a second FastCGI request inside the body of the first. The backend does not discard leftover bytes, so the smuggled request runs on the same connection. That lets it sidestep front-end routing rules and run with the privileges of the FPM worker.

Actual risk depends on configuration. PHP powers roughly 70% of websites with a known server-side language, but exploitation needs specific conditions. phpAfterShell also depends on an exploitable gadget chain in the application's own code, which may not exist. Most of the other critical flaws need non-default settings, such as runtime-mixed session serializers, PHP 8.5 exception arguments being enabled, or startup warnings written to a file-based error log on non-thread-safe builds. Default installations are therefore insulated from many of these vectors.

Why it matters

Teams that treated the October PHP2Shell fixes as the end of this problem now have a gap: those mitigations were parameter-level and do not cover the session and FastCGI paths. Anyone running PHP-FPM behind Nginx or Apache with persistent backend connections, or default file-based sessions with upload progress on, is exposed to unauthenticated attacks. Because exploitation hinges on configuration and application code, you need to inventory your settings rather than assume a default install is safe or unsafe.

What to do

  • Update PHP to 8.5.13, 8.4.28, 8.3.37 or 8.2.36 (or 8.6.0).
  • Rebuild affected container images and restart the PHP-FPM master service or web server process so patched binaries are active.
  • Set session.upload_progress.enabled = 0 in php.ini if upload progress tracking is not needed.
  • Turn off FastCGI connection reuse with fastcgi_keep_conn off in Nginx or enablereuse=off in Apache.
PHP RCE phpAfterShell PHP-FPM Patch Management Vulnerability

Summarised by CISO AI from Wiz Research, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.