# CVE-2026-24477: AnythingLLM - Credentials Disclosure

> Live exploitation tracking for CVE-2026-24477 by the CrowdSec Live Exploit Tracker, built from real-world attack data crowdsourced from CrowdSec's global network.

Page: https://tracker.crowdsec.net/cves/CVE-2026-24477

## Key facts

- **Exploitation phase:** Background Noise. Continuous low-level scanning or exploitation attempts are observed, mostly opportunistic and automated.
- **CVSS score:** 8.7
- **Public exploit available:** Yes
- **Affected products:** Mintplex-Labs AnythingLLM
- **Weaknesses:** CWE-201 (Insertion of Sensitive Information Into Sent Data)
- **Tags:** web_application, ai_mcp

## 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.

## CrowdSec analysis

[CVE-2026-24477](https://euvd.enisa.europa.eu/vulnerability/CVE-2026-24477) is a high-severity vulnerability in AnythingLLM prior to version 1.10.0, where the Qdrant API key could be exposed in plain text to unauthenticated users via the /api/setup-complete endpoint. This flaw allows attackers to gain full read and write access to the Qdrant vector database, potentially compromising the application's core knowledge base and leading to the leakage of confidential documents. Exploitation of this vulnerability could result in unauthorized access to sensitive data and disruption of semantic search and retrieval functionalities.

CrowdSec has been tracking this vulnerability and its exploits since 1st of April 2026.

According to CrowdSec data, while opportunistic exploitation dominates, a portion of threat actors trying to exploit CVE-2026-24477 apply basic targeting methods such as port or service detection. This indicates emerging patterns of selective targeting.
CrowdSec data also reveals a clear uptick in attacks involving CVE-2026-24477 over the past week. Activity is above the usual baseline, suggesting growing attention from attackers. This may reflect rising awareness, recent exploit releases, or expanded targeting efforts.

Attackers exploit the `/api/setup-complete` endpoint to retrieve sensitive configuration data, including the `QdrantApiKey`, which can lead to unauthorized access and compromise of the Qdrant vector database.

## Timeline

- 2026-01-26: CVE Published. CVE-2026-24477 is published to NVD.
- 2026-04-01: Rule Released. CrowdSec releases a rule to detect CVE-2026-24477 exploitation attempts against the CrowdSec Network.
- 2026-04-01: CrowdSec First Seen. CrowdSec observes in-the-wild exploitation of CVE-2026-24477 for the first time.

## References

- https://github.com/Mintplex-Labs/anything-llm/security/advisories/GHSA-gm94-qc2p-xcwf
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2026/CVE-2026-24477.yaml

## Live exploitation data

The [Live Exploit Tracker page](https://tracker.crowdsec.net/cves/CVE-2026-24477) follows observed exploitation activity for CVE-2026-24477. [Request an API key](https://tracker.crowdsec.net/request-api-key) for full access to its exploitation timeline, attacking IP addresses and blocklists.