qdrant has arbitrary file write via /logger endpoint

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.5 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

EPSS

• CVE-2026-25628: 0.54% estimated exploitation activity in the next 30 days; percentile 45.68 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary It is possible to append to arbitrary files via /logger endpoint. Minimal privileges are required (read-only access). Tested on Qdrant 1.15.5 Details POST /logger (Source code link) endpoint accepts an attacker-controlled ondisk.logfile path. There are no authorization checks (but authentication check is present). This can be exploited in the following way: if configuration directory is writable and config/local.yaml does not exist, set log path to config/local.yaml and send a request with a log injection payload. ThePATCH /collections endpoint was used with an invalid collection name to inject valid yaml. After running the PoC, the content of config/local.yaml will be: Some junk log lines are present, but they don't matter as this is still valid yaml. After that, if qdrant is restarted (via legitimate means or by a OOM/crash), then local.yaml config will have higher priority and service.staticcontentdir will be set to ... In a container environment, this allows one to read…

Published by the source

5 Feb 2026, 21:22 UTC

Last modified by the source

6 Feb 2026, 21:44 UTC

Source last checked

26 Oct 2026, 15:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-f632-vm87-2m2f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-25628

Advisory: qdrant has arbitrary file write via `/logger` endpoint
IDs: CVE-2026-25628, GHSA-f632-vm87-2m2f
Record: https://patchnext.com/advisories/cve-2026-25628 (revision 1, source checked 26 Oct 2026, 15:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: qdrant 1.15.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io qdrant: affected >= 1.9.3, < 1.15.6; fixed in 1.15.6

## Suggested inspection (read-only)
- crates.io qdrant: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on qdrant.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-f632-vm87-2m2f (GitHub-reviewed advisory GHSA-f632-vm87-2m2f lists affected ranges: crates.io qdrant >=1.9.3 <1.15.6)

Commands are suggestions: review each one before running it.