CVE-2026-129496

validatedZero produced an exploit or a check.

GHSA-gr4f-wgx5-jpfv ↗EUVD-2026-130180 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+3h40mkevAttacks confirmed in the real world.
php:ext-date < 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
CWE-416 Use After Free
ETK-2026-4963Zero's internal tracking ID, independent of the CVE number., permanent identifier
+5h14mTTV
7mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0hpublic poc+3h40mcheck available+5h14magent stopped
0
+1h
+2h
+3h
+4h

description

Affected non-thread-safe PHP deployments can retain a dangling ext-date timezone-cache reference across startup and into a new worker's first request. An unauthenticated remote attacker may crash PHP-FPM, Apache mod_php, or CGI workers and could potentially execute code as the PHP worker when file-based PHP error logging and the required diagnostic conditions are present.

mitigation

Upgrade PHP to 8.2.36, 8.3.37, 8.4.28, or 8.5.13, as appropriate for the deployed branch. Until upgraded, eliminate startup configuration warnings, restart the PHP master and workers, and route PHP error logging away from the affected file-based timestamp path, such as to syslog.

fixed in 8.2.36, 8.3.37, 8.4.28, 8.5.13

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
7m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-19 14:43Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+3h40m
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-19 14:43Z
  2. 2026-11-19 14:43Z
  3. 2026-11-19 14:45Z
    PHP Fixes 7 Critical Flaws, Including Bugs That Could Allow Remote Code Execution
  4. 2026-11-19 16:28Z
  5. 2026-11-19 19:58Z

this entry in the feed

GET /api/v1/feed/CVE-2026-129496

{
  "etk_id": "ETK-2026-4963",
  "cve_id": "CVE-2026-129496",
  "display_id": "CVE-2026-129496",
  "ghsa_id": "GHSA-gr4f-wgx5-jpfv",
  "euvd_id": "EUVD-2026-130180",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Use-after-free in PHP ext-date timezone cache",
  "summary": "Affected non-thread-safe PHP deployments can retain a dangling ext-date timezone-cache reference across startup and into a new worker's first request. An unauthenticated remote attacker may crash PHP-FPM, Apache mod_php, or CGI workers and could potentially execute code as the PHP worker when file-based PHP error logging and the required diagnostic conditions are present.",
  "mitigation": "Upgrade PHP to 8.2.36, 8.3.37, 8.4.28, or 8.5.13, as appropriate for the deployed branch. Until upgraded, eliminate startup configuration warnings, restart the PHP master and workers, and route PHP error logging away from the affected file-based timestamp path, such as to syslog.",
  "vendor": "php",
  "product": "php:ext-date",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 8.2.36"
      ],
      "ecosystem": "php",
      "fixed_versions": [
        "8.2.36"
      ],
      "package_name": "ext-date",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 8.3.0, < 8.3.37"
      ],
      "ecosystem": "php",
      "fixed_versions": [
        "8.3.37"
      ],
      "package_name": "ext-date",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 8.4.0, < 8.4.28"
      ],
      "ecosystem": "php",
      "fixed_versions": [
        "8.4.28"
      ],
      "package_name": "ext-date",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 8.5.0, < 8.5.13"
      ],
      "ecosystem": "php",
      "fixed_versions": [
        "8.5.13"
      ],
      "package_name": "ext-date",
      "purl": null
    }
  ],
  "cwes": [
    416
  ],
  "cvss_score": 9.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "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",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 7.40912105,
  "t0_at": "2026-11-19T14:43:52.930000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-19T19:58:19.860416+00:00",
      "days": 0.21836725018518519,
      "is_lower_bound": false,
      "measured_at": "2026-11-19T14:43:52.930000+00:00",
      "url": null
    },
    "public_poc": {
      "at": "2026-11-19T18:23:30+00:00",
      "days": 0.15251238425925925,
      "is_lower_bound": false,
      "measured_at": "2026-11-19T14:43:52.930000+00:00",
      "url": "https://github.com/abraxas/php-tzcache-rce"
    },
    "trigger_signal": {
      "at": "2026-11-19T14:43:52.930000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-19T14:43:52.930000+00:00",
      "url": "https://github.com/php/php-src/security/advisories/GHSA-gr4f-wgx5-jpfv"
    }
  }
}

published 2026-11-19 19:50Z
last change 2026-11-20 05:43Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.