CVE-2026-129474PHP engine >= 8.5.0, Use After Free
NVD
Vulnerability Summary
Use-after-free in magic method backtraces can lead to remote code execution. PHP can access freed memory when collecting the arguments of a method handled by call() or callStatic() for a backtrace. On PHP 8.5 and later, an unauthenticated attacker may be able to trigger this through a crafted request that causes a fatal error while the application enters such a method. Successful exploitation can execute arbitrary code with the privileges of the PHP worker. The demonstrated remote attack requires fatal_error_backtraces=1 and zend.exception_ignore_args=0. Fatal error backtraces are enabled by default in PHP 8.5. PHP's built-in default also includes arguments, but php.ini-production sets zend.exception_ignore_args=1 and prevents this attack path.
CVSS v4.0 Base Metrics — Score 9.2 (CRITICAL)
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NAttack VectorNetwork
Attack ComplexityHigh
Attack RequirementsPresent
Privileges RequiredNone
User InteractionNone
Confidentiality (Vulnerable System)High
Integrity (Vulnerable System)High
Availability (Vulnerable System)High
Confidentiality (Subsequent System)None
Integrity (Subsequent System)None
Availability (Subsequent System)None
Affected & Patched Versions
- PHP engine >= 8.5.0, < 8.5.13
- PHP 8.5.13
What to do
Plan remediation soon. No exploitation is confirmed yet, but the severity is critical.
- Check whether you run PHP engine >= 8.5.0, and which version.
- Update to a patched version listed above, then confirm the new version.
- Until you can update, follow the vendor workaround: As an immediate workaround for the fatal error attack, set zend.exception_ignore_args=1 in the configuration used by the affected PHP workers and restart them. On PHP 8.5 and later, setting fatal_error_backtraces=0 also prevents this attack path. Check the effective configuration, including FPM pool settings and application overrides. Changing only the CLI configuration is insufficient.
- Until you can update, follow the vendor workaround: Setting display_errors=0 does not prevent PHP from constructing the backtrace. Request-size limits and avoiding expensive processing or logging of untrusted bodies can reduce exposure, but are not a complete substitute for the configuration workaround or update. Extensions that independently inspect interrupted calls should also be reviewed.
Timeline
- Nov 19, 2026Published
- Nov 19, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new PHP engine >= 8.5.0, CVEsYou are reading CVE-2026-129474. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsRelated Coverage
External References
Data last checked: Nov 19, 2026 14:43 UTC