Wiz rejoint Google Cloud : Faire de la magie ensemble

CVE-2026-129496: 
PHP Analyse et atténuation de la vulnérabilité

Aperçu

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).

Détails techniques

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).

Impact

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).

Exploitabilité

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).

Étapes d’exploitation

  1. Identify vulnerable targets: Scan for internet-facing PHP-FPM, Apache mod_php, or CGI deployments running non-thread-safe PHP 8.2.x < 8.2.36, 8.3.x < 8.3.37, 8.4.x < 8.4.28, or 8.5.x < 8.5.13 using tools like Shodan or Censys.
  2. Confirm preconditions: Verify the target has a file-based 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.
  3. Target a fresh worker: Time requests to hit a newly spawned or recycled PHP worker before it completes its first normal request, as the vulnerable window closes after the first successful request cycle.
  4. Trigger the use-after-free: Send a crafted HTTP request designed to trigger an early request-phase diagnostic (e.g., exceeding max_input_vars via a large number of POST parameters), causing the worker to access the freed timezone cache.
  5. Achieve crash or code execution: For denial of service, the crafted request alone is sufficient to crash the worker. For code execution (as demonstrated in lab conditions), supply attacker-controlled data in request fields (e.g., HTTP Basic Authorization header for FPM, or a POST body exceeding the PHP memory limit for Apache mod_php) to overwrite the freed memory and redirect execution flow with known runtime addresses (GitHub Advisory).

Indicateurs de compromis

  • Network: Repeated HTTP requests with abnormally large numbers of POST parameters (exceeding max_input_vars), oversized Authorization headers, or POST bodies approaching or exceeding the PHP memory limit, particularly targeting fresh or recycled workers.
  • Logs: PHP error log entries showing 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.
  • Process: PHP-FPM or Apache mod_php worker processes crashing and restarting in rapid succession; unexpected child process terminations logged by the process manager.
  • File System: No specific file artifacts are associated with the crash-only exploitation path; however, successful code execution may result in unexpected files written to web-accessible directories or new cron jobs created under the PHP worker's user account (GitHub Advisory).

Atténuation et solutions de contournement

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).

Réactions de la communauté

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.

Ressources supplémentaires

État de correction de la distribution Linux

Corrigez la disponibilité entre les grandes distributions Linux et leurs versions.

Debian

Fixé

bookworm

php8.2: 8.2.36-1~deb12u1

Fixé

sid

php8.4: 8.4.28-2

Fixé

trixie

php8.4: 8.4.28-1~deb13u1

Fixé

Ubuntu

Fixé

bionic (esm-infra)

php7.2: 7.2.24-0ubuntu0.18.04.17+esm15

Fixé

devel

php8.5

Affecté

focal (esm-infra)

php7.4: 7.4.3-4ubuntu2.29+esm6

Fixé

jammy

php8.1: 8.1.2-1ubuntu2.29

Fixé

noble

php8.3: 8.3.6-0ubuntu0.24.04.14

Fixé

resolute

php8.5: 8.5.4-0ubuntu1.6

Fixé

trusty (esm-infra-legacy)

php5: 5.5.9+dfsg-1ubuntu4.29+esm19

Fixé

xenial (esm-infra-legacy)

php7.0: 7.0.33-0ubuntu0.16.04.16+esm23

Fixé

RHEL / CentOS

Fixé

RHEL 8

php:7.4/php.src

Affecté

RHEL 9

php.src

Affecté

RHEL 10

php8.4-0:8.4.28-1.el10_3.src

Fixé

Alpine

Fixé

edge

php83: 8.3.37-r0, 8.5.13-r0

Fixé

Source: Ce rapport a été généré à l’aide de l’IA

Connexe PHP Vulnérabilités :

CVE ID

Gravité

Partition

Technologies

Nom du composant

Exploit CISA KEV

A corrigé

Date de publication

GHSA-hg3m-q4fj-ggmqCRITICAL9.3
  • PHP logoPHP
  • wallabag/wallabag
NonNonNov 20, 2026
CVE-2026-63012MEDIUM6.5
  • PHP logoPHP
  • baserproject/baser-core
NonOuiNov 19, 2026
GHSA-crpp-mf59-rhpqMEDIUMN/A
  • PHP logoPHP
  • api-platform/core
NonOuiNov 20, 2026
GHSA-9wh3-m3m5-jffxMEDIUMN/A
  • PHP logoPHP
  • nowo-tech/transaction-doctrine
NonOuiNov 20, 2026
GHSA-65w2-9r4h-848gMEDIUMN/A
  • PHP logoPHP
  • nowo-tech/transaction-doctrine
NonOuiNov 20, 2026

Évaluation gratuite des vulnérabilités

Évaluez votre posture de sécurité cloud

É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.

Évaluation de la demande

Ressources Wiz supplémentaires

Obtenez une démo personnalisée

Prêt(e) à voir Wiz en action ?

"La meilleure expérience utilisateur que j’ai jamais vue, offre une visibilité totale sur les workloads cloud."
David EstlickRSSI
"Wiz fournit une interface unique pour voir ce qui se passe dans nos environnements cloud."
Adam FletcherChef du service de sécurité
"Nous savons que si Wiz identifie quelque chose comme critique, c’est qu’il l’est réellement."
Greg PoniatowskiResponsable de la gestion des menaces et des vulnérabilités