Timezone cache use-after-free can lead to remote code execution
Get instant alerts when new vulnerabilities affect PHP - before attackers find them.
Timezone cache use-after-free can lead to remote code execution. In non-thread-safe builds, a diagnostic written to a file-based error_log during module startup, for example for an invalid date.timezone value or a session configuration warning, causes the timezone cache to be allocated in startup memory that is freed while a reference to it is kept. A diagnostic raised early in the first request of a worker, such as the max_input_vars warning, then accesses the freed cache. On such a deployment an unauthenticated remote attacker can crash PHP-FPM, Apache mod_php or CGI workers with a crafted request. Arbitrary code execution may be possible and has been demonstrated with known memory addresses. This issue affects PHP versions 8.2.* before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28 and 8.5.* before 8.5.13.
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
Generated by AI (claude-fable-5.1) and published by VulnTracker. It is not reviewed by a person, so check the vendor advisory before you act on it.
Upgrade PHP to 8.2.36, 8.3.37, 8.4.28 or 8.5.13 or later for its branch, the versions the CVE description names, prioritising non-thread-safe PHP-FPM, mod_php and CGI deployments that log to a file-based error_log.
A fix is recorded
Guidance updated 2026-11-20
Sign in free to see the steps, fixed versions and workarounds.
SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.
Get alerted
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
This product uses data from the NVD API but is not endorsed or certified by the NVD. CVE records are from the CVE Program (CVE.org).