
PEACH
Un cadre d’isolation des locataires
CVE-2026-129481 is a heap use-after-free vulnerability in PHP's session extension, triggered by interrupted session shutdown via a fatal error in a user-defined stream wrapper callback. It affects PHP versions 8.3.0–8.3.36, 8.4.0–8.4.27, and 8.5.0–8.5.12; PHP 8.2 and earlier are not affected. The vulnerability was disclosed on November 19, 2026, and is described as an incomplete fix for CVE-2026-109619. It carries a CVSS v4.0 base score of 9.2 (Critical) (GitHub Advisory).
The root cause is classified as CWE-416 (Use After Free) and CWE-459 (Incomplete Cleanup). When a PHP session starts, the session extension records the executing script's filename in an internal global variable. If a fatal error occurs in an application callback during session variable destruction at shutdown — such as in a user-defined stream wrapper's stream_close() method — session shutdown is aborted before the filename pointer is released or cleared. The request heap is subsequently freed while the worker process retains the stale filename pointer; a subsequent request handled by the same worker can then release this dangling pointer, triggering the use-after-free. Exploitation requires OPcache to be disabled (so the filename is allocated in request memory rather than persistent OPcache memory) and that both requests reach the same PHP-FPM worker (GitHub Advisory).
Successful exploitation can result in memory corruption or a PHP worker process crash, causing denial of service. An attacker who can control session cleanup behavior may also potentially read sensitive memory contents through the heap use-after-free condition. While remote code execution has not been demonstrated through this specific field, the advisory notes it is theoretically possible if memory layout can be controlled. The two requests involved do not need to belong to the same user or session — only the same PHP-FPM worker process (GitHub Advisory).
No public proof-of-concept exploit code is known to exist, and there is no evidence of active in-the-wild exploitation as of the disclosure date (GitHub Advisory). The EPSS score is 0.0, reflecting the current absence of observed exploitation activity. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. Exploitation requires high attack complexity, including the ability to trigger a fatal error in a session cleanup callback and route a follow-up request to the same PHP-FPM worker, with OPcache disabled.
stream_wrapper_register()) that stores a stream resource in the session. The stream wrapper's stream_close() method must be designed to raise a fatal error during cleanup.stream_close() during session variable destruction at shutdown, aborting session cleanup before the script filename pointer is released.stream_close() callbacks; repeated worker crashes or restarts in php-fpm.log./var/log/syslog or dmesg) referencing PHP worker PIDs.stream_close() callbacks, particularly in upload or user-controlled directories (GitHub Advisory).Upgrade PHP to the fixed versions: 8.3.37, 8.4.28, or 8.5.13. The fix clears the recorded session filename and line number during session initialization and terminates the PHP process if a module's request-shutdown handler bails out, preventing reuse of a partially cleaned-up worker. If immediate patching is not possible, set pm.max_requests=1 in PHP-FPM configuration to prevent a worker from handling a second request after a failed cleanup (at a performance cost). Additionally, avoid fatal errors in callbacks reached during session cleanup, and consider disabling or restricting user-defined stream wrappers. Enabling OPcache alone is not a reliable mitigation, as scripts can still execute without being cached (GitHub Advisory).
The vulnerability received broad coverage across the security community following the November 19, 2026 PHP security release. Security outlets including The Hacker News, SecurityWeek, Infosecurity Magazine, and CyberSecurityNews reported on the PHP patch batch, which addressed multiple critical flaws. Patchstack highlighted the implications for WordPress environments, and Checkmarx published analysis noting what is known and unknown about the critical PHP security release. Community discussion was active on Mastodon and developer forums, with practitioners emphasizing the importance of upgrading PHP-FPM deployments promptly (GitHub Advisory).
Corrigez la disponibilité entre les grandes distributions Linux et leurs versions.
bionic (esm-infra)
php7.2: 7.2.24-0ubuntu0.18.04.17+esm15
devel
php8.5
focal (esm-infra)
php7.4: 7.4.3-4ubuntu2.29+esm6
jammy
php8.1: 8.1.2-1ubuntu2.29
noble
php8.3: 8.3.6-0ubuntu0.24.04.14
resolute
php8.5: 8.5.4-0ubuntu1.6
trusty (esm-infra-legacy)
php5: 5.5.9+dfsg-1ubuntu4.29+esm19
xenial (esm-infra-legacy)
php7.0: 7.0.33-0ubuntu0.16.04.16+esm23
RHEL 8
RHEL 9
php:8.3/php.src
RHEL 10
php8.4-0:8.4.28-1.el10_3.src
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."