
PEACH
Un cadre d’isolation des locataires
CVE-2026-129474 is a use-after-free vulnerability in PHP's magic method backtrace handling that can lead to remote code execution. It affects PHP versions 8.5.0 through 8.5.12 (fixed in 8.5.13), and was disclosed on November 19, 2026 via a GitHub Security Advisory. The flaw occurs when PHP collects arguments for methods handled by __call() or __callStatic() during backtrace generation, potentially reading stale values referencing freed memory. It carries a CVSS v4.0 base score of 9.2 (Critical) (GitHub Advisory).
The root cause is a use-after-free (CWE-416) in PHP's backtrace collection logic. Before PHP enters a magic method (__call() or __callStatic()), it briefly represents the requested method as a separate call frame; a backtrace taken during this interval can collect stale values from an earlier call that reference already-freed memory. Exploitation requires two non-default-safe conditions to be simultaneously active: fatal_error_backtraces=1 (the PHP 8.5 default) and zend.exception_ignore_args=0 (the PHP built-in default, but overridden by php.ini-production). The demonstrated attack vector involves submitting a crafted, oversized JSON body to an endpoint that processes it and logs via a magic static method, causing a memory_limit fatal error at the precise moment the magic method call is being entered — a behavior enabled by delayed allocation-failure handling introduced in PHP 8.5.12. Successful exploitation also requires knowledge of usable memory addresses to bypass ASLR for reliable code execution (GitHub Advisory).
Successful exploitation allows an unauthenticated remote attacker to execute arbitrary code with the privileges of the PHP worker process, resulting in full compromise of confidentiality, integrity, and availability of the affected system. Less sophisticated attempts can crash the PHP worker process (denial of service) or produce ordinary resource-limit errors. Potentially affected application patterns include Laravel facades and Magento guest shipping estimation endpoints, though full exploitation of complete framework installations has not been publicly demonstrated (GitHub Advisory).
As of the disclosure date (November 19, 2026), there is no public proof-of-concept exploit and no evidence of in-the-wild exploitation (GitHub Advisory). The EPSS score is 0.0, reflecting the absence of observed exploitation activity at time of publication (Feedly). Exploitation complexity is high, requiring specific configuration conditions, control over memory allocation via request data, a reachable magic method call path, and knowledge of memory addresses to achieve reliable code execution rather than a crash. The vulnerability is not listed in the CISA KEV catalog at this time.
fatal_error_backtraces=1 (default) and zend.exception_ignore_args=0 (built-in default). Target applications using __call() or __callStatic() magic methods in request-handling paths, such as Laravel facade-based logging or Magento guest endpoints.__callStatic().memory_limit threshold exactly while the magic method call frame is being entered, triggering a fatal error at the vulnerable interval.zend.exception_ignore_args=0, PHP reads stale values from the freed call frame, which may contain attacker-influenced bytes from reused memory.memory_limit) to endpoints known to use magic method dispatch (e.g., logging facades, API import endpoints); repeated requests from the same source with varying body sizes suggesting heap-grooming attempts.Fatal error: Allowed memory size exhausted coinciding with magic method invocations (__call or __callStatic); PHP-FPM logs showing unexpected worker process crashes or restarts (SIGABRT, SIGSEGV) correlated with specific request patterns./tmp by the PHP worker user; new cron entries or SSH authorized keys added under the web server account (GitHub Advisory).The primary remediation is upgrading to PHP 8.5.13 or later, which contains the fix (GitHub Advisory). For immediate workarounds prior to upgrading, set zend.exception_ignore_args=1 in the php.ini configuration used by affected PHP workers (including FPM pool configs) and restart them — note that changing only the CLI configuration is insufficient. Alternatively, setting fatal_error_backtraces=0 on PHP 8.5+ also blocks this attack path. Administrators using php.ini-production as their base configuration are already protected, as it sets zend.exception_ignore_args=1 by default. Additionally, enforcing request-size limits and avoiding expensive processing or logging of untrusted request bodies can reduce exposure, but these are not complete substitutes for the configuration fix or upgrade.
The vulnerability received broad coverage across the security community upon disclosure on November 19, 2026, with outlets including BleepingComputer, SecurityWeek, The Hacker News, and Infosecurity Magazine reporting on the PHP 8.5.13 release fixing multiple critical flaws (BleepingComputer, SecurityWeek, The Hacker News). Checkmarx published analysis noting the complexity of exploitation and the configuration-dependent nature of the attack (Checkmarx). OX Security contextualized the flaw within a broader wave of PHP critical vulnerabilities in 2026 (OX Security). Patchstack highlighted implications for WordPress hosting environments (Patchstack).
Corrigez la disponibilité entre les grandes distributions Linux et leurs versions.
bionic (esm-infra)
php7.2
devel
php8.5
focal (esm-infra)
php7.4
jammy
php8.1
noble
php8.3
resolute
php8.5: 8.5.4-0ubuntu1.6
trusty (esm-infra-legacy)
php5
xenial (esm-infra-legacy)
php7.0
Source: Ce rapport a été généré à l’aide de l’IA
Évaluation gratuite des vulnérabilités
Évaluez vos pratiques de sécurité cloud dans 9 domaines de sécurité afin d’évaluer votre niveau de risque et d’identifier les lacunes dans vos défenses.
Obtenez une démo personnalisée
"La meilleure expérience utilisateur que j’ai jamais vue, offre une visibilité totale sur les workloads cloud."
"Wiz fournit une interface unique pour voir ce qui se passe dans nos environnements cloud."
"Nous savons que si Wiz identifie quelque chose comme critique, c’est qu’il l’est réellement."