Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-f632-vm87-2m2f | qdrant has arbitrary file write via `/logger` endpoint |
Thu, 19 Feb 2026 18:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:qdrant:qdrant:*:*:*:*:*:*:*:* |
Mon, 09 Feb 2026 11:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Qdrant
Qdrant qdrant |
|
| Vendors & Products |
Qdrant
Qdrant qdrant |
Fri, 06 Feb 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 06 Feb 2026 21:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Qdrant affected by arbitrary file write via `/logger` endpoint | |
| Weaknesses | CWE-73 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-02-06T21:11:27.721Z
Reserved: 2026-02-04T05:15:41.789Z
Link: CVE-2026-25628
Updated: 2026-02-06T21:11:16.590Z
Status : Analyzed
Published: 2026-02-06T21:16:18.083
Modified: 2026-02-19T17:45:58.093
Link: CVE-2026-25628
No data.
OpenCVE Enrichment
Updated: 2026-04-17T22:30:29Z
Github GHSA