On November 19, 2026, the PHP group published security updates addressing 17 vulnerabilities across all actively supported branches (PHP 8.2, 8.3, 8.4, and 8.5). Seven of these flaws are rated Critical (CVSS 9.2) and present direct pathways to unauthenticated remote code execution (RCE). Security teams are advised to identify and patch exposed PHP deployments, as earlier mitigation efforts implemented during October's response to "PHP2Shell" do not provide protection against all of these new exploit vectors. As of yet, no exploitation in the wild has been observed by Wiz or mentioned in public reporting.
What are these vulnerabilities?
phpAfterShell: File-Based Session Handling (CVE-2026-126714)
Reported by depthfirst, this vulnerability exists in PHP’s default file-based session handler (session.save_handler = files). When PHP writes session update progress (such as during unauthenticated file uploads), the file-write process is not atomic. If a PHP worker process is abruptly stopped during this write, due to memory limits or timeout settings, it can leave behind a partially written, malformed session file.
When a subsequent request calls session_start(), PHP attempts to deserialize this file. If the file's contents are carefully structured, this deserialization process can be manipulated to trigger an object deserialization primitive. This behavior bypasses the initial parameters set during October's PHP2Shell patches, making a fresh update necessary to secure file-based session pipelines.
PHP-FPM Request Smuggling (CVE-2026-129289)
This issue centers on how PHP-FPM processes unread request-body bytes before reusing a persistent connection. In environments where the front-end web server (such as Nginx or Apache) is configured to keep FastCGI connections open to the FPM backend, an unauthenticated user can structure a request to append a secondary, hidden FastCGI request within the request body.
Because the backend does not discard the leftover bytes, the subsequent request handled over that same connection executes the smuggled instructions. This allows a request to bypass front-end routing rules and execute with the privileges of the active FPM worker.
Wiz Research data: what’s the risk to cloud environments?
The overall risk depends largely on your environment's configuration. PHP remains widely used, powering approximately 70% of websites with known server-side languages. While the technical severity of these bugs is high, executing them successfully requires specific conditions. For instance, phpAfterShell (CVE-2026-126714) requires file-based sessions (the PHP default) and relies on finding an exploitable gadget chain in the application's code (which isn’t guaranteed to exist in every application) to achieve code execution.
Importantly, the vast majority of the other critical vulnerabilities in this release require non-default configurations or uncommon setups, such as enabling runtime-mixed session serializers, enabling PHP 8.5 exception arguments (zend.exception_ignore_args = 0), or writing startup warnings to a file-based error log on non-thread-safe builds. This ultimately means that default installations are naturally insulated from many of these vectors.
Which products are affected?
Which actions should security teams take?
A. Plan a Routine Upgrade
- Plan to update your PHP installations to 8.5.13, 8.4.28, 8.3.37, or 8.2.36 (or 8.6.0).
Plan to update your PHP installations 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 to ensure the newly patched binaries are active in memory.
Rebuild affected container images and restart the PHP-FPM master service or web server process to ensure the newly patched binaries are active in memory.
B. Temporary Configuration Adjustments (If patching is delayed)
- Disable Session Upload Progress: If your application does not require tracking upload progress, disabling this feature in php.ini mitigates the primary attack path for phpAfterShell (CVE-2026-126714) in particular: session.upload_progress.enabled = 0
Disable Session Upload Progress: If your application does not require tracking upload progress, disabling this feature in php.ini mitigates the primary attack path for phpAfterShell (CVE-2026-126714) in particular: session.upload_progress.enabled = 0
- Disable FastCGI Connection Reuse: Block the PHP-FPM request smuggling vector by configuring Nginx (fastcgi_keep_conn off) or Apache (enablereuse=off) to close backend connections immediately.
Disable FastCGI Connection Reuse: Block the PHP-FPM request smuggling vector by configuring Nginx (fastcgi_keep_conn off) or Apache (enablereuse=off) to close backend connections immediately.
- Configure Exception Arguments (PHP 8.5): Ensure exception arguments are omitted to mitigate CVE-2026-129474: zend.exception_ignore_args = 1
Configure Exception Arguments (PHP 8.5): Ensure exception arguments are omitted to mitigate CVE-2026-129474: zend.exception_ignore_args = 1
Wiz customers can use the pre-built query and advisory in the Wiz Threat Center to search for vulnerable instances in their environment.
References
PHP changelog
DepthFirst phpAfterShell blogpost
Precursor Security blogpost












