qdrant has arbitrary file write via `/logger` endpoint
CVE-2026-25628 · GHSA-f632-vm87-2m2f · published 2026-02-05 · updated 2026-02-06
- Severity
- High
- CVSS score
- 8.5
- Chance of exploitation (EPSS)
- 0.54%
- Fixed in
- 1.15.6
- Exploitation Public proof of concept
- Automatable No
- Technical impact Total
- CISA SSVC
Remote code execution.
Upgrade qdrant to 1.15.6 or later.
1. Limit usage of /logger endpoint to users with management privileges only (or better disable it completely). 2. Restrict the path of the log file to a dedicated logs directory. This vulnerability does not affect Qdrant cloud as the configuration directory is not writable.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| qdrant | crates.io | >= 1.9.3, < 1.15.6 | 1.15.6 |
- CriticalMCP Path Traversal Allows Full-Filesystem Read and JWT Secret Exfiltration Leading to Account Takeoverlangflow, langflow-base
- Critical@zereight/mcp-gitlab: Unauthenticated arbitrary file read via `upload_markdown` enables PAT exfiltration and full account takeover@zereight/mcp-gitlab
- CriticalFlowise RCE via SQL Database Chain Nodeflowise, flowise-components
- CriticalLangroid: SQLChatAgent dangerous-function blocklist can be bypassed with quoted or schema-qualified pg_read_file callslangroid
- Criticalfast-mcp-telegram: Bearer token path traversal bypasses reserved Telegram session protectionfast-mcp-telegram
- CriticalMCP Toolbox HTTP tool path parameters allow traversal to unintended endpointsgithub.com/googleapis/mcp-toolbox
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.