November 17, 2026

PHP Project Issues Warning Over New Session Vulnerability as PHP2Shell Exploit Attempts Surge Globally

The PHP development team has issued a formal warning regarding a newly discovered vulnerability that could potentially allow an attacker to execute arbitrary code on a web server. This disclosure, made on October 23, 2026, comes at a particularly sensitive time for the web development community, arriving just forty-eight hours after the project released a series of emergency patches to address two critical flaws collectively known as PHP2Shell. While the newly identified issue is currently deemed a lower risk than its predecessors, its discovery underscores the ongoing security challenges facing the most widely used server-side scripting language on the internet.

The latest vulnerability has been assigned the identifier CVE-2026-115560. Unlike the PHP2Shell flaws, which triggered an immediate emergency response, the PHP project is categorizing this new issue as a secondary concern that primarily affects web applications operating under specific and somewhat unconventional configurations. Because the risk is perceived as unlikely to manifest in standard deployments, the project has opted not to issue an immediate emergency software update. Instead, the security team is advising administrators to implement a manual configuration change to mitigate the risk until a formal fix can be integrated into the next scheduled routine maintenance release.

In an informational advisory published late Friday, the PHP project clarified that CVE-2026-115560 is a distinct issue from the vulnerabilities addressed on October 21. Those earlier flaws, tracked as CVE-2026-109618 and CVE-2026-109619, were of the highest severity, as they allowed unauthenticated attackers to achieve remote code execution on vulnerable servers. Those critical issues were patched in the emergency releases of PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35. The security team emphasized that while users should prioritize upgrading to those versions to protect against PHP2Shell, those specific updates do not contain a fix for the newly disclosed CVE-2026-115560.

The technical nature of CVE-2026-115560 involves the way PHP handles session data and serialization. For a server to be at risk, an application must meet a very narrow set of criteria in its operational environment. Specifically, the vulnerability can only be triggered if a web application is configured to use either the "php_binary" or "php_serialize" options for the session.serialize_handler setting within its main configuration files. Furthermore, the application must then dynamically change this setting to the standard "php" handler during execution by calling the ini_set() function. Critically, this change must occur before the session_start() function is invoked.

PHP Warns of Another Unpatched RCE Two Days After Emergency PHP2Shell Patches

In addition to these specific configuration requirements, the "session upload progress" feature must remain active for the vulnerability to be exploitable. This feature, which is enabled by default in many PHP installations, is designed to allow developers to track the progress of file uploads in real-time. The PHP project noted that applications that do not dynamically switch their serialization handlers while running are not exposed to this specific threat, even if the upload progress feature remains active. The advisory suggests that the combination of these specific conditions is rare in professional production environments, leading to the decision to handle the fix through the standard release cycle.