Security Intelligence
November 20, 2026 | Security intelligence
Another Shell?! phpAfterShell headlines PHP security release
At a glance:
-
PHP released versions 8.5.13, 8.4.28, 8.3.37, and 8.2.36 on November 19, 2026, fixing 18 vulnerabilities across supported branches, including seven vulnerabilities rated Critical by the PHP project.
-
Researchers published technical details for phpAfterShell, tracked as CVE-2026-126714, showing how corruption of PHP's default session files can lead to object injection and, when combined with a suitable gadget chain or additional vulnerability, potentially code execution.
-
The most relevant environments to review are internet-facing PHP applications using PHP-FPM with FastCGI connection reuse enabled and applications relying on PHP's default file-based session storage. No public reporting indicates active exploitation of the newly disclosed vulnerabilities.
Threat summary
On November 19, 2026, PHP released 8.5.13, 8.4.28, 8.3.37 and 8.2.36, fixing 18 vulnerabilities, seven of them rated critical. The same day, researchers published technical details on one of the flaws, CVE-2026-126714, dubbed phpAfterShell. The technical details demonstrate how a flaw in PHP's default session handling can be used to manipulate user sessions and, when combined with another vulnerability, achieve code execution on the server.
PHP applications use sessions to track authentication state, permissions, shopping carts, and other user data between requests. phpAfterShell affects PHP’s default file-based session storage and is closely related to the PHP2Shell vulnerabilities disclosed in October 2026.
While PHP's October updates limited which objects could be created while PHP recorded upload progress, researchers found that interrupting a session write at a precise moment could corrupt the session file and cause PHP to load attacker-controlled objects later when the application reopened the session. Therefore, servers updated in October remain affected until the November releases are installed.
Researchers demonstrated object injection through a corrupted session file and showed that the same technique can be used to manipulate session data, including values related to authentication and permissions. They also demonstrated a path to code execution by chaining phpAfterShell with a second, undisclosed PHP vulnerability, without relying on a gadget chain in the application.
The advisory states that code execution is also possible where an application contains a suitable deserialization gadget chain. Successful exploitation requires influence over session data and an interruption at a useful point in the write.
The vulnerability affects:
-
PHP 8.2 before 8.2.36
-
PHP 8.3 before 8.3.37
-
PHP 8.4 before 8.4.28
-
PHP 8.5 before 8.5.13
-
Older unpatched builds of end-of-life PHP 7.4, 8.0 and 8.1 are also affected (though the official end-of-life mitigation branches for those versions are not)
Deployments that store sessions in Redis, databases, or other external backends are outside this specific flaw, though each store’s handling of interrupted updates warrants its own review.
The release also addresses CVE-2026-129289, a vulnerability in PHP-FPM, the component that executes PHP code behind web servers such as nginx and Apache. Under specific deployment conditions, a remote, unauthenticated threat actor can inject a forged FastCGI request that is processed directly by PHP-FPM. The advisory states that successful exploitation can result in execution of attacker-controlled PHP code within the PHP-FPM worker process, without user interaction or a non-default PHP configuration.
Exposure to CVE-2026-129289 is limited to environments that reuse FastCGI backend connections and applications that leave request data unread. Affected front ends include:
-
nginx with fastcgi_keep_conn on
-
Apache mod_proxy_fcgi with enablereuse=on
-
HAProxy FastCGI applications that retain backend connections
-
LiteSpeed Server Application Programming Interface (although the confirmed impact in this case is service disruption rather than code execution)
Standard nginx and Apache configurations are not affected.
The remaining vulnerabilities affect session serialization, memory management, date handling, and other PHP runtime components. Several advisories state that these flaws may lead to code execution under specific conditions. No public reporting indicated exploitation of the newly disclosed vulnerabilities as of November 20, 2026.
Analysis
The vulnerabilities affect components that sit directly in the request-processing path of many web applications. Customer portals, e-commerce platforms, content management systems, hosting platforms, and internally developed business applications commonly rely on both PHP-FPM and PHP session management.
CVE-2026-129289 provides one of the more straightforward attack paths addressed in this release. Under the documented conditions, a remote, unauthenticated threat actor can execute PHP code with a single request. The vulnerability affects PHP-FPM deployments that reuse FastCGI backend connections and applications that leave part of the request body unread.
Internet-facing systems that reuse FastCGI backend connections, such as nginx with fastcgi_keep_conn enabled or Apache with enablereuse=on, meet one of the key conditions required for exploitation. Standard nginx and Apache deployments create a new backend connection for each request and are not affected. Reviewing these settings is a quick way to identify systems that may be exposed to CVE-2026-129289. Security researchers have already published tools that can identify potentially vulnerable servers, increasing the likelihood that exposed systems will be discovered quickly.
phpAfterShell affects applications that use PHP’s default file-based session storage. The most important question is where session data is stored. Applications using file-based sessions are affected, while those using Redis, databases, or other external backends are not exposed to this specific flaw.
phpAfterShell affects a broad range of PHP deployments, but exploitation requires multiple conditions, repeated attempts, and precise timing. In contrast, CVE-2026-129289 provides a more direct path to compromise where the required deployment conditions exist, making reviewing and updating internet-facing PHP-FPM deployments more of a priority.
While the exploitation paths differ, the impact of both vulnerabilities ultimately depends on the role of the affected server. PHP application servers often have access to databases, cloud resources, internal APIs, and authentication systems. Where code execution is achieved, those connections can provide a path to sensitive data and additional systems beyond the initial application. Applications that support customer portals, payment processing, or administrative functions face the greatest operational risk.
Mitigations
Apply the November PHP updates and restart PHP-FPM workers after deployment. The fixes address all vulnerabilities included in the release, including the session-handling flaw underlying phpAfterShell. The updated code clears session files before writing and stops processing if that operation fails, preventing the file-corruption condition used in the research. Restarting services is important because existing PHP workers continue using the old code until they are recycled.
Fixed releases are available from PHP, and the official Docker php images were updated shortly after disclosure. Linux distributions are releasing updates on their own schedules, and many vendors backport security fixes without changing the reported PHP version number. Vendor security advisories are therefore a more reliable indicator of patch status than the PHP version string alone.
Internet-facing PHP applications that reuse FastCGI backend connections deserve the closest attention. Identifying where connection reuse is enabled helps narrow the list of potentially exposed servers. Where updates cannot be applied immediately, disabling connection reuse removes the documented attack path.
Applications that rely on PHP’s default file-based session storage warrant separate review. Moving sessions to a backend that replaces records atomically also avoids the specific file-handling issue exploited by phpAfterShell, although updating remains the recommended fix.
The published research used PHP’s upload progress feature to trigger session writes before application code executed. Where upload progress is not required, setting session.upload_progress.enabled=0 in php.ini or the PHP-FPM pool configuration and restarting PHP workers removes the attack path demonstrated by the researchers and can reduce exposure while updates are being scheduled. The November releases disable the feature by default, although existing configuration files, distribution packages, and management platforms may continue to enable it. Systems that retained the October PHP2Shell mitigation still require the November updates. Applications that write untrusted data into sessions through other mechanisms still require the update.
Monitor PHP infrastructure for repeated worker crashes, unusual session-related errors, and PHP-FPM processes spawning shells or unexpected child processes. On internet-facing systems, these indicators may provide some of the earliest signs of testing or exploitation activity targeting the newly disclosed vulnerabilities.
Stay on top of emerging threats like this.
Sign up to receive a weekly roundup of our security intelligence feed. You'll be the first to know of emerging attack vectors, threats, and vulnerabilities.

