Timezone cache use-after-free can lead to remote code execution
2 public exploits exists; no exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 8%. Fixed in PHP 8.2.36, PHP 8.3.37, PHP 8.4.28 and 1 more.
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 before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28 and 8.5.* before 8.5.13.
Briefing
Written from the sources below · deepseek-v4.1-flash
A timezone cache use-after-free affects non-thread-safe PHP builds when early diagnostics access memory freed after a startup error_log diagnostic. Unauthenticated attackers can crash PHP-FPM, Apache mod_php, or CGI workers and code execution may be possible; versions before 8.2.36, 8.3.37, 8.4.28, and 8.5.13 are affected.
Why it mattersPublic PoC and writeup exist, EPSS is 8%, and unauthenticated crafted requests can crash workers, with code execution demonstrated.
ActionUpgrade to PHP 8.2.36, 8.3.37, 8.4.28, or 8.5.13.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| PHP Group | PHP | <8.2.36, >=8.3.0 <8.3.37, >=8.4.0 <8.4.28, >=8.5.0 <8.5.13 | 8.2.36, 8.3.37, 8.4.28, 8.5.13 |
Exploit evidence
2 public sources
Coverage
News and research mentioning this CVE
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in PHP, strongest first
Embed
A live severity badge for an advisory, README or ticket