Image: securityweek.com · rights & removal
PHP Patches Seven Critical RCE Vulnerabilities
Reporting by SecurityWeekRead the original at securityweek.com
Executive Summary
Facts Only
* PHP rolled out security patches on Thursday according to its four-week update schedule.
* Patches included fixes for seven critical-severity remote code execution (RCE) vulnerabilities.
* CVE-2026-115560 resides in the session upload progress feature and involves a mismatched decoder potentially executing code with PHP worker privileges.
* CVE-2026-129481 is a use-after-free flaw following an interrupted session shutdown, which may lead to memory corruption or crashes.
* CVE-2026-129182 covers additional exploitation scenarios for CVE-2026-109619 (RCE via stale global state).
* CVE-2026-129474, impacting PHP 8.5 and later, is a use-after-free weakness that could allow an unauthenticated attacker to cause a fatal error and achieve RCE depending on application context.
* CVE-2026-126714 is a flaw that could lead to RCE via an object gadget chain if session contents and serialized data writes are manipulated during session interruption.
* CVE-2026-129289 addresses a PHP-FPM request smuggling issue, allowing unauthenticated attackers to execute code by manipulating the request body stream during connection shutdown.
* CVE-2026-129496 is in the timezone cache and can lead to memory corruption, worker crashes, or arbitrary code execution on affected configurations.
* PHP 8.6.0 and PHP 8.5.13 were rolled out with fixes for critical bugs and 10 high/medium severity flaws.
Full Take
The sequence of disclosures reveals a pattern where updates address deeply technical memory management issues, specifically use-after-free conditions and state handling (e.g., session cleanup, global state, cache). The fact that several RCE vulnerabilities are framed around object gadget chains or control over memory allocation suggests that the foundational risk lies in how the PHP runtime manages complex data structures during state transitions. The vulnerability CVE-2026-129496, which allows code execution via a timezone cache reference, implies that seemingly innocuous diagnostic operations can introduce exploitable timing or state manipulation into the worker environment. This points to an underlying systemic challenge: ensuring deterministic and safe memory lifecycle management across application states, especially when dealing with external input streams like HTTP requests. The focus on multiple related flaws stemming from session handling (CVE-2026-115560, CVE-2026-129481) indicates that the complexity of state management acts as a persistent attack surface, where small failures in cleanup or deserialization can compound into critical remote execution vectors. The implication is that security resilience requires not just patching specific code paths but enforcing stricter, more deterministic rules around memory ownership and context switching within the execution environment itself.
BRIDGE QUESTIONS:
What are the systemic architectural assumptions underpinning PHP's session and request lifecycle management that allow these state transitions to introduce such severe risks?
How can development practices be shifted to prioritize verifiable memory safety across serialization boundaries rather than relying solely on runtime mitigations against known gadget chains?
If memory corruption vulnerabilities are inherent to concurrent or asynchronous execution, what new layers of verification are necessary to ensure application-level integrity remains intact regardless of runtime state?
From the original · SecurityWeek
PHP on Thursday rolled out a fresh set of security patches as part of its four-week update schedule, including fixes for seven critical-severity remote code execution (RCE) vulnerabilities. First in line is CVE-2026-115560, which was publicly disclosed last month, two days after PHP2Shell patches landed.Read the full story at securityweek.com
Sentinel unavailable
The automated check of the source article's wording did not complete, so no result is shown.
This looks only at the wording of the original source article, not at this page's AI-written sections. A small local AI model made this estimate. It has not been checked against known human and machine texts, so treat it as provisional. It cannot show who wrote an article.
