cve.bz

CVE-2026-129474 Use-after-free in magic method backtraces can lead to remote code execution

9.2 criticalEPSS 7.2%

Critical (9.2) in php group php. EPSS 7.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

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:N
EPSS
7.2% estimated probability of exploitation activity in the next 30 days; 94th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-416 Use After Free
Published
Modified
Assigned by
php (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-129474 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-129474?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-129474?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-129474 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
PHP Group PHPfrom 8.5.0 before 8.5.13

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu22.04:LTSphp8.1no fix listedUBUNTU-CVE-2026-129474
Ubuntu24.04:LTSphp8.3no fix listedUBUNTU-CVE-2026-129474
Ubuntu26.04:LTS, 26.10php8.5no fix listedUBUNTU-CVE-2026-129474
UbuntuPro:14.04:LTSphp5no fix listedUBUNTU-CVE-2026-129474
UbuntuPro:16.04:LTSphp7.0no fix listedUBUNTU-CVE-2026-129474
UbuntuPro:18.04:LTSphp7.2no fix listedUBUNTU-CVE-2026-129474
UbuntuPro:20.04:LTSphp7.4no fix listedUBUNTU-CVE-2026-129474
openSUSETumbleweedphp88.5.13-1.1openSUSE-SU-2026:12618-1

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu · openSUSE.

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

References

Check your stackJSON