Unauthenticated Qdrant key disclosure via unmasked settings
Published Jan 26, 2026 · Updated Jan 26, 2026
Information disclosure in Mintplex Labs AnythingLLM before 1.10.0 allows remote attackers to read a Qdrant API key without authentication. The /api/setup-complete handler serializes QdrantApiKey from systemSettings.js without the masking conditional applied to other secrets. Exposure requires Qdrant to be selected with an API key; the key grants read/write access to vectors and metadata, enabling document disclosure or collection corruption.
Summary
What happened
Information disclosure in Mintplex Labs AnythingLLM before 1.10.0 allows remote attackers to read a Qdrant API key without authentication. The /api/setup-complete handler serializes QdrantApiKey from systemSettings.js without the masking conditional applied to other secrets. Exposure requires Qdrant to be selected with an API key; the key grants read/write access to vectors and metadata, enabling document disclosure or collection corruption.
The record
- CVE
- CVE-2026-24477
- Published
- Jan 26, 2026
- Updated
- Jan 26, 2026
- Vendor
- Mintplex Labs
- Product
- AnythingLLM
- Classifications
- CWE-201, T1552
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 26, 2026CVE publishedPublication date reported by the CVE source.
- Jan 26, 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.10.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Unauthenticated setup-complete curl proof of conceptproof of concept · 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