Testing Blog

CVE-2026-129474: PHP Use-After-Free in Magic… | Uptycs

Written by Uptycs Threat Research | Nov 20, 2026, 1:00:42 PM
CVE IDCVE-2026-129474
Affected productPHP Group PHP
SeverityCritical CVSS 9.2 (v4.0)
ExploitationNo known exploitation
CISA KEVNot listed
Fix availableYes
Bulletin statusAnalysis complete · Last updated 2026-11-20

Key takeaways

  • Affects PHP (PHP Group) 8.5.0 through 8.5.12.
  • No known exploitation yet: patch before attackers catch up.
  • Upgrade PHP to 8.5.13 or later: This is the only complete fix. Use your platform's package manager or the official PHP binaries; for example, on systems with an OS-managed PHP package, check whether your distribution….

Summary

CVE-2026-129474 is a use-after-free vulnerability (CWE-416) in PHP's backtrace argument collection for magic method calls (__call() and __callStatic()). When a fatal error — such as exceeding memory_limit — occurs while PHP is collecting arguments for a backtrace, it may read stale values referencing freed memory. A remote attacker who can influence enough request data to affect memory allocation may trigger memory corruption, crash the PHP worker process, or, with knowledge of memory layout, execute arbitrary code. The flaw was disclosed on 19 November 2026 and is fixed in PHP 8.5.13, released the same day.

Technical details

The root cause is a use-after-free condition in the Zend Engine's backtrace logic. When fatal_error_backtraces is enabled (the default) and zend.exception_ignore_args is disabled (also the default in php.ini-development), PHP collects method arguments at the moment a fatal error fires. If that fatal error interrupts a __call() or __callStatic() dispatch, the engine may reference argument values that point to memory already freed during error handling, producing a corrupted state. Exploitation requires no authentication and no prior foothold, but the CVSS 4.0 vector (AV:N/AC:H/AT:P/PR:N/UI:N) reflects high attack complexity and the need for specific preconditions: the attacker must reliably trigger a fatal error at the right moment and have sufficient influence over heap layout. The exact internal code path has not been made fully public. Notably, php.ini-production sets zend.exception_ignore_args=On, which prevents argument collection and blocks this vulnerability — deployments using that template are not exposed.

CVSS vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Affected products

Product / branchAffected versionsFixed version
PHP (PHP Group)8.5.0 through 8.5.128.5.13

Impact

  • Remote code execution: An attacker with no credentials who can shape request data may, under specific heap conditions, redirect execution to attacker-controlled code.
  • Worker process crash: Even without achieving code execution, triggering the use-after-free can crash the PHP worker, causing denial of service for affected applications.
  • Memory corruption: The freed-memory read can corrupt adjacent heap structures, potentially affecting application state or data integrity beyond the immediate crash.
  • Scope limited by configuration: Deployments that follow `php.ini-production` defaults (`zend.exception_ignore_args=On`) are not affected; risk is concentrated in development-style or custom configurations where argument collection is active.

Exploitation status

As of the disclosure date (19 November 2026), there is no confirmed in-the-wild exploitation and no public proof-of-concept code. CISA's SSVC assessment classifies exploitation as "none" and notes the vulnerability is not automatable. Despite the absence of active exploitation, the critical CVSS score and unauthenticated remote attack vector justify treating this as high patch priority, particularly for internet-facing PHP 8.5 deployments not using php.ini-production defaults.

Recommendations

  1. Upgrade PHP to 8.5.13 or later: This is the only complete fix. Use your platform's package manager or the official PHP binaries; for example, on systems with an OS-managed PHP package, check whether your distribution has issued an updated package for PHP 8.5.13.
  2. Apply the interim configuration mitigation: If immediate upgrade is not possible, set zend.exception_ignore_args=On in php.ini. This disables argument collection during backtraces and blocks the vulnerable code path. Restart the PHP process after the change.
  3. Verify the mitigation is active: Confirm the running configuration with php -i | grep zend.exception_ignore_args and ensure the value is On. For PHP-FPM or web server SAPI deployments, verify the pool or virtual-host configuration has not overridden this setting.
  4. Audit exposure of magic method surfaces: Review application code that relies on __call() or __callStatic() on externally reachable endpoints, as these are the code paths that can reach the vulnerable backtrace logic.
  5. Review access logs for anomalous fatal-error patterns: Look for repeated requests that appear designed to push PHP worker memory to its limit (memory_limit exhaustion), which may indicate reconnaissance or exploitation attempts.
  6. Confirm php.ini profile in use: For all production systems, validate that php.ini-production or an equivalent hardened configuration is the active baseline, not php.ini-development.

How Uptycs helps

Uptycs vulnerability management continuously inventories PHP versions across hosts, containers, and cloud workloads, allowing security teams to immediately identify every asset running an affected PHP 8.5.x release and prioritize patching based on exposure. Uptycs Threat Research is actively monitoring CVE-2026-129474 for shifts in exploitation activity and will update this bulletin if public exploits emerge or in-the-wild attacks are observed.

References

Update history

  • 2026-11-20: Initial publication.

See how Uptycs finds affected assets across your hybrid cloud.

Get a demo
White Paper

Verifiable AI: The Foundation for Trust in Cybersecurity

Download copy

Index