PHP Issues Emergency Security Updates Across All Supported Branches
The PHP development team has released a coordinated set of security updates addressing seven critical-severity remote code execution (RCE) vulnerabilities, alongside ten high and medium-severity flaws. The patches shipped on Thursday as part of the project’s regular four-week cadence and apply to PHP 8.6.0, PHP 8.5.13, PHP 8.4.28, PHP 8.3.37, and PHP 8.2.36. Administrators running any supported version should prioritize upgrading immediately, as several of the resolved issues relate to previously exploited weaknesses.
Session Upload Progress Flaw Allows Deserialization Attack
The first critical vulnerability, CVE-2026-115560, was publicly disclosed last month, two days after the PHP2Shell patches landed in October. The bug resides in the session upload progress feature and stems from a mismatched decoder that can interpret part of a session key as serialized object data. According to PHP’s advisory, an application with a suitable object gadget chain can then execute code with the privileges of the PHP worker. This flaw enables an attacker to write attacker-controlled data using one session serialization format and read it back using another, triggering unintended deserialization.
Use-After-Free Vulnerabilities Linked to PHP2Shell Exploits
Three of the seven critical RCEs are use-after-free weaknesses connected to CVE-2026-109619, one of the two PHP2Shell vulnerabilities patched in October and now widely exploited in the wild.
CVE-2026-129481: Incomplete Fix for Previously Exploited Flaw
CVE-2026-129481 is described as a use-after-free occurring after a session shutdown has been interrupted. PHP characterizes it as an incomplete fix for CVE-2026-109619. The advisory notes that an attacker who can cause an application’s session cleanup to fail may corrupt memory or crash a reused PHP worker. While the use-after-free could potentially lead to remote code execution, PHP states that code execution through this specific field has not been demonstrated. Notably, PHP 8.2 is not affected by this vulnerability.
CVE-2026-129182: Additional Exploitation Scenarios for Stale Global State
CVE-2026-129182 covers additional exploitation scenarios for CVE-2026-109619, specifically an RCE via stale global state. As with the prior issue, PHP confirms that RCE via these scenarios has not been demonstrated, though the underlying memory corruption risk remains.
Unauthenticated RCE in PHP 8.5+ Via Use-After-Free
CVE-2026-129474 impacts PHP 8.5 and later versions. This use-after-free weakness could allow an unauthenticated attacker to cause a fatal error and achieve remote code execution. PHP explains that exploitation depends on the application and requires control over enough request data to influence memory allocation, a reachable magic method call, and a fatal error at the relevant point. This makes the vulnerability conditional but high-impact where prerequisites are met.
Session Deserialization via Interrupted Write Operation
Tracked as CVE-2026-126714, this flaw allows attackers able to influence session contents and interrupt the write of serialized data to a session file. When the session is next opened, the deserialization of attacker-controlled content may occur, potentially leading to RCE via a suitable object gadget chain in the application. The vulnerability highlights risks in session persistence mechanisms when write operations are disrupted.
PHP-FPM Request Smuggling Enables Code Execution
CVE-2026-129289 is a PHP-FPM request smuggling issue caused by PHP reading a request-body stream lazily. The engine treats a request body as handled during request shutdown and skips the normal cleanup that discards unread input. Consequently, PHP can fail to discard unread bytes from an HTTP request body before reusing a persistent PHP-FPM or LSAPI connection. In PHP-FPM, an unauthenticated attacker can make those bytes form a separate FastCGI request, bypass front-end routing, and execute attacker-controlled PHP code with the privileges of the worker. This represents a significant risk for shared hosting and multi-tenant environments using PHP-FPM.
Timezone Cache Corruption During Startup Diagnostics
The seventh critical vulnerability, CVE-2026-129496, resides in the timezone cache. PHP can retain a reference to the cache when writing a diagnostic to a PHP error log file during process startup. A later diagnostic can then access the freed cache before it is reset. On affected configurations, a remote attacker can trigger memory corruption, cause a worker to crash, and potentially execute arbitrary code with the privileges of the PHP worker. This flaw underscores the danger of use-after-free conditions in early initialization paths.
Upgrade Guidance and Affected Versions
All seven critical vulnerabilities are resolved in the following releases:
- PHP 8.6.0 (new feature release with security fixes)
- PHP 8.5.13
- PHP 8.4.28
- PHP 8.3.37
- PHP 8.2.36
Each release also includes patches for ten high and medium-severity issues. Organizations should consult the PHP news archive for complete changelogs and upgrade instructions. Given the active exploitation of related PHP2Shell flaws, immediate deployment is strongly recommended for all internet-facing PHP deployments.
Source: SecurityWeek