Authenticated remote code execution via arbitrary log path
Published Feb 6, 2026 · Updated Feb 6, 2026
External path control in Qdrant 1.9.3 through 1.15.5 allows remote authenticated users to execute code through the /logger endpoint. The POST /logger handler passes the on_disk.log_file value to the logging subsystem for append without constraining it to a log directory. Read-only API access is sufficient; a writable configuration directory and restart allow injected YAML to expose files, while writable loader paths enable code execution.
Summary
What happened
External path control in Qdrant 1.9.3 through 1.15.5 allows remote authenticated users to execute code through the /logger endpoint. The POST /logger handler passes the on_disk.log_file value to the logging subsystem for append without constraining it to a log directory. Read-only API access is sufficient; a writable configuration directory and restart allow injected YAML to expose files, while writable loader paths enable code execution.
The record
- CVE
- CVE-2026-25628
- Published
- Feb 6, 2026
- Updated
- Feb 6, 2026
- Vendor
- Qdrant
- Product
- Qdrant
- Classifications
- CWE-73, T1574.006
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 6, 2026CVE publishedPublication date reported by the CVE source.
- Feb 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.9.3, < 1.16.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- exploit_privesc.pyfunctional · demonstrated
- exploit_rce.pyfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo