CVE-2026-120135

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

GHSA-663r-q6wf-5j93 ↗EUVD-2026-114735 ↗

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.24.0
fixed in 0.24.0
CWE-674 Uncontrolled Recursion
ETK-2026-3198Zero's internal tracking ID, independent of the CVE number., permanent identifier
5h 02msince last run
20mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h07m
0
+4h
+6h
+8h
+10h
+12h

description

Apache Thrift's Java libthrift artifact is affected in versions before 0.24.0. An attacker may cause unbounded recursive processing in an affected application. The advisory does not specify the input or deployment preconditions required to trigger the issue.

mitigation

Upgrade org.apache.thrift:libthrift to version 0.24.0 or later. Prioritize updates for applications that process untrusted data.

fixed in 0.24.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.
–
agent run time
20m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-31 20:33Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-10-31 20:33Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3198",
  "cve_id": "CVE-2026-120135",
  "display_id": "CVE-2026-120135",
  "ghsa_id": "GHSA-663r-q6wf-5j93",
  "euvd_id": "EUVD-2026-114735",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Uncontrolled recursion in Apache Thrift Java bindings",
  "summary": "Apache Thrift's Java libthrift artifact is affected in versions before 0.24.0. An attacker may cause unbounded recursive processing in an affected application. The advisory does not specify the input or deployment preconditions required to trigger the issue.",
  "mitigation": "Upgrade org.apache.thrift:libthrift to version 0.24.0 or later. Prioritize updates for applications that process untrusted data.",
  "vendor": "Apache Software Foundation",
  "product": "Apache Thrift",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 0.24.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "0.24.0"
      ],
      "package_name": "org.apache.thrift:libthrift",
      "purl": null
    }
  ],
  "cwes": [
    674
  ],
  "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": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 19.99335605,
  "t0_at": "2026-10-31T20:33:00.088000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-31T20:33:00.088000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-31T20:33:00.088000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-120135"
    }
  }
}

published 2026-10-31 20:59Z
last change 2026-11-01 03:14Z

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.