Mintplex-Labs anything-llm
AnythingLLM has key leak in `systemSettings.js`
AnythingLLM is an application that turns pieces of content into context that any LLM can use as references during chatting. If AnythingLLM prior to version 1.10.0 is configured to use Qdrant as the vector database with an API key, this QdrantApiKey could be exposed in plain text to unauthenticated users via the `/api/setup-complete` endpoint. Leakage of QdrantApiKey allows an unauthenticated attacker full read/write access to the Qdrant vector database instance used by AnythingLLM. Since Qdrant often stores the core knowledge base for RAG in AnythingLLM, this can lead to complete compromise of the semantic search / retrieval functionality and indirect leakage of confidential uploaded documents. Version 1.10.0 patches the issue.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.10.0
Fixed in 1.10.0
Mitigation
Upgrade anything-llm to 1.10.0 or later.
References
- Vendor advisory github.com/Mintplex-Labs/anything-llm/security…
Timeline
Days relative to CVE publicationFirst public PoC 49 days after publication; not in CISA KEV. First PoC: nuclei template: AnythingLLM - Information Disclosure (nuclei template, 17 Mar 2026).
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| nuclei template | nuclei template: AnythingLLM - Information Disclosure | 17 Mar 2026 | 14 Nov 2026 |