Skip to main content

Qdrant CVE-2026-25628

HIGH
External Control of File Name or Path (CWE-73)
2026-02-06 security-advisories@github.com GHSA-f632-vm87-2m2f
8.5
CVSS 3.1 · GitHub Advisory
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate with read-only Qdrant account
  2. Delivery
    Send POST to /logger endpoint
  3. Exploit
    Craft malicious on_disk.log_file path parameter
  4. Execution
    Append arbitrary data to target file
  5. Impact
    Compromise system integrity

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File name/path control
Exploitation Conditions

Qdrant versions 1.9.3 through 1.15.x with /logger endpoint enabled. Attacker requires valid read-only user credentials. Target file must be writable by Qdrant process. Cross-compartment impact requires shared filesystem or application dependency on modified files.

Impact

CVSS 8.5 (HIGH). Attack vector: Network. Complexity: High. Privileges required: Low. User interaction: None. Public exploit/POC available.

Exploit ScenarioDerived

An attacker could exploit this vulnerability to compromise the affected system.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

Arbitrary file append vulnerability in Qdrant vector database versions 1.9.3 through 1.15.x allows authenticated users with minimal read-only privileges to write to arbitrary files through an unsanitized log file path parameter in the /logger endpoint. Public exploit code exists for this vulnerability, enabling attackers to corrupt system files or inject malicious content with high impact to confidentiality, integrity, and availability. The issue is resolved in version 1.16.0.

Earlier versions of this analysis (1)
v1 Mar 12, 2026 - 21:54 CVSS 8.5

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. [CVSS 8.5 HIGH]

RemediationAI

A vendor patch is available — apply it immediately. Fixed in version 1.16.0.. Restrict network access to the affected service where possible.

Affected Packages

cargo qdrant fix: 1.15.6

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in cargo

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Affects Qdrant. 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.

Know when Qdrant gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 8.5 HIGH
AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector
Network
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
PoC Detected
Feb 19, 2026 - 17:45 vuln.today
Public exploit code
Patch released
Feb 19, 2026 - 17:45 nvd
Patch available
CVE Published
Feb 06, 2026 - 21:16 nvd
HIGH 8.5

DescriptionGitHub Advisory

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.

Executive ViewAI

Why It Matters

Qdrant vector database installations (versions 1.9.3-1.15.x) are vulnerable to arbitrary file write attacks through an exposed logging endpoint, potentially allowing attackers to corrupt critical system files or inject malicious content. Organizations using affected Qdrant versions in production environments face immediate risk of data manipulation, system compromise, and operational disruption.

Business Impact: High
Compensating Controls

Apply vendor patch. Until patching is complete: (1) Implement WAF rules to block POST/PUT requests to /logger endpoint, (2) Network segmentation to restrict /logger endpoint access to trusted internal sources only, (3) Disable Qdrant logging feature if not critical to operations, (4) Enable detailed audit logging on the Qdrant host filesystem to detect unauthorized file writes.

Threat Intelligence Overview

EPSS Score
0.0%
Top 95% exploitable
Exploit
POC
Public exploit code exists
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

62
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Affected Products (CPE)GitHub Advisory

cpe:2.3:a:qdrant:qdrant:*:*:*:*:*:*:*:*

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy