VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

qdrant: vulnerability history, versions and safety

qdrant is a package in the crates.io ecosystem. Vulert records 2 vulnerabilities for it across 0 release, from Jun 2024 to Feb 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C1 H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 05 Feb 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all qdrant vulnerabilities

Vulert verdict on qdrant 0.0.0 i

Updated on 23 Oct 2026

Good news: 0.0.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 69/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Active

What to do: Stay on 0.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 0.0.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 1 in the last year i
  • Latest disclosure 05 Feb 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 35,109 i
  • Last release 30 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by crates.io, refreshed 23 Oct 2026. Licence information is not legal advice.

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 tracks for qdrant, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.0.0 18 Apr 2024 none Apache-2.0 — Details →

All 1 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for qdrant

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-3584: Path Traversal Vulnerability in qdrant 9.8 critical 1.9.0 02 Jun 2024
CVE-2026-25628: Qdrant Arbitrary File Write Vulnerability via Logger Endpoint 8.5 high 1.15.6 05 Feb 2026

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 qdrant

Is qdrant safe to use?

Vulert records 2 vulnerabilities for qdrant in crates.io: 1 critical, 1 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is qdrant's Vulert package health score?

Vulert scores qdrant 69/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of qdrant affected?

No. 0.0.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of qdrant should I use?

0.0.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does qdrant have?

2 vulnerabilities are recorded for qdrant in the crates.io ecosystem: 1 critical, 1 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new qdrant vulnerabilities disclosed?

1 vulnerability was recorded for qdrant in the last 12 months, and the oldest entry in this database dates to 02 Jun 2024. 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 qdrant 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 qdrant for upcoming vulnerabilities?

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