PHP2Shell: A third vulnerability affects already patched versions

Just five days after the release of patches for PHP2Shell, a new update proves insufficient to mitigate risk. A third vulnerability exposes updated versions and can be mitigated through configuration changes, while CrowdSec’s measures still afford IT departments a window to address the issue, with no widespread exploitation currently observed.

On October 23, the PHP project issued a notice regarding a new vulnerability, CVE-2026-115560, which permits remote code execution through the session upload tracking function. This flaw affects versions 8.5.12, 8.4.27, 8.3.36, and 8.2.35, released on October 21 to address PHP2Shell. PHP2Shell refers to vulnerabilities CVE-2026-109618 and CVE-2026-109619, rated 9.2 out of 10, which allow code execution on a server without authentication. The first exploit involves data corruption following memory exhaustion, while the second takes advantage of a state left by one request and reused by the next on the same process. PHP maintainers consider installations using mod_php to be the most vulnerable and view the update as the only complete fix available. Linux distributions and long-term support providers had received patches in advance. The French government’s CERT-FR, which monitors, alerts, and responds to cyberattacks, added the notice on October 26 to its alert regarding PHP and urges immediate application of the patches due to PHP’s integration in numerous products.

The PHP maintainers deem exploitation unlikely, as it requires an application to alter the session serialization handler at runtime while keeping the upload tracking active. As a result, PHP has postponed the fix to its next update cycle without specifying a date, promising a comprehensive advisory alongside this fix. Thus, the risk remains concentrated within application code, known only to the teams managing it.

Configuration: The Only Protection Until the Next Cycle

In the meantime, protection can be achieved through the php.ini file or by configuring the FPM process handler, specifically by setting the directive session.upload_progress.enabled=0 and then restarting all PHP processes. Modifications made through the application, such as using ini_set() or a user.ini file, will not take effect. Cloudflare’s application firewall covers the vulnerability with an existing rule, provided that the site retains the default field name for upload tracking. Sites that have altered this setting via session.upload_progress.name will rely solely on their own configuration.

This restart is also necessary for the October 21 patches. PHP cautions that a patched binary leaves processes still running the previous version exposed. On Windows, PHP released new builds on October 26 that incorporate a corrected Brotli compression library (CVE-2026-111497), accessible through the cURL extension when automatic decompression of responses is enabled.

Five Days of Attempts Without Mass Exploitation

CrowdSec, a French collaborative security provider that markets an application firewall, released network measures on October 26. From October 21 to 25, 1,730 sensors from 771 organizations across 73 countries blocked 10,073 requests originating from 1,187 IP addresses. The first block occurred on October 21 at 10:37 UTC, nearly three hours before the vulnerabilities were disclosed and before the PHP patch was released at 14:00 UTC. Seventeen addresses were already blocked at that time. Cloudflare enacted its rules at 03:02 UTC the same day and noted attackers modifying their requests to evade detection. New sources dropped to around 130 per day from Friday to Sunday, down from 612 on Thursday, with no publicly confirmed compromises reported by the editor.

Attackers appear to be testing vulnerabilities rather than exploiting them. Half of the sources targeted sent just a single request over the five days, and 82% sent three or fewer. Only 24 sources insisted on a particular sensor more than ten times. Established techniques typically require multiple requests against the same server. The initial scans primarily targeted the simplest vector: session uploads, and the first tools claiming to exploit PHP2Shell emerged on the first night. By Thursday, a cluster of attackers, 72% of which had previously targeted React2Shell—a vulnerability in the React library exploited in 2025—switched their focus in a single morning, then disappeared from the sensor network. The 446 addresses that appeared subsequently, with 30% being new to the network, were associated with background scanning aimed at any known vulnerabilities. CERT-FR reported attempts against specific PHP deployments.

A Window for Correction This Week

CrowdSec attributes the current calm to the absence of a working exploit code for default installations. The editor would change its assessment if such code were released, if new sources exceeded 130 per day, if repeated attempts intensified, or if the memory vulnerability, currently targeted by 147 sources compared to 429 for the sessions, caught up. CrowdSec notes that the number of sources targeting React2Shell escalated 27 times between the second and sixth day of its exposure.

This window is beneficial for IT departments, which know where PHP runs across their environments, including business applications and hosted sites. This timeframe allows for the implementation of corrective versions, the disabling of upload tracking, and the restarting of processes, as well as the decision on which servers to remove from the network if any warning signs emerge. For servers that cannot be updated immediately, PHP lists partial measures, including locking memory limits against modifications by applications and reducing the maximum upload size to 8 or 32 megabytes, albeit none of these measures render an installation completely safe. Notably, versions 8.1 and earlier will no longer receive updates from the project, although minimal backports have been published for versions 7.4, 8.0, and 8.1.

Scroll to Top