CVE-2026-96294

validatedZero produced an exploit or a check.

GHSA-q62p-j25r-fc4c ↗EUVD-2026-91411 ↗

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).kevAttacks confirmed in the real world.
Apache Software Foundation Apache Thrift < 0.25.0
fixed in 0.25.0
CWE-248 Uncaught Exception
ETK-2026-477, permanent identifier
pkg:npm/thrift
+1.3dTTV
37mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+31h21magent stopped
0
+6h
+12h
+18h
+24h

description

The npm thrift package is affected before version 0.25.0. An attacker may be able to cause an uncaught exception; the advisory does not specify the trigger or required preconditions.

mitigation

Upgrade the npm thrift package to version 0.25.0 or later.

fixed in 0.25.0

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.
0.43%35th percentile
agent run time
37m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 11:09Z
Δ 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 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-10-02 11:09Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-477",
  "cve_id": "CVE-2026-96294",
  "display_id": "CVE-2026-96294",
  "ghsa_id": "GHSA-q62p-j25r-fc4c",
  "euvd_id": "EUVD-2026-91411",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unhandled exception handling in Apache Thrift Node.js bindings",
  "summary": "The npm thrift package is affected before version 0.25.0. An attacker may be able to cause an uncaught exception; the advisory does not specify the trigger or required preconditions.",
  "mitigation": "Upgrade the npm thrift package to version 0.25.0 or later.",
  "vendor": "Apache Software Foundation",
  "product": "Apache Thrift",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 0.25.0"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "0.25.0"
      ],
      "package_name": "thrift",
      "purl": "pkg:npm/thrift"
    }
  ],
  "cwes": [
    248
  ],
  "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",
  "epss_score": 0.0043,
  "epss_percentile": 0.3551,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 36.55000018333333,
  "t0_at": "2026-10-02T11:09:56.230000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-03T18:30:50.519198+00:00",
      "days": 1.3061839027546296,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T11:09:56.230000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-02T11:09:56.230000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T11:09:56.230000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-96294"
    }
  }
}

published 2026-10-03 17:54Z
last change 2026-10-21 13:29Z

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.