Back Ox.Security The 2026 Vulnpocalypse Hits PHP: Four Critical RCEs, but How Dangerous Are They?
PHP has patched four critical remote code execution vulnerabilities, each rated 9.2. But exploiting them requires specific conditions, raising questions their real-world risk. Here’s what security teams need to know.
On November 19, 2026, PHP released security updates for versions 8.5, 8.4, 8.3 and 8.2, addressing 19 CVEs in PHP 8.5.13 alone. Four of the vulnerabilities — CVE-2026-115560, CVE-2026-126714, CVE-2026-129474 and CVE-2026-129496 — are classified as critical remote code execution (RCE) flaws.
Despite their critical ratings, exploiting these vulnerabilities is far from straightforward. Each requires specific conditions, ranging from unusual PHP configurations to precise timing or memory manipulation. Some may cause crashes more readily than remote code execution. The result is a significant gap between their severity scores and the risk they pose to most real-world environments.
PHP is an open-source server-side scripting language that powers much of the web, including websites and applications built on WordPress, Drupal, Magento and Laravel. It commonly runs through PHP-FPM behind NGINX or Apache, or as an Apache module (mod_php).
Upgrade promptly, but prioritize based on exposure. Update to PHP 8.5.13, 8.4.28, 8.3.37 or 8.2.36, as appropriate for your environment. Rebuild affected container images and restart PHP-FPM workers to ensure the fixes take effect.
Check session upload progress settings. Review your configuration for session.upload_progress.enabled. If enabled, investigate whether applications or processes sharing session storage use different serializers. This is a key prerequisite for exploiting CVE-2026-115560.
Review exception settings on PHP 8.5. Check whether zend.exception_ignore_args is set to 0. If so, consider setting it to 1 or disabling fatal error backtraces with fatal_error_backtraces=0 as a temporary mitigation for CVE-2026-129474. Pay particular attention to containers without a php.ini, where built-in defaults may apply.
CVE-2026-115560: Session Serializer Mismatch
Unlike the other three vulnerabilities, CVE-2026-115560 is a logic flaw, not a memory corruption bug, making exploitation reliable when the right conditions are present.
An attacker would need three conditions:
Session upload progress is enabled.
Mismatched session serializers. One component writes session data using php_serialize or php_binary, while another reads it using php. This can occur when applications, PHP-FPM pools or CLI jobs session storage, or when session settings are changed at runtime.
A usable deserialization gadget chain. Libraries such as Guzzle and Monolog have been demonstrated to enable command execution under these conditions.
The fix disables session upload progress by default and prevents runtime changes to session settings while upload progress is enabled. You can see the changes in the official PHP patch .
CVE-2026-126714: Partially Overwritten Session Files
CVE-2026-126714 can occur when a session file write is interrupted, leaving old and new session data mixed together. Under the right conditions, this corrupted data could potentially be exploited for remote code execution through unsafe deserialization.
Exploitation requires an attacker to control session content and interrupt the write at a precise point. This is most plausible in a threaded (ZTS) PHP build, where another thread could force the process to exit during the write. A usable deserialization gadget chain is also required.
The patch fixes the issue by always truncating the session file before writing new data and failing the operation if truncation is unsuccessful. This prevents leftover session data from being combined with new data.
CVE-2026-129474: Use-After-Free in Backtraces
CVE-2026-129474 affects PHP 8.5 only. The vulnerability involves a use-after-free condition when PHP generates backtraces involving magic methods such as __call and __callStatic.
Exploitation requires several specific conditions:
zend.exception_ignore_args=0
A request path that invokes a magic method, such as those used by Laravel facades
A request that triggers the memory limit at precisely the right moment
An ASLR bypass to achieve reliable remote code execution
Under these conditions, triggering a crash is more realistic than achieving RCE.
The patch corrects how PHP handles arguments in backtraces involving __call and __callStatic. These methods store arguments differently from ordinary function calls, which could cause PHP to access freed memory. The fix also ensures that the resulting string is properly terminated.
CVE-2026-129496: Timezone Cache Use-After-Free
CVE-2026-129496 is a use-after-free vulnerability involving PHP’s date extension and its timezone cache. The issue can occur when PHP attempts to log an error during startup, before the relevant components have been fully initialized.
Exploitation requires several specific conditions:
A non-thread-safe PHP build
A warning triggered during startup
error_log configured to write to a file
A request handled by a newly started worker
The patch fixes the issue by changing how PHP formats timestamps in error logs. It now uses the timezone cache only after the necessary modules have been activated and the PHP executor is running, preventing access to freed memory.
Our Verdict: Mostly Trend, With One Config Worth Checking
Measured against the Trend or Risk checklist from our Cry2Wolf analysis :
Exploited in the wild? No exploitation has been reported.
Working exploit? No. None of the four has a public one-shot exploit.
Reliable? Mostly no. Three are memory corruption bugs that need precise timing, specific builds or an ASLR bypass. CVE‑2026‑115560 is the exception: it’s reliable, but only when its conditions are met.
Preconditions? Every CVSS vector has “Attack Requirements: Present.” Three of the four need a non-default or unusual configuration before an attack can even start.
Severity? All four are rated Critical (9.2). On paper, this is the most severe of the recent “named” disclosures, and that’s why config checks matter here.
Bottom line: mostly trend. Patch on your normal cycle, but today check two settings: whether session.upload_progress.enabled is on with mixed session serializers, and whether zend.exception_ignore_args=0 on PHP 8.5. Those two cover the most realistic attack paths. We will update this verdict if exploitation is observed.
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
