Qdrant up to 1.15.x /logger on_disk.log_file file inclusion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Qdrant up to 1.15.x. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the file /logger. The manipulation of the argument on_disk.log_file results in file inclusion. This vulnerability is cataloged as CVE-2026-25628. The attack may be launched remotely. There is no exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in Qdrant up to 1.15.x. Affected is some unknown processing of the file /logger. The manipulation of the argument on_disk.log_file with an unknown input leads to a file inclusion vulnerability. CWE is classifying the issue as CWE-73. The product allows user input to control or influence paths or file names that are used in filesystem operations. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is shared for download at github.com. This vulnerability is traded as CVE-2026-25628 since 02/04/2026. The exploitability is told to be difficult. It is possible to launch the attack remotely. There are known technical details, but no exploit is available.
Upgrading to version 1.16.0 eliminates this vulnerability. Applying the patch 32b7fdfb7f542624ecd1f7c8d3e2b13c4e36a2c1 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-5567). VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Name
Version
License
Website
- Product: https://github.com/qdrant/qdrant/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.4
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔒
CNA Base Score: 8.5
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: File inclusionCWE: CWE-73
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Qdrant 1.16.0
Patch: 32b7fdfb7f542624ecd1f7c8d3e2b13c4e36a2c1
Timeline
02/04/2026 CVE reserved02/06/2026 Advisory disclosed
02/06/2026 VulDB entry created
02/19/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-f632-vm87-2m2f
Status: Confirmed
CVE: CVE-2026-25628 (🔒)
GCVE (CVE): GCVE-0-2026-25628
GCVE (VulDB): GCVE-100-344784
EUVD: 🔒
Entry
Created: 02/06/2026 22:25Updated: 02/19/2026 20:14
Changes: 02/06/2026 22:25 (66), 02/07/2026 06:41 (1), 02/19/2026 20:14 (11)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.