ALPINE-CVE-2026-129496: Use After Free
Timezone cache use-after-free can lead to remote code execution.
In non-thread-safe builds, a diagnostic written to a file-based errorlog 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 maxinputvars warning, then accesses the freed cache. On such a deployment an unauthenticated remote attacker can crash PHP-FPM, Apache modphp 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
alpine/php83to a version that resolves this vulnerability.Fixed in 8.3.37-r0 - Upgrade
Upgrade
alpine/php84to a version that resolves this vulnerability.Fixed in 8.4.28-r0 - Upgrade
Upgrade
alpine/php85to a version that resolves this vulnerability.Fixed in 8.5.13-r0 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 8.2.36 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 8.3.37 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 8.4.28 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 8.5.13
Event History
Frequently Asked Questions
Which deployments are exposed to remote exploitation?
Exposure is limited to non-thread-safe PHP deployments using PHP-FPM, Apache mod_php, or CGI workers. The described trigger also requires a file-based error_log and a startup diagnostic, such as an invalid date.timezone value or a session configuration warning.
Does exploitation require authentication or user interaction?
No. An unauthenticated remote attacker can trigger crashes with a crafted request when the affected deployment conditions are present; arbitrary code execution may also be possible.
What conditions trigger the use-after-free?
A diagnostic during module startup causes the timezone cache to be allocated in startup memory and later freed while still referenced. A subsequent early diagnostic in a worker's first request, such as a max_input_vars warning, accesses that freed cache.
Which PHP releases contain fixes?
Fixed releases are PHP 8.2.36, 8.3.37, 8.4.28, and 8.5.13. Earlier releases in the affected branches are vulnerable.
What can be done if an immediate upgrade is not possible?
The provided information identifies the required conditions but does not document a complete mitigation. Reducing exposure requires avoiding the affected non-thread-safe deployment scenario and eliminating startup and early-request diagnostics that create the described cache access pattern.