November 20, 2026

Critical "php2shell" Vulnerabilities Trigger Emergency PHP Security Updates to Prevent Remote Execution

The global PHP security team has issued an emergency set of updates to address two critical vulnerabilities that could allow unauthenticated attackers to execute arbitrary code on web servers. Released on October 21, 2026, the patches arrive as a direct response to a high-pressure situation involving a public leak of vulnerability details just one day before the scheduled maintenance window. The flaws, identified as CVE-2026-109618 and CVE-2026-109619, have both been assigned a high-severity score of 9.2 under the CVSS v4.0 framework, signaling a significant risk to the vast number of websites and applications powered by the PHP language.

The security release covers several active branches of the PHP engine, specifically versions 8.5.12, 8.4.27, 8.3.36, and 8.2.35. Because these vulnerabilities allow for remote code execution (RCE) without requiring any prior authentication, they represent the highest tier of threat for server administrators. The rapid response from the PHP core developers underscores the severity of the situation, particularly after details of the flaws began circulating online under the moniker "php2shell."

A High-Stakes Timeline and the "php2shell" Leak

The road to these emergency patches began on October 20, 2026, when the official PHP project announced an upcoming critical security release scheduled for the following day at 14:00 UTC. While such announcements are standard practice to allow administrators to prepare for downtime, the situation escalated rapidly when technical details of the vulnerabilities were leaked ahead of schedule. Security research firms, including Sansec and Huntress, quickly identified the circulating information and published warnings to the broader community.

The leak created a dangerous window of opportunity for threat actors to develop exploits before official fixes were widely available. Recognizing this, the PHP security team and the PHP CVE Numbering Authority (CNA) accelerated their processes. The official GitHub Security Advisories were published early on October 21, followed immediately by the formal CVE records. By the time the official binaries and source code updates were released, the community was already on high alert. While Linux distributions and Long-Term Support (LTS) vendors had received the patches in advance through private security channels, the public leak forced a slightly earlier-than-planned deployment for the general public.

Understanding CVE-2026-109618: Memory Corruption via Out-of-Memory Errors

The first of the two critical flaws, CVE-2026-109618, involves a fundamental issue with how PHP handles memory exhaustion. In the C programming language, which serves as the foundation for the PHP interpreter, developers often use a function called longjmp() to handle exceptional circumstances. When PHP runs out of memory (OOM), it uses this mechanism to immediately exit the current execution context and abort the web request.

However, technical advisories reveal that in certain specific contexts, request-related memory can become reachable by the system before it has been fully or properly initialized. If a memory allocation fails at this precise moment, the PHP engine does not properly account for the early exit triggered by the OOM condition. This leaves the request memory in an invalid, "half-initialized" state. Crucially, the failed allocation that triggers the crash does not even need to be directly related to the memory that is left corrupted.

The danger arises during the request shutdown procedure. As PHP attempts to clean up and close the request, it may read from or branch its logic based on this invalid data. An attacker can exploit this by carefully crafting a request that pushes the server into an OOM state while remaining within the apparent limits set by the server’s configuration. This is often achieved through multipart parsing paths, which are commonly used for file uploads and complex form data. By manipulating how the server processes these large or complex inputs, an attacker can induce the specific memory state required to trigger code execution.