Thrift vulnerabilitiesRanked by how likely they are to be used.

Product17 versions
The short answer

Thrift is made by Apache. We track 7 published vulnerabilities in it, across 17 versions. None of them is on the list of flaws known to be exploited today. If you run Thrift, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Thrift vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Thrift's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Thrift flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 9.2%

    In Apache Thrift all versions up to and including 0.12.0, a server or client may run into an endless loop when feed with specific input data.

    CVSS7.5Published29 Oct 2019
  2. 8.2%

    Apache Thrift Java client library versions 0.5.0 through 0.11.0 can bypass SASL negotiation isComplete validation in the org.apache.thrift.transport.TSaslTransport class.

    CVSS7.5Published7 Jan 2019
  3. 6.9%

    The Apache Thrift Go client library exposed the potential during code generation for command injection due to using an external formatting tool.

    CVSS8.8Published12 Feb 2018
  4. 6.8%

    In Apache Thrift 0.9.3 to 0.13.0, malicious RPC clients could send short messages which would result in a large memory allocation, potentially leading to denial of service.

    CVSS7.5Published12 Feb 2021
  5. 6.5%

    In Apache Thrift 0.9.3 to 0.12.0, a server implemented in Go using TJSONProtocol or TSimpleJSONProtocol may panic when feed with invalid input data.

    CVSS7.5Published29 Oct 2019
  6. 5.3%

    The client libraries in Apache Thrift before 0.9.3 might allow remote authenticated users to cause a denial of service (infinite recursion) via vectors involving the skip function.

    CVSS6.5Published16 Jun 2017
  7. 4.9%

    The Apache Thrift Node.js static web server in versions 0.9.2 through 0.11.0 have been determined to contain a security vulnerability in which a remote user has the ability to access files outside the set webservers...

    CVSS6.5Published7 Jan 2019
  8. 1.1%

    Mismatched Memory Management Routines vulnerability in Apache Thrift c_glib language bindings.

    CVSS7.5Published28 Apr 2026
  9. 1.1%

    Improper Validation of Specified Quantity in Input, Out-of-bounds Read vulnerability in Apache Thrift C++ bindings.

    CVSS8.7Published27 Jul 2026
  10. 1.0%

    Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in Apache Thrift Python, Go, PHP and Java bindings.This issue affects Apache Thrift: before 0.24.0.

    CVSS8.7Published27 Jul 2026
Precursor Intelligence

Running Thrift? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 7 published vulnerabilities listed under the name Thrift, across 17 versions.

None of Thrift's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Thrift. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.