CVE-2026-24477: AnythingLLM API Key Exposure Vulnerability
AnythingLLM, Qdrant
AnythingLLM before version 1.10.0 exposes the Qdrant API key in plain text via an unauthenticated endpoint. This vulnerability allows attackers to gain full read and write access to the underlying vector database.
disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why
- CVSS
- 8.7
- EPSS
- 0.02 · top 18% · 2026-11-13
- fix status
- Fix status unknown
- first report
- 27 Jan 2026
- last update
- 27 Jan 2026
- CVE ids
Timeline · 1
Sources · 1
Advisories and databases
- 2026-01-27CVE-2026-24477: AnythingLLM is an application that turns pieces of content into context that any LLM can use as references during chatting.NVD · nvd.nist.gov/vuln/detail/CVE-2026-24477
Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.
Classification
- lane
- Patch now
- AI role
- Attack on AI
- categories
- Infrastructure vulnerabilityData leak
- severity
- 2 · Disclosed vulnerability
- fix status
- Fix status unknown
- targets
- Framework / tooling
- mitre atlas
- no technique for these categories
- dates
- happened 27 Jan 2026 · first reported 27 Jan 2026
- origin
- NVDVulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- record
- confidence 0.95 · created 2026-10-18 10:04Z · updated 2026-10-18 10:04Z
Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned
Copy a brief
This record as a short Markdown brief, for a ticket, a chat or a coding agent.
the brief as text
# CVE-2026-24477: AnythingLLM API Key Exposure Vulnerability https://gcdradar.vercel.app/incidents/cve-2026-24477-anythingllm-api-key-exposure-vulnerability · AIR-2026-0952 · closed 2026-01-27 - Lane: Patch now - Severity: 2 (Disclosed vulnerability) - Fix status: Fix status unknown - First reported: 2026-01-27 - AI role: Attack on AI - Products: AnythingLLM, Qdrant - CVE ids: CVE-2026-24477 - CVSS: 8.7 ## Summary AnythingLLM before version 1.10.0 exposes the Qdrant API key in plain text via an unauthenticated endpoint. This vulnerability allows attackers to gain full read and write access to the underlying vector database. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2026-01-27: CVE-2026-24477: AnythingLLM is an application that turns pieces of content into context that any LLM can use as references during chatting. (https://nvd.nist.gov/vuln/detail/CVE-2026-24477) ## Sources - 2026-01-27 NVD: CVE-2026-24477: AnythingLLM is an application that turns pieces of content into context that any LLM can use as references during chatting. https://nvd.nist.gov/vuln/detail/CVE-2026-24477 Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closed4.3AnythingLLM AnythingLLM Authentication Flaw Permits Unauthorized Workspace Access
Patch now · Disclosed · since 28 May 2026 · CVE-2026-47713
AI - closed4.3AnythingLLM CVE-2026-42456: Insecure direct object reference in AnythingLLM tts endpoint
Patch now · Disclosed · since 8 May 2026 · CVE-2026-42456
AI - closed8.7MCP servers & tools CVE-2026-25650: MCP Salesforce Connector Auth Token Disclosure Vulnerability
Patch now · Disclosed · since 6 Feb 2026 · CVE-2026-25650
AI - closed7.1MCP SDKs CVE-2026-25536: Model Context Protocol SDK cross-client data leak
Patch now · Disclosed · since 4 Feb 2026 · CVE-2026-25536
AI - closed5.3Claude Code + SDKs CVE-2026-21852: Claude Code Data Leak via Malicious Config
Patch now · Disclosed · since 21 Jan 2026 · CVE-2026-21852
AI - closed8.4Dify CVE-2025-67732: API Key Exposure Vulnerability in Dify
Patch now · Disclosed · since 5 Jan 2026 · CVE-2025-67732
AI