CVE-2026-63772

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

GHSA-h4r6-c5rr-jcwm ↗EUVD-2026-91628 ↗

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-616, permanent identifier
16d 02h 03msince last run
1h 46mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+63h12m
0
+2h
+4h
+6h
+8h
+10h

description

Apache Thrift Go bindings before 0.25.0 are affected by uncontrolled resource allocation. An unauthenticated remote attacker may crash a service that accepts attacker-controlled Thrift traffic using the affected bindings.

mitigation

Upgrade github.com/apache/thrift to version 0.25.0 or later. Restrict untrusted access to Thrift endpoints until the update is deployed.

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.43%35th percentile
agent run time
1h 46m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 12: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 12:52Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-616",
  "cve_id": "CVE-2026-63772",
  "display_id": "CVE-2026-63772",
  "ghsa_id": "GHSA-h4r6-c5rr-jcwm",
  "euvd_id": "EUVD-2026-91628",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Resource exhaustion in Apache Thrift Go bindings",
  "summary": "Apache Thrift Go bindings before 0.25.0 are affected by uncontrolled resource allocation. An unauthenticated remote attacker may crash a service that accepts attacker-controlled Thrift traffic using the affected bindings.",
  "mitigation": "Upgrade github.com/apache/thrift to version 0.25.0 or later. Restrict untrusted access to Thrift endpoints until the update is deployed.",
  "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": "github.com/apache/thrift",
      "purl": null
    }
  ],
  "cwes": [
    770
  ],
  "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": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 106.45006338333333,
  "t0_at": "2026-10-02T12:52:07.427000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-02T12:52:07.427000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T12:52:07.427000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-63772"
    }
  }
}

published 2026-10-05 02:17Z
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.