CVE-2026-66837

waiting for further signalsZero needs more public information before it can validate it.

GHSA-fvvf-6w23-6h87 ↗EUVD-2026-91586 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Apache Software Foundation Apache Thrift < 0.25.0
fixed in 0.25.0
ETK-2026-352, permanent identifier
18d 23h 33msince last run
17mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+4h54m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Apache Thrift PHP bindings before version 0.25.0 are affected by integer-wraparound and stack-based buffer-overflow flaws. The available advisory does not state the attacker impact or the conditions required to trigger the issue.

mitigation

Upgrade the apache/thrift package to version 0.25.0 or later. Identify and replace deployments using earlier releases of the PHP bindings.

fixed in 0.25.0

check
no
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.
0.29%20th percentile
agent run time
17m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 12:29Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, 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-10-02 12:29Z
    ghsa: trigger signal, started the run
  2. 2026-10-02 12:29Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-352",
  "cve_id": "CVE-2026-66837",
  "display_id": "CVE-2026-66837",
  "ghsa_id": "GHSA-fvvf-6w23-6h87",
  "euvd_id": "EUVD-2026-91586",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Integer and stack buffer overflows in Apache Thrift PHP bindings",
  "summary": "Apache Thrift PHP bindings before version 0.25.0 are affected by integer-wraparound and stack-based buffer-overflow flaws. The available advisory does not state the attacker impact or the conditions required to trigger the issue.",
  "mitigation": "Upgrade the apache/thrift package to version 0.25.0 or later. Identify and replace deployments using earlier releases of the PHP bindings.",
  "vendor": "Apache Software Foundation",
  "product": "Apache Thrift",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 0.25.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "0.25.0"
      ],
      "package_name": "apache/thrift",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
  "epss_score": 0.0029,
  "epss_percentile": 0.2031,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 17.43475511666667,
  "t0_at": "2026-10-02T12:29:09.189000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-02T12:29:09.189000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T12:29:09.189000+00:00",
      "url": "https://github.com/advisories/GHSA-fvvf-6w23-6h87"
    }
  }
}

published 2026-10-02 16:23Z
last change 2026-10-21 16:15Z

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.