Home / Bug Bounty & Vulnerabilities / PHP Security Update Addresses Seven Critical Remote Code Execution Vulnerabilities

PHP Security Update Addresses Seven Critical Remote Code Execution Vulnerabilities

The PHP development team has officially rolled out a comprehensive set of security patches as part of its regular four-week maintenance cycle, addressing a significant array of vulnerabilities that could allow for remote code execution (RCE). The latest release, which includes updates across multiple active branches of the language, focuses heavily on neutralizing seven critical-severity flaws that have been identified within the core engine and its various modules. These updates are essential for administrators and developers, as the nature of the vulnerabilities—ranging from session management errors to request handling flaws—presents a broad attack surface for potential adversaries.

The flagship updates, delivered through PHP 8.6.0 and PHP 8.5.13, provide fixes for these seven critical bugs alongside ten additional vulnerabilities categorized as high or medium severity. Furthermore, the security team has extended the reach of these patches to include older, supported versions of the language, with PHP 8.4.28, PHP 8.3.37, and PHP 8.2.36 also receiving the necessary security hardening.

Addressing Complex Session and Memory Vulnerabilities

Among the most pressing issues addressed is CVE-2026-115560, a critical vulnerability that was publicly disclosed last month. The flaw gained significant attention due to its emergence just two days after the patches for the infamous "PHP2Shell" vulnerabilities were released. This vulnerability resides within the session upload progress feature, a component that, if manipulated, allows an attacker to manipulate how session data is serialized and stored.

The core of the issue lies in a decoder mismatch. When an application writes attacker-provided data using one session serialization format but subsequently reads it using a different, incompatible format, the integrity of the data is compromised. According to the official PHP advisory, a mismatched decoder can interpret parts of a session key as serialized object data. If an application possesses a suitable object gadget chain—a sequence of pre-existing code that can be triggered to perform unintended actions—an attacker can leverage this mismatch to execute code with the full privileges of the PHP worker process.

The maintenance release also tackles CVE-2026-129481, a use-after-free vulnerability that represents an incomplete remediation of a previously identified flaw. This particular vulnerability occurs when an application’s session shutdown process is interrupted. It is directly linked to CVE-2026-109619, one of the two "PHP2Shell" vulnerabilities patched in October, which has seen widespread exploitation in the wild. PHP developers noted that while an attacker who successfully triggers a session cleanup failure in this manner could potentially cause memory corruption or crash a reused PHP worker, the possibility of RCE through this specific field has not yet been demonstrated in a controlled environment. Notably, the PHP 8.2 branch remains unaffected by this specific use-after-free issue.

A related concern is addressed in CVE-2026-129182, which covers additional exploitation scenarios for the same underlying RCE vector via stale global state, known as CVE-2026-109619. Much like the previously mentioned use-after-free, while the risk profile is high due to the nature of the vulnerability, the PHP team has clarified that remote code execution via these specific scenarios remains unproven at this time.

Critical Weaknesses in Memory Management and Request Handling

The security update also targets vulnerabilities that impact the newer iterations of the language. Specifically, CVE-2026-129474 is a use-after-free vulnerability that affects PHP 8.5 and later. This flaw is particularly concerning as it could theoretically allow an unauthenticated attacker to induce a fatal error, which, under the right conditions, could culminate in remote code execution. The PHP advisory explains that the exploitability of this vulnerability is highly dependent on the target application. It requires the attacker to exert significant control over request data to influence memory allocation patterns, while also requiring the application to have a reachable magic method call and to trigger a fatal error at the precise moment required to hijack the process flow.

Another critical vulnerability, CVE-2026-126714, involves the manipulation of session files. If an attacker can influence the contents of a session and then successfully interrupt the write operation of serialized data to a session file, they can trigger the deserialization of their own controlled content the next time that session is opened. If the underlying application includes an appropriate object gadget chain, this can lead to remote code execution, highlighting the danger of trusting data retrieved from session files.

The patch list also includes a fix for CVE-2026-129289, a request smuggling vulnerability within PHP-FPM (FastCGI Process Manager). This flaw stems from a "lazy" approach to reading request-body streams. When PHP treats a request body as handled during the request shutdown phase, it can fail to perform the necessary cleanup, skipping the step that discards unread input. Consequently, PHP may retain unread bytes from an HTTP request body and fail to clear them before reusing a persistent PHP-FPM or LSAPI connection. In a PHP-FPM environment, this enables an unauthenticated attacker to craft bytes that form a separate, malicious FastCGI request. By bypassing front-end routing, the attacker can execute arbitrary PHP code with the privileges of the worker process, making this a high-priority fix for any infrastructure relying on PHP-FPM.

Finally, the seventh critical-severity flaw, CVE-2026-129496, involves the timezone cache. The vulnerability exists because PHP may retain a reference to the timezone cache when writing a diagnostic message to an error log file during the startup of a process. A subsequent diagnostic operation might then attempt to access this already freed cache before the system has a chance to reset it. On affected configurations, this allows a remote attacker to trigger memory corruption, force a worker to crash, and potentially execute arbitrary code using the permissions of the PHP worker.

Ensuring System Integrity

The rapid identification and patching of these vulnerabilities underscore the ongoing challenge of securing a core component of the web ecosystem. The "PHP2Shell" series of vulnerabilities, in particular, has served as a catalyst for deeper security reviews, leading to the discovery of the secondary and incomplete fixes released today. For system administrators, the recommendation is clear: the critical nature of these seven vulnerabilities necessitates an immediate review of current PHP deployments and an update to the latest patched versions.

Administrators are encouraged to consult the official PHP news archive for detailed guidance on these updates and to ensure that their production environments are running on supported, patched versions of the language. The complexity of these flaws, particularly those involving request smuggling and session serialization, serves as a reminder of the importance of maintaining a robust security posture and keeping software dependencies updated to defend against evolving threat landscapes. As exploitation techniques become more sophisticated, the collaboration between the core PHP team and the security research community remains a vital defense mechanism for the millions of applications that rely on the language to power the modern internet.

Tagged:

Leave a Reply

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