
PEACH
Un cadre d’isolation des locataires
CVE-2026-129182 is a use-after-free vulnerability in PHP 8.5 involving the repopulation of the last_fatal_error_backtrace global after executor shutdown. It affects PHP versions 8.5.0 through 8.5.12 (fixed in 8.5.13). The flaw was disclosed on November 19, 2026, via a GitHub Security Advisory. It carries a CVSS v4.0 base score of 9.2 (Critical) (GitHub Advisory).
The root cause is a use-after-free (CWE-416) combined with incomplete cleanup (CWE-459) in PHP's fatal error backtrace handling. During request shutdown, PHP restores modified INI settings; if a fatal error occurs at this stage — triggered by conflicting max_memory_limit or zlib.output_compression/output_handler settings — the last_fatal_error_backtrace global is repopulated after the executor has already been torn down. The request heap is subsequently freed, but a diagnostic emitted early in a later request handled by the same PHP-FPM or mod_php worker can access the now-stale backtrace pointer, causing a heap use-after-free. Exploitation requires specific per-path INI configuration (e.g., max_memory_limit overrides or zlib.output_compression + output_handler via .user.ini) and an early diagnostic trigger in a subsequent request (via Apache per-directory config or FastCGI PHP_VALUE/PHP_ADMIN_VALUE parameters). This vulnerability is a follow-on to CVE-2026-109619 (GHSA-6wmf-4rv5-p3rp), which addressed a related but narrower scenario (GitHub Advisory).
Successful exploitation can result in memory corruption, PHP-FPM or mod_php worker crashes (availability impact), and potentially full remote code execution (RCE), though RCE through the specific identified entry points has not yet been demonstrated. An unauthenticated attacker could also read sensitive data from freed memory regions, exposing confidential server-side information. The integrity of the affected worker process is also at risk due to heap corruption (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. The EPSS score is 0.0, and the vulnerability is not listed in the CISA KEV catalog. Exploitation requires specific server-side configuration conditions (per-path INI overrides and an early diagnostic trigger), which limits the attack surface compared to fully unauthenticated, configuration-agnostic vulnerabilities (GitHub Advisory).
.user.ini files or Apache <Directory> blocks)..user.ini sets zlib.output_compression=0 and output_handler=ob_gzhandler while the global config has zlib.output_compression=1, or where a path-specific max_memory_limit is lower than the global value and memory usage exceeds it at shutdown.last_fatal_error_backtrace after executor cleanup.PHP_VALUE/PHP_ADMIN_VALUE FastCGI parameter from a controlled or compromised frontend.max_memory_limit exceeded or zlib/output_handler conflicts); repeated worker crash/restart events in PHP-FPM logs ([pool www] child ... exited on signal 11 (SIGSEGV))..user.ini with zlib.output_compression or output_handler overrides.PHP_VALUE or PHP_ADMIN_VALUE parameters from the frontend proxy, especially those setting INI values that conflict with global configuration..user.ini files in web-accessible directories containing zlib.output_compression, output_handler, or max_memory_limit directives that differ from global PHP configuration.Upgrade to PHP 8.5.13 or later, which contains the fix that prevents PHP from creating or consuming the fatal-error backtrace while the executor is inactive. As an immediate workaround, set fatal_error_backtraces=0 in php.ini and restart all PHP-FPM or mod_php workers; ensure that request-specific configuration (e.g., .user.ini) cannot re-enable this setting. Administrators should also audit per-path INI configurations for conflicting zlib.output_compression/output_handler or max_memory_limit overrides to reduce the attack surface (GitHub Advisory).
The vulnerability received broad coverage from security media outlets including The Hacker News, SecurityWeek, Infosecurity Magazine, and CyberSecurityNews, all noting PHP's November 2026 security release patching multiple critical flaws. Checkmarx published analysis noting the significance of the release. Community discussion on Mastodon (infosec.exchange) and developer blogs (ma.ttias.be, dev.to) highlighted the complexity of the exploitation preconditions. Patchstack flagged the release as relevant to WordPress hosting environments due to PHP-FPM usage (GitHub Advisory).
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."