CVE-2026-25628: Qdrant is a vector similarity search engine and vector database

This month

HIGH 8.5UPGRADE

CVE-2026-25628 is a high-severity flaw (CVSS 8.5) affecting qdrant. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Qdrant is a vector similarity search engine and vector database. From 1.9.3 to before 1.16.0, it is possible to append to arbitrary files via /logger endpoint using an attacker-controlled on_disk.log_file path. Minimal privileges are required (read-only access). This vulnerability is fixed in 1.16.0.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.5 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.6% (top 54%)
CISA exploited list	No
Weakness	CWE-73
Published	2026-02-06
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: qdrant

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-02-06 21:16 UTCPublished CVE record published
2026-06-17 10:24 UTCUpdated Record last modified

qdrant qdrant UPGRADE

Affected: >= 1.9.3 and <= 1.16.0

Fixed in: newer than 1.16.0

Safe to downgrade to: a release before 1.9.3

1. Check installed version

apt-cache policy qdrant || rpm -q qdrant || qdrant --version

2. UPGRADE to newer than 1.16.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade qdrant

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade qdrant

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.9.3 (Debian / Ubuntu)

apt-cache madison qdrant sudo apt install qdrant=<VERSION_BEFORE_1.9.3> sudo apt-mark hold qdrant

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list qdrant sudo dnf downgrade qdrant-<VERSION_BEFORE_1.9.3> sudo dnf versionlock add qdrant

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-25628?

qdrant: upgrade to newer than 1.16.0. Exact commands for each OS are on this page.

Is CVE-2026-25628 being exploited?

CVE-2026-25628 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-25628 affect?

CVE-2026-25628 affects qdrant. Severity is high (CVSS 8.5). Qdrant is a vector similarity search engine and vector database. From 1.9.3 to before 1.16.0, it is possible to append to arbitrary files via /logger endpoint using an attacker-controlled on_disk.log_file path. Minimal privileges are requir

How urgent is CVE-2026-25628?

Priority 46/100. High severity; Public exploit reference

Related CVEs

CVE-2024-3829 CRITICAL 9.1 UPGRADE qdrant/qdrant version 1.9.0-dev is vulnerable to arbitrary file read and write during the snapshot recovery pr
CVE-2024-3584 HIGH 7.5 UPGRADE qdrant/qdrant version 1.9.0-dev is vulnerable to path traversal due to improper input validation in the `/coll
CVE-2024-3078 MEDIUM 5.5 UPGRADE A vulnerability was found in Qdrant up to 1.6.1/1.7.4/1.8.2 and classified as critical
CVE-2024-2221 CRITICAL 9.8 DOWNGRADE qdrant/qdrant is vulnerable to a path traversal and arbitrary file upload vulnerability via the `/collections/

References

← Back to latest CVEs