VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

thrift: vulnerability history, versions and safety

thrift is a package in the Debian ecosystem. Vulert records 35 vulnerabilities for it across 29 releases, from Feb 2018 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
35 vulnerabilities recorded U35
i
27 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
26 in the last 12 months

Most recent disclosure 27 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all thrift vulnerabilities

Vulert verdict on thrift i

Updated on 23 Oct 2026

Careful: 27 of the 35 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 35 vulnerabilities on record across 8 years, 26 in the last year.

What to do: Plan around the 27 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 35 over 8 years · 26 in the last year i
  • Latest disclosure 27 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 27 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for thrift, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 29 of 29 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 2
  • 2019 6
  • 2021 1
  • 2026 26

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 26 of the 35 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for thrift

The 5 most severe of 35 vulnerabilities recorded for this package

Search all 35 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-based Buffer Overflow in Apache Thrift - Critical Vulnerability 9.8 critical No fix published 27 Jul 2026
Critical Out-of-Bounds Read Vulnerability in Apache Thrift Package 9.1 critical No fix published 27 Jul 2026
Critical Out-of-bounds Read Vulnerability in Apache Thrift Package 9.1 critical No fix published 27 Jul 2026
Critical Host Mismatch Vulnerability in Apache Thrift Package 9.1 critical No fix published 27 Jul 2026
Command Injection in Apache Thrift Go Client Library 8.8 high 0.11.0-3 12 Feb 2018

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About thrift

Is thrift safe to use?

Vulert records 35 vulnerabilities for thrift in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 35 not yet rated. 27 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does thrift have?

35 vulnerabilities are recorded for thrift in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 35 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new thrift vulnerabilities disclosed?

26 vulnerabilities were recorded for thrift in the last 12 months, and the oldest entry in this database dates to 12 Feb 2018. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of thrift are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor thrift for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the thrift version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.