PHP Group PHP
Timezone cache use-after-free can lead to remote code execution
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 8.2.0, < 8.2.36
- >= 8.3.0, < 8.3.37
- >= 8.4.0, < 8.4.28
- >= 8.5.0, < 8.5.13
Fixed in 8.2.36, 8.3.37, 8.4.28, 8.5.13
Mitigation
Upgrade PHP to 8.2.36 or 8.3.37 or 8.4.28 or 8.5.13 or later.
References
- Vendor advisory github.com/php/php-src/security/advisories/GHS…
Timeline
Days relative to CVE publicationFirst public PoC 4 h after publication; not in CISA KEV. First PoC: abraxas/php-tzcache-rce (created 19 Nov 2026, found by us: 19 Nov 2026).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| abraxas/php-tzcache-rce | 19 Nov 2026 +4 h | 19 Nov 2026 | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.