Security readout for executives and security teams
Plain-English summary
AnythingLLM before 1.10.0 can expose a configured Qdrant API key to unauthenticated users through a setup endpoint. That key can allow full read/write access to the Qdrant vector database, which may hold sensitive retrieval data used by RAG workflows. Upgrade priority is high for exposed or production AnythingLLM deployments using Qdrant with an API key.
Executive priority
Treat as high priority where AnythingLLM supports business RAG or knowledge-base workflows. A leaked Qdrant key could let an attacker read or alter retrieval data, undermining confidentiality and trust in LLM answers. Patch and key rotation should be scheduled urgently for affected deployments.
Technical view
CVE-2026-24477 is a CWE-201 sensitive information exposure in Mintplex-Labs anything-llm versions before 1.10.0. When configured with Qdrant and a QdrantApiKey, the key may be returned in plaintext via /api/setup-complete without authentication. The CVSS v4.0 score is 8.7, network exploitable, low complexity, no privileges, and no user interaction.
Likely exposure
Exposure is limited to AnythingLLM versions before 1.10.0 that use Qdrant as the vector database with an API key configured. Internet-facing deployments or internally reachable instances are higher concern. Deployments not using Qdrant API keys are not described as affected in the provided sources.
Exploitation context
The advisory describes unauthenticated network access to a setup endpoint that can disclose the Qdrant API key. The source bundle does not indicate CISA KEV listing or active exploitation. If obtained, the key could enable read/write access to the Qdrant database and compromise retrieval integrity or expose sensitive uploaded document content indirectly.
Researcher notes
The issue is specifically tied to systemSettings.js behavior exposing QdrantApiKey through /api/setup-complete before 1.10.0. Public sources confirm the affected version boundary and impact but do not provide evidence of exploitation in the wild. Validate exposure by configuration and version, not by product presence alone.
Mitigation direction
- Upgrade AnythingLLM to version 1.10.0 or later.
- Rotate any Qdrant API key used by affected AnythingLLM instances.
- Review vendor advisory for any deployment-specific guidance.
- Assess Qdrant data exposure and integrity if the endpoint was reachable.
Validation and detection
- Inventory AnythingLLM versions and flag any instance below 1.10.0.
- Confirm whether affected instances use Qdrant with an API key.
- Review access logs for unauthenticated requests to /api/setup-complete.
- Verify Qdrant API keys were rotated after upgrade.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-201: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-24477 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.7 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
8.7HighVector: 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
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Mintplex-Labs/anything-llm/security/advisories/GHSA-gm94-qc2p-xcwfCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insertion of Sensitive Information Into Sent Data
Insertion of Sensitive Information Into Sent Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.