CVE
PHP remote code execution in timezone cache
Affects PHP 8.2–8.5 releases before 8.2.36, 8.3.37, 8.4.28 and 8.5.13, when a startup diagnostic is written through the file-based error_log. Fixed in those versions.
- Exploited
- No known exploitation
- Fix
- Fixed in 8.2.36, 8.3.37, 8.4.28, 8.5.13
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. A startup diagnostic (e.g. invalid date.timezone or session config warning) is written through PHP's file-based error_log
Summary
A use-after-free bug in the timezone cache of PHP (from the PHP Group), in non-thread-safe builds where a startup warning is written to a file-based error log, lets an attacker crash PHP-FPM, Apache mod_php or CGI workers. Arbitrary code execution may also be possible. The attacker can reach it remotely, without logging in, by sending a crafted request.
Original 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 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach17/20Affects PHP (a widely deployed server, runtime, framework or database)
- Severity9.2/10CVSS 9.2
- No patch0/5No signal
What would change the score
- Would score about 88 if added to CISA KEV
- Would score about 83 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
A startup diagnostic (e.g. invalid date.timezone or session config warning) is written through PHP's file-based error_logUpgrade to a fixed version: 8.2.36, 8.3.37, 8.4.28, 8.5.13.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129496 (Timezone cache use-after-free can lead to remote code execution), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129496 (entry last updated 2026-11-19):
Affected:
- PHP Group PHP: from 8.2.0, fixed in 8.2.36; from 8.3.0, fixed in 8.3.37; from 8.4.0, fixed in 8.4.28; from 8.5.0, fixed in 8.5.13
Fixed versions: 8.2.36, 8.3.37, 8.4.28, 8.5.13.
Conditions (all must be true for the bug to be hit):
- A startup diagnostic (e.g. invalid date.timezone or session config warning) is written through PHP's file-based error_log (source: https://github.com/php/php-src/security/advisories/GHSA-gr4f-wgx5-jpfv)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129496 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129496 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/php/php-src/security/advisories/GHSA-gr4f-wgx5-jpfv
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129496
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129496"}.Timeline
- cve.now early warning
PHP readies critical updates to patch RCE flaw CVE-2026-115560
1 day - CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- PHP Group PHP
From 8.2.0 · fixed in 8.2.36; From 8.3.0 · fixed in 8.3.37; From 8.4.0 · fixed in 8.4.28; From 8.5.0 · fixed in 8.5.13
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · php/php-src · Advisory GHSA-gr4f-wgx5-jpfv |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129496 |
| Record | NVD · CVE-2026-129496 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129496
Is CVE-2026-129496 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A use-after-free bug in PHP's timezone cache. A remote unauthenticated attacker can crash PHP workers and may be able to run arbitrary code with the privileges of the PHP worker.Source: github.com
Which versions are affected by CVE-2026-129496?
PHP: from 8.2.0 before 8.2.36; from 8.3.0 before 8.3.37; from 8.4.0 before 8.4.28; from 8.5.0 before 8.5.13.Source: cve.now feed data
Am I affected, and how do I check?
PHP 8.2.0 up to before 8.2.36, 8.3.0 before 8.3.37, 8.4.0 before 8.4.28, and 8.5.0 before 8.5.13. The advisory also requires that a startup diagnostic, such as an invalid date.timezone or a session config warning, is actually written through PHP's file-based error_log. Running `php -v` shows the version, and the error_log and date.timezone settings show how diagnostics are handled.Source: github.com
How do I fix CVE-2026-129496?
Upgrade to the fixed release for the branch in use: 8.2.36, 8.3.37, 8.4.28 or 8.5.13 (or later). The facts name no workaround.Source: github.com