20 Nov 2026, Fri

PHP Issues Massive Security Update Addressing Seven Critical Remote Code Execution Vulnerabilities

The PHP development team has officially rolled out a comprehensive set of security patches as part of its recurring four-week maintenance cycle. This latest release is particularly significant, as it addresses seven critical-severity vulnerabilities capable of facilitating remote code execution (RCE). These flaws, which impact various versions of the widely used server-side scripting language, represent a major effort by maintainers to harden the PHP ecosystem against increasingly sophisticated attack vectors.

The urgency of this release follows a period of heightened scrutiny surrounding PHP’s security posture, specifically regarding how the language handles session data and process memory. Among the most notable entries in this update is CVE-2026-115560, a vulnerability that was disclosed publicly last month, mere days after the initial patches for the "PHP2Shell" exploit were deployed.

CVE-2026-115560 resides within PHP’s session upload progress feature. According to the official advisory, the flaw can be exploited by an attacker to write data using one session serialization format while subsequently reading it through a different, mismatched decoder. This discrepancy is the core of the danger: a mismatched decoder can inadvertently interpret portions of a session key as serialized object data. If an application possesses a suitable "object gadget chain"—a series of existing code segments that an attacker can link together—it may be possible to execute arbitrary code under the privileges of the underlying PHP worker process.

The scope of this update also sheds light on the lingering complexity of previously identified security gaps. For instance, CVE-2026-129481, another use-after-free vulnerability, has been identified as an incomplete remediation of CVE-2026-109619. The latter was one of the two primary flaws associated with the "PHP2Shell" incident discovered in October, which has since seen widespread exploitation in the wild.

In the case of CVE-2026-129481, the vulnerability is triggered when an application’s session shutdown process is interrupted. PHP maintainers explain that an attacker capable of forcing this specific failure can induce memory corruption or cause a PHP worker to crash. While the potential for remote code execution via this specific vulnerability remains theoretical and has not been fully demonstrated in a live exploit scenario, the memory corruption risk alone presents a significant stability and security threat. Notably, the PHP 8.2 branch is reported to be unaffected by this particular flaw, offering some relief to organizations still utilizing that version.

Complementing this, CVE-2026-129182 introduces further complexities regarding the exploitation of CVE-2026-109619. This vulnerability pertains to RCE via stale global state, providing additional potential attack paths that researchers have identified. Much like the previous use-after-free, while RCE through these specific scenarios has not been definitively proven, the existence of such weaknesses highlights the necessity of these broad-spectrum updates to prevent potential future exploitation.

The update also addresses vulnerabilities specifically targeting newer iterations of the language. CVE-2026-129474, which impacts PHP 8.5 and later versions, is a use-after-free vulnerability that could potentially allow an unauthenticated attacker to trigger a fatal error and achieve RCE. However, the conditions for successful exploitation are stringent; the attack requires the adversary to have substantial control over request data to influence memory allocation, a reachable magic method call, and the ability to trigger a fatal error at a precise moment in the execution flow.

Another critical concern addressed in this cycle is CVE-2026-126714, which involves the manipulation of session contents. Attackers who can influence session data and simultaneously interrupt the write process of serialized data to a session file can trigger the deserialization of attacker-controlled content when the session is accessed again. This mechanism, if executed correctly, allows for RCE via an application-specific object gadget chain.

Beyond session-based vulnerabilities, the update tackles a sophisticated request smuggling issue identified as CVE-2026-129289. This flaw is rooted in how PHP-FPM processes request-body streams. Because PHP reads these streams lazily, it can mistakenly treat a request body as handled during the request shutdown process, thereby skipping the standard cleanup procedures that are designed to discard unread input.

"PHP can fail to discard unread bytes from an HTTP request body before reusing a persistent PHP-FPM or LSAPI connection," the PHP security team explained in their advisory. In practical terms, this means that in an environment using PHP-FPM, an unauthenticated attacker can manipulate these unread bytes to form an entirely separate FastCGI request. This maneuver allows the attacker to bypass front-end routing configurations and execute arbitrary PHP code with the privileges of the worker process, effectively circumventing standard security boundaries.

The seventh critical-severity flaw, CVE-2026-129496, is located within the timezone cache. The vulnerability occurs when PHP retains a reference to the cache while simultaneously writing a diagnostic message to an error log file during the process startup. If a subsequent diagnostic is triggered, it can access the already freed cache memory before it is properly reset. This race condition can lead to memory corruption, worker crashes, and, in certain configurations, the potential for remote code execution under the privileges of the PHP worker.

The magnitude of this update is reflected in the version releases themselves. PHP 8.6.0 and PHP 8.5.13 have been issued specifically to incorporate these critical fixes, alongside a suite of 10 additional high and medium-severity patches. Furthermore, the development team has ensured that these essential security updates are backported to previous versions, with patches now included in PHP 8.4.28, PHP 8.3.37, and PHP 8.2.36.

This multi-version approach is a testament to the continued prevalence of legacy PHP deployments in the global web infrastructure. By extending these critical protections to the 8.2, 8.3, and 8.4 branches, the PHP maintainers are providing a necessary buffer for administrators who may not be able to immediately migrate to the latest versions of the language.

The sheer volume of critical vulnerabilities addressed in this single update cycle underscores the ongoing challenge of maintaining the security of a language that powers a vast majority of the web. The "gadget chain" risks, use-after-free vulnerabilities, and request smuggling issues identified here serve as a reminder that the PHP core is subject to complex memory and state management problems that require constant vigilance.

For developers and system administrators, the recommendation is clear: update to the latest patched versions immediately. The complexity of these vulnerabilities, particularly those that bypass front-end routing or exploit serialized session data, makes them dangerous for any application that handles untrusted user input. For more detailed information regarding the specific technical patches and to download the latest releases, users are encouraged to consult the official PHP news archive.

As the industry grapples with these findings, the security community continues to monitor for signs of active exploitation of these newly identified vectors. Given that many of these vulnerabilities are related to previously disclosed issues—such as the PHP2Shell flaws—the threat landscape remains dynamic. Security professionals should prioritize reviewing their server configurations, particularly regarding PHP-FPM and session handling, to ensure that they are not unnecessarily exposed to these critical risks while the update process is underway.

By Sagoh

Leave a Reply

Your email address will not be published. Required fields are marked *