According to technical details provided in the advisory, an application is only exposed to CVE-2026-115560 if it uses a front end that enables persistent backend connections and an application path that opens php://input without reading it fully. Relevant configurations include nginx with fastcgi_keep_conn enabled, Apache mod_proxy_fcgi with enablereuse=on, HAProxy FastCGI applications that retain backend connections, and LSAPI. Standard nginx and Apache configurations that close the FastCGI connection after each request are not affected by the demonstrated attack. Until the November release, users are urged to set session.upload_progress.enabled=0 and restart the PHP worker to mitigate the risk.
The November release fixes specific version thresholds: PHP 8.2 before 8.2.36, 8.3 before 8.3.37, 8.4 before 8.4.28, and 8.5 before 8.5.13. It is important to note that the emergency releases issued on October 21, 2026, which fixed the critical “PHP2Shell” vulnerabilities (CVE-2026-109618 and CVE-2026-109619), do not include a fix for CVE-2026-115560. Therefore, systems that have already been patched for the October flaws remain exposed to this new issue if they meet the specific configuration prerequisites.

This development follows a month of heightened security activity for the language. On October 21, PHP released emergency fixes for PHP2Shell, a pair of critical vulnerabilities that enabled unauthenticated RCE via specially crafted HTTP requests. Hunt.io reported that it identified 616 PHP2Shell-related files, including exploit kits and proof-of-concepts, across multiple hosts. CrowdStrike analysts noted that while exploit developers are unlikely to create a single universal exploit for all deployments, active exploitation has been observed targeting Palo Alto Networks management interfaces and Check Point Security Gateways.
In October, PHP also patched a critical out-of-bounds write vulnerability in the Brotli decoder library (CVE-2026-111497), known as Node2Shell or Broccoli2Shell, which could result in arbitrary code execution. The European Union’s cybersecurity agency, ENISA, along with the European Commission and Europol, issued a joint statement on October 21 advising organizations to take immediate action to address the PHP2Shell vulnerabilities. The agencies highlighted that many commercial and open-source products rely on PHP in the background, meaning some systems may be affected even if they do not appear to use PHP directly.

Users are advised to upgrade to the fixed versions as soon as they become available on November 19. For organizations that cannot apply the update immediately, the maintainers recommend isolating exposed applications from public networks where feasible. Security teams are encouraged to monitor for unusual multipart uploads, unexpected changes to session serialization behavior, and suspicious child processes spawned by PHP or web-server workers to detect potential exploitation attempts.



