CVE-2026-94634

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

GHSA-2gpw-mvhv-qq99 ↗EUVD-2026-91364 ↗

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
CWE-770 Allocation of Resources Without Limits or Throttling
ETK-2026-332, permanent identifier
pkg:pypi/thrift
19d 01h 07msince last run
14mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+5h20m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Apache Thrift Python bindings before version 0.25.0 are affected by resource handling without adequate limits and an unsafe default. An attacker may be able to cause excessive resource consumption. The advisory does not specify the attacker precondition or affected request path.

mitigation

Upgrade the PyPI thrift package 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.
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
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 10:11Z
Δ 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 10:11Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-332",
  "cve_id": "CVE-2026-94634",
  "display_id": "CVE-2026-94634",
  "ghsa_id": "GHSA-2gpw-mvhv-qq99",
  "euvd_id": "EUVD-2026-91364",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Resource exhaustion in Apache Thrift Python bindings",
  "summary": "Apache Thrift Python bindings before version 0.25.0 are affected by resource handling without adequate limits and an unsafe default. An attacker may be able to cause excessive resource consumption. The advisory does not specify the attacker precondition or affected request path.",
  "mitigation": "Upgrade the PyPI 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": "pypi",
      "fixed_versions": [
        "0.25.0"
      ],
      "package_name": "thrift",
      "purl": "pkg:pypi/thrift"
    }
  ],
  "cwes": [
    770
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0043,
  "epss_percentile": 0.3552,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 14.078243916666667,
  "t0_at": "2026-10-02T10:11:20.762000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-02T10:11:20.762000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T10:11:20.762000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-94634"
    }
  }
}

published 2026-10-02 11:42Z
last change 2026-10-21 15:37Z

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.