CVE Watchtower

CVE-2026-129496PHP ext-date >= 8.2.0, Use After Free

NVD

Vulnerability Summary

Timezone cache use-after-free can lead to remote code execution. PHP can retain a reference to a freed timezone cache when a diagnostic is written to a PHP error log file during process startup. A later diagnostic during early request initialization can access the freed cache before it is reset. On affected configurations, a remote attacker can trigger memory corruption, cause a worker to crash, and potentially execute arbitrary code with the privileges of the PHP worker.
Severity Level
CRITICAL(9.2)
Published Date
Nov 19, 2026
Last Modified
Nov 19, 2026
Exploitation Status
No confirmed exploitation yet
CVE Record Status
Published
Root Weakness (CWE)
The product reuses or references memory after it has been freed, which can cause a crash or execution of arbitrary code.
CVSS v4.0 Base Metrics — Score 9.2 (CRITICAL)
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Attack VectorNetwork
Attack ComplexityHigh
Attack RequirementsPresent
Privileges RequiredNone
User InteractionNone
Confidentiality (Vulnerable System)High
Integrity (Vulnerable System)High
Availability (Vulnerable System)High
Confidentiality (Subsequent System)None
Integrity (Subsequent System)None
Availability (Subsequent System)None

Affected & Patched Versions

Affected Versions
  • PHP ext-date >= 8.2.0, < 8.2.36
  • PHP ext-date >= 8.3.0, < 8.3.37
  • PHP ext-date >= 8.4.0, < 8.4.28
  • PHP ext-date >= 8.5.0, < 8.5.13
Patched Versions
  • PHP 8.2.36
  • PHP 8.3.37
  • PHP 8.4.28
  • PHP 8.5.13

What to do

Plan remediation soon. No exploitation is confirmed yet, but the severity is critical.

  1. Check whether you run PHP ext-date >= 8.2.0, and which version.
  2. Update to a patched version listed above, then confirm the new version.
  3. Until you can update, follow the vendor workaround: The fix formats error log timestamps in UTC outside a fully initialized active request, avoiding use of request-local timezone state at unsafe points in the lifecycle.
  4. Until you can update, follow the vendor workaround: Until an update can be deployed, correct configuration errors and deprecated settings that produce startup diagnostics, then restart the PHP master process and all workers. Sending PHP errors to a suitable logging destination that does not use this file-timestamp path, such as syslog, also avoids the demonstrated trigger. Changing $_REQUEST or cookie settings is not a complete mitigation. The demonstrated Apache cleanup path does not require those settings.

Timeline

  • Nov 19, 2026Published
  • Nov 19, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new PHP ext-date >= 8.2.0, CVEsYou are reading CVE-2026-129496. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

Data last checked: Nov 19, 2026 14:43 UTC