Skip to main content
VulnerabilityPublished

CVE-2026-120135: Apache Thrift · Java TProtocolUtil.skip() does not limit the recursion depth by default

Affects thriftSource GCVE Database

0
Compare
Authoritative record:CVE-2026-120135· High 8.2

Not known to be exploited · CVSS 8.2 High : upgrade to 0.24.0 soon.

Data as of 17 Nov 2026, 16:06 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (apache)CVSS 4.08.2
Patch
Available – fixed in 0.24.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade thrift to 0.24.0.

Affected software

ProductAffectedFixed in
Bitnamithriftpkg:bitnami/thriftOther threatsAffected
  • <0.24.0
Fixed in
  • 0.24.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Apache Thrift to version 0.24.0 or later, where the recursion depth limitation has been implemented to fix this vulnerability. Since a patch is available, applying this official fix is the recommended mitigation.

Description

Apache Thrift Java bindings before version 0.24.0 contain an uncontrolled recursion vulnerability in the TProtocolUtil.skip() method. This flaw allows recursion depth to be unbounded, potentially leading to resource exhaustion or denial of service. The issue is fixed in version 0.24.0, and users are advised to upgrade to this version to mitigate the risk.

References

Community reviews

Loading reviews…