CVE-2026-83632

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

GHSA-ffqv-2x6m-g28r ↗EUVD-2026-91583 ↗

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-615, permanent identifier
16d 03h 14msince 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+62h09m
0
+2h
+4h
+6h
+8h
+10h

description

Apache Thrift versions earlier than 0.25.0 are affected by resource-allocation and integer-handling flaws that can result in heap buffer overflow conditions. An attacker able to reach the affected processing path may trigger these conditions; the advisory does not state a more specific access precondition.

mitigation

Upgrade Apache Thrift 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.38%30th percentile
agent run time
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 12:22Z
Δ 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:22Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-615",
  "cve_id": "CVE-2026-83632",
  "display_id": "CVE-2026-83632",
  "ghsa_id": "GHSA-ffqv-2x6m-g28r",
  "euvd_id": "EUVD-2026-91583",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Resource allocation and heap buffer overflow in Apache Thrift",
  "summary": "Apache Thrift versions earlier than 0.25.0 are affected by resource-allocation and integer-handling flaws that can result in heap buffer overflow conditions. An attacker able to reach the affected processing path may trigger these conditions; the advisory does not state a more specific access precondition.",
  "mitigation": "Upgrade Apache Thrift to version 0.25.0 or later.",
  "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": "thrift",
      "purl": null
    }
  ],
  "cwes": [
    770
  ],
  "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": 0.0038,
  "epss_percentile": 0.303,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 13.717337666666667,
  "t0_at": "2026-10-02T12:22:23.617000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-02T12:22:23.617000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T12:22:23.617000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-83632"
    }
  }
}

published 2026-10-05 02:17Z
last change 2026-10-21 04:45Z

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.