Skip to main content
Menu
CVEs

CVE

PHP remote code execution in magic method backtraces

Affects PHP 8.5.0 up to before 8.5.13, with fatal error backtraces enabled, exception args not ignored, and a reachable __call() or __callStatic(). Fixed in 8.5.13.

CVE-2026-129474Published Updated Summary written by a model

9.2CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 8.5.13
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. PHP 8.5.x before 8.5.13 Fatal error backtraces enabled and exception args not ignored Application reaches a __call() or __callStatic() magic method while a fatal error (such as exceeding memory_limit) occurs

Summary

A use-after-free flaw in PHP, from the PHP Group, can let an attacker corrupt memory, crash the PHP worker or, in some cases, run arbitrary code. It can be reached remotely without logging in, by sending enough request data to influence memory allocation while a fatal error such as exceeding the memory limit occurs during a magic method call, when argument collection for backtraces is left on (zend.exception_ignore_args disabled).

Original description

Use-after-free in magic method backtraces can lead to remote code execution.

When collecting the arguments of a method call handled by __call() or __callStatic() for a backtrace, PHP can read stale values that may refer to freed memory. If a fatal error such as exceeding memory_limit occurs while an application enters such a call, with fatal_error_backtraces enabled (the default) and zend.exception_ignore_args disabled, a remote attacker who controls enough request data to influence memory allocation may cause memory corruption, crash the PHP worker or, with knowledge of memory addresses, execute arbitrary code. php.ini-production enables zend.exception_ignore_args, which prevents this.

This issue affects PHP versions 8.5.* before 8.5.13.

Who should check

Teams running PHP 8.5.x before 8.5.13 with fatal_error_backtraces on and zend.exception_ignore_args off, e.g. apps using __call/__callStatic such as Laravel facades.

Not fixed by: Changing only the CLI configuration or setting display_errors=0 does not prevent it.

“The demonstrated remote attack requires fatal_error_backtraces=1 and zend.exception_ignore_args=0 .”

github.com

cve.now Index

38Pcve.now Index 38 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach17/20Affects PHP (a widely deployed server, runtime, framework or database)
  • Severity9.2/10CVSS 9.2
  • No patch0/5No signal

What would change the score

  • Would score about 88 if added to CISA KEV
  • Would score about 83 if CISA's SSVC rates exploitation active

What to do

  • Check whether your setup matches what the bug needs.

    PHP 8.5.x before 8.5.13 Fatal error backtraces enabled and exception args not ignored Application reaches a __call() or __callStatic() magic method while a fatal error (such as exceeding memory_limit) occurs
  • Upgrade to a fixed version: 8.5.13.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129474 (Use-after-free in magic method backtraces can lead to remote code execution), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129474 (entry last updated 2026-11-19):
Affected:
- PHP Group PHP: from 8.5.0, fixed in 8.5.13
Fixed versions: 8.5.13.
Conditions (all must be true for the bug to be hit):
- PHP 8.5.x before 8.5.13 (source: https://github.com/php/php-src/security/advisories/GHSA-8mjj-2r7p-4hg2)
- Fatal error backtraces enabled and exception args not ignored (source: https://github.com/php/php-src/security/advisories/GHSA-8mjj-2r7p-4hg2)
- Application reaches a __call() or __callStatic() magic method while a fatal error (such as exceeding memory_limit) occurs (source: https://github.com/php/php-src/security/advisories/GHSA-8mjj-2r7p-4hg2)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129474 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129474 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/php/php-src/security/advisories/GHSA-8mjj-2r7p-4hg2
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129474
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129474"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • PHP Group PHP

    From 8.5.0 · fixed in 8.5.13

Evidence 2

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · php/php-src · Advisory GHSA-8mjj-2r7p-4hg2
CVE record 1Establishes: The identifier and description.
RecordCVE List · CVE-2026-129474

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129474

Is CVE-2026-129474 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A use-after-free bug in how PHP builds backtraces for magic methods (__call() and __callStatic()) can be triggered when a fatal error, such as exceeding memory_limit, occurs. It can lead to arbitrary code execution with the privileges of the PHP worker, or to a worker crash or memory corruption.Source: github.com

Which versions are affected by CVE-2026-129474?

PHP: from 8.5.0 before 8.5.13.Source: cve.now feed data

Am I affected, and how do I check?

PHP 8.5.x from 8.5.0 up to, but not including, 8.5.13. The remote scenario described needs fatal_error_backtraces=1 and zend.exception_ignore_args=0, an application that reaches a __call() or __callStatic() magic method, and a fatal error at the relevant point. The version can be checked with php -v and the two settings with php -i or the php.ini file.Source: github.com

How do I fix CVE-2026-129474?

Upgrade PHP to 8.5.13 or later. The facts list no workaround.Source: github.com

More CVEs