CVE-2026-94646

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

GHSA-pjxr-77cv-5rj7 ↗EUVD-2026-91563 ↗

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-341, permanent identifier
pkg:npm/thrift
18d 21h 13msince last run
18mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h47m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Apache Thrift Node.js bindings before version 0.25.0 improperly validate certain input, allowing prototype pollution or uncaught exceptions. An attacker who can provide the affected input may modify object prototype attributes or trigger an exception; no further precondition is stated.

mitigation

Upgrade Apache Thrift Node.js bindings to version 0.25.0 or later.

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.
–
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.46%38th percentile
agent run time
18m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 11:52Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-10-02 11:52Z
    ghsa: trigger signal, started the run
  2. 2026-10-02 11:52Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-341",
  "cve_id": "CVE-2026-94646",
  "display_id": "CVE-2026-94646",
  "ghsa_id": "GHSA-pjxr-77cv-5rj7",
  "euvd_id": "EUVD-2026-91563",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Prototype pollution in Apache Thrift Node.js bindings",
  "summary": "Apache Thrift Node.js bindings before version 0.25.0 improperly validate certain input, allowing prototype pollution or uncaught exceptions. An attacker who can provide the affected input may modify object prototype attributes or trigger an exception; no further precondition is stated.",
  "mitigation": "Upgrade Apache Thrift Node.js bindings 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": 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.0046,
  "epss_percentile": 0.3854,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 18.374109116666666,
  "t0_at": "2026-10-02T11:52:21.192000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-02T11:52:21.192000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T11:52:21.192000+00:00",
      "url": "https://github.com/advisories/GHSA-pjxr-77cv-5rj7"
    }
  }
}

published 2026-10-02 14:20Z
last change 2026-10-21 05:31Z

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.