CVE-2026-25628

8.5

Qdrant · Qdrant

Qdrant versions 1.9.3 through 1.15.5 allow authenticated users with read-only access to perform arbitrary file appends via the /logger endpoint.

Executive summary

A vulnerability in the Qdrant vector database allows authenticated users to append data to arbitrary files, potentially leading to unauthorized system changes or escalation.

Vulnerability

The flaw is categorized as CWE-73, involving improper control of file names or paths within the /logger endpoint. An attacker with minimal read-only privileges can manipulate the on_disk.log_file parameter to append content to files outside the intended log directory.

Business impact

The ability to append content to arbitrary files on the host system creates a critical security risk, as it may allow for the corruption of configuration files, the injection of malicious scripts, or the alteration of system logs to hide unauthorized activity. Given the CVSS score of 8.5, this vulnerability represents a high risk to data integrity and system availability, especially in environments where the Qdrant instance is exposed to network-accessible users.

Remediation

Immediate Action: Update Qdrant to version 1.16.0 or the backported version 1.15.6 immediately to resolve the path validation flaw.

Proactive Monitoring: Monitor server access logs for unusual requests directed at the /logger endpoint and audit the file system for unexpected modifications to critical configuration files.

Compensating Controls: Implement strict network access control lists to limit access to the Qdrant API to trusted IP addresses and utilize a Web Application Firewall to block requests containing directory traversal sequences in parameters.

Exploitation status

Public Exploit Available: Unknown (No weaponized exploit or public proof-of-concept repository identified; CISA SSVC assessment notes a PoC exists, which refers to the researcher's technical write-up).

Analyst recommendation

The severity of this issue necessitates immediate attention. Organizations utilizing Qdrant must verify their current version and apply the provided patch to prevent unauthorized file system manipulation. Given that this vulnerability can be triggered by authenticated users with low-level privileges, restricting administrative or API access remains a vital secondary defense while the update is deployed.

Sources