CVE-2026-129496
Description
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected products
2Patches
Vulnerability mechanics
References
1News mentions
8- CVE-2026-129289 and Other Critical PHP Vulnerabilities: What WordPress Site Owners Need to KnowWordfence Blog · Nov 20, 2026
- How Cloudflare WAF helps protect against phpAfterShell and other critical PHP flawsCloudflare Blog · Nov 20, 2026
- Critical PHP Flaws Allow Code Execution, but Don't Panic 'PHP2Shell'-StyleDark Reading · Nov 19, 2026
- PHP Patches Seven Critical RCE VulnerabilitiesSecurityWeek · Nov 19, 2026
- PHP Releases Patches to Fix 18 VulnerabilitiesInfosecurity Magazine · Nov 19, 2026
- PHP’s November 2026 Security Release: What Reaches WordPressPatchstack Blog · Nov 19, 2026
- PHP Fixes 7 Critical Flaws, Including Bugs That Could Allow Remote Code ExecutionThe Hacker News · Nov 19, 2026
- PHP Warns of Critical Security Flaws Affecting All Supported Versions, Urges Users to UpdateCyber Security News · Nov 19, 2026