Qdrant
Newest record 2026-02-06 · 7 distinct CVE ids · open in the explorer (the explorer matches the first product a record names, so it can list fewer)
Exploited or KEV-listed · 0
Records at severity 3–4 (exploitation confirmed by CISA, the vendor or reporting) and records flagged as listed in CISA KEV. The KEV flag is the classifier’s cisa-kev tag or a source on the KEV catalog; it is recorded when the collector sees the listing, so a missing flag does not mean a CVE is absent from the catalog.
No record for Qdrant has confirmed exploitation or a KEV flag.
Disclosures by month · last 24 months
Disclosed CVEs, no confirmed exploitation · 7
- closed8.5Qdrant CVE-2026-25628: Qdrant Arbitrary File Append Vulnerability
Disclosed · since 6 Feb 2026 · CVE-2026-25628
AI - closed8.7AnythingLLM CVE-2026-24477: AnythingLLM API Key Exposure Vulnerability
Disclosed · since 27 Jan 2026 · CVE-2026-24477
AI - closed9.8Qdrant CVE-2024-3829: Input validation failure in Qdrant snapshot recovery
Disclosed · since 3 Jun 2024 · CVE-2024-3829
AI - closed9.8Qdrant CVE-2024-3584: Qdrant Vector Database Path Traversal Vulnerability
Disclosed · since 30 May 2024 · CVE-2024-3584
AI - closed9.8Qdrant CVE-2024-2221: Qdrant Path Traversal and Arbitrary File Upload
Disclosed · since 10 Apr 2024 · CVE-2024-2221
AI - closed5.5Qdrant CVE-2024-3078: Qdrant Full Snapshot REST API Path Traversal
Disclosed · since 29 Mar 2024 · CVE-2024-3078
AI - closed7.5Qdrant CVE-2023-38975: Qdrant Buffer Overflow Vulnerability
Disclosed · since 29 Aug 2023 · CVE-2023-38975
AI
Fix status and fixed versions are recorded when a source states them (each record’s page shows what is known); check the vendor’s own advisory before acting.