# CVE-2026-25628: Qdrant affected by arbitrary file write via `/logger` endpoint

> An attacker with read-only access can append data to arbitrary files on the server via the /logger endpoint in Qdrant.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Feb 2026
- **Updated:** 6 Feb 2026
- **Also known as:** GHSA-f632-vm87-2m2f

## What is CVE-2026-25628?

CVE-2026-25628 is a high-severity path traversal vulnerability in qdrant, published on 6 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2026-25628?

2 open source packages ship an affected version, including qdrant. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `qdrant` | crates.io | From 1.9.3 | 1.15.6 |
| `qdrant` | crates.io | From 1.9.3 | 1.15.6 |

Products: Qdrant Qdrant.

## How do I fix CVE-2026-25628?

Upgrade qdrant to 1.15.6 or later.

## Is CVE-2026-25628 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25628 exists.

## Other vulnerabilities in qdrant

- [CVE-2024-3829](https://insights.sbomify.com/CVE-2024-3829/): Arbitrary File Read and Write during Snapshot Recovery in qdrant/qdrant (critical 9.8)
- [CVE-2024-3584](https://insights.sbomify.com/CVE-2024-3584/): Path Traversal in qdrant/qdrant (critical 9.8)
- [CVE-2024-2221](https://insights.sbomify.com/CVE-2024-2221/): Path Traversal and Arbitrary File Upload Vulnerability in qdrant/qdrant (critical 9.8)
- [CVE-2023-38975](https://insights.sbomify.com/CVE-2023-38975/): Memory corruption in n/a (high 7.5)
- [CVE-2024-3078](https://insights.sbomify.com/CVE-2024-3078/): Qdrant Full Snapshot REST API snapshots.rs path traversal (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25628 and fix it if it is affected.

What it is: CVE-2026-25628 is a high-severity path traversal vulnerability in qdrant, published on 6 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25628 exists.

Affected packages and fixed versions:
- qdrant (crates.io): affected from 1.9.3; fixed in 1.15.6
- qdrant (crates.io): affected from 1.9.3; fixed in 1.15.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25628/ (Markdown: https://insights.sbomify.com/CVE-2026-25628/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25628
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25628
- OSV: https://osv.dev/vulnerability/CVE-2026-25628

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25628/
Summaries are generated and may contain mistakes; the official description above is the record.