
PEACH
Un cadre d’isolation des locataires
CVE-2026-129496 is a timezone cache use-after-free vulnerability in PHP that can lead to remote code execution or denial of service. It affects PHP versions 8.2.0–8.2.35, 8.3.0–8.3.36, 8.4.0–8.4.27, and 8.5.0–8.5.12 (non-thread-safe builds only). The vulnerability was published on November 19, 2026, with patched versions released the same day. It carries a CVSS v4 base score of 9.2 (Critical) (GitHub Advisory, Feedly).
The root cause is a use-after-free (CWE-416) combined with incomplete cleanup (CWE-459) in PHP's timezone cache handling within non-thread-safe builds. During module startup, if a diagnostic is written to a file-based error_log (e.g., due to an invalid date.timezone value or a session configuration warning), PHP allocates the timezone cache in temporary startup memory. That memory is freed at the end of startup, but the internal reference to the cache persists until the date extension initializes the first request. When an early request-phase diagnostic — such as the max_input_vars warning — fires in a fresh worker, it accesses the already-freed hash table, which may contain attacker-controlled request data. In FPM and Apache mod_php, workers inherit the stale reference from the parent process, and the vulnerable window persists until the worker completes its first normal request (GitHub Advisory).
A successful exploit allows an unauthenticated remote attacker to crash PHP-FPM, Apache mod_php, or CGI workers via a crafted HTTP request, causing denial of service. Beyond crashes, arbitrary code execution with the privileges of the PHP worker process has been demonstrated locally in both FPM and Apache mod_php environments using known memory addresses. Exploitation does not require application-level code execution or attacker control of PHP_VALUE/PHP_ADMIN_VALUE, meaning the attack surface extends to any vulnerable PHP deployment meeting the startup-diagnostic preconditions (GitHub Advisory, Feedly).
As of the disclosure date (November 19, 2026), no public proof-of-concept exploit code has been released and no in-the-wild exploitation has been observed (Feedly). However, code execution has been demonstrated privately in controlled lab conditions for both FPM and Apache mod_php using known runtime addresses, with ASLR remaining enabled during the proofs. The EPSS score is currently 0.0, and the vulnerability is not listed in the CISA KEV catalog at this time. Exploitation requires specific preconditions: a non-thread-safe PHP build, a file-based error_log, a startup-phase diagnostic, and an early request-phase diagnostic in a fresh worker (GitHub Advisory).
error_log configured and a startup diagnostic condition present (e.g., invalid date.timezone or deprecated session settings), which causes the timezone cache to be allocated in startup memory.max_input_vars via a large number of POST parameters), causing the worker to access the freed timezone cache.max_input_vars), oversized Authorization headers, or POST bodies approaching or exceeding the PHP memory limit, particularly targeting fresh or recycled workers.max_input_vars warnings or memory limit errors coinciding with worker crashes; FPM or Apache error logs showing unexpected worker terminations (segmentation faults, SIGSEGV) shortly after worker startup.Upgrade PHP to the patched versions: 8.2.36, 8.3.37, 8.4.28, or 8.5.13, which fix the issue by formatting error log timestamps in UTC outside of a fully initialized active request, avoiding use of request-local timezone state at unsafe lifecycle points. As a temporary workaround, correct any configuration errors or deprecated settings that produce startup diagnostics (e.g., fix invalid date.timezone values, resolve session deprecation warnings) and restart the PHP master process and all workers. Redirecting PHP errors to syslog instead of a file-based error_log also avoids the demonstrated trigger. Note that modifying $_REQUEST or cookie settings alone is not a complete mitigation, as the Apache cleanup path does not require those settings (GitHub Advisory, Feedly).
The vulnerability received broad coverage from security media outlets including BleepingComputer, SecurityWeek, The Hacker News, and Infosecurity Magazine, all highlighting the critical RCE potential across the November 2026 PHP security release batch (BleepingComputer, SecurityWeek). The WordPress and Joomla hosting communities responded quickly, with platforms like Patchstack and Roots.io publishing guidance for patching PHP on managed servers (Patchstack, Roots.io). Checkmarx and OX Security published analytical posts noting the complexity of the exploitation chain and the conditions required for full RCE (Checkmarx, OX Security). Social media discussion on Infosec.Exchange noted the non-thread-safe build restriction as a meaningful limiting factor for real-world exploitation.
Corrigez la disponibilité entre les grandes distributions Linux et leurs versions.
bookworm
php8.2: 8.2.36-1~deb12u1
sid
php8.4: 8.4.28-2
trixie
php8.4: 8.4.28-1~deb13u1
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
php:7.4/php.src
RHEL 9
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."