# CVE-2026-24477: AnythingLLM has key leak in `systemSettings.js`

> Unauthenticated attackers can leak Qdrant API keys from the setup endpoint, gaining full read/write access to the vector database and confidential documents.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jan 2026
- **Updated:** 3 Apr 2026
- **Also known as:** GHSA-gm94-qc2p-xcwf

## What is CVE-2026-24477?

CVE-2026-24477 is a high-severity vulnerability in Mintplexlabs Anythingllm, published on 26 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

## Which versions are affected by CVE-2026-24477?

It affects 1 product.


Products: Mintplexlabs Anythingllm.

## How do I fix CVE-2026-24477?

No fix has been published for CVE-2026-24477 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-24477 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24477 exists.

Public exploit code:

- AnythingLLM - Information Disclosure (nuclei): http/cves/2026/CVE-2026-24477.yaml

## Other vulnerabilities in Mintplexlabs Anythingllm

- [CVE-2024-3025](https://insights.sbomify.com/CVE-2024-3025/): Path Traversal in mintplex-labs/anything-llm (critical 9.9)
- [CVE-2024-0455](https://insights.sbomify.com/CVE-2024-0455/): SSRF on AWS deployed instances of AnythingLLM via /metadata (critical 9.9)
- [CVE-2026-32626](https://insights.sbomify.com/CVE-2026-32626/): AnythingLLM has a Streaming Phase XSS to RCE via LLM Response Injection (critical 9.7)
- [CVE-2024-3104](https://insights.sbomify.com/CVE-2024-3104/): Remote Code Execution in mintplex-labs/anything-llm (critical 9.6)
- [CVE-2024-3149](https://insights.sbomify.com/CVE-2024-3149/): SSRF in mintplex-labs/anything-llm (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24477 and fix it if it is affected.

What it is: CVE-2026-24477 is a high-severity vulnerability in Mintplexlabs Anythingllm, published on 26 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24477 exists.

Affected product: Mintplexlabs Anythingllm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24477/ (Markdown: https://insights.sbomify.com/CVE-2026-24477/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24477
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24477
- OSV: https://osv.dev/vulnerability/CVE-2026-24477

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24477/
Summaries are generated and may contain mistakes; the official description above is the record.