Skip to main content
VulnerabilityPublished Updated

CVE-2024-3829: Qdrant client · qdrant input validation failure

Affects qdrant-clientSource GCVE Database

0
Compare
Authoritative record:CVE-2024-3829· Critical 9.8

Not known to be exploited · CVSS 9.8 Critical : upgrade to 1.9.0 as a priority.

Data as of 16 Nov 2026, 17:50 UTC

CVSS 3.0 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.9.0
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Jun 2024

  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 15 Nov 2026.

What to do

Upgrade qdrant-client to 1.9.0.

Affected software

ProductAffectedFixed in
PyPIqdrant-clientAffected
  • <1.9.0
Fixed in
  • 1.9.0

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

AI-suggested

Upgrade qdrant to version 1.9.0 or later, where this vulnerability is fixed. No other mitigations are indicated by the vendor advisory.

Description

Qdrant client versions prior to 1.9.0 contain a vulnerability in the snapshot recovery process that allows attackers to read and write arbitrary files on the server by exploiting symlink manipulation. This can lead to a full system takeover. The vulnerability is fixed in version 1.9.0.

References

Community reviews

Loading reviews…