CVE-2026-24477CWE-201

AnythingLLM has key leak in `systemSettings.js`

High · published January 26, 2026

CVSS v4.0
8.7
EPSS
2%
Percentile
76.8
In the wild
Unconfirmed
What it is

🚨 A misconfigured API endpoint could expose your entire knowledge base! If you're using AnythingLLM with Qdrant before version 1.10.0, your QdrantApiKey might just be sitting there in plain sight! 🔥 Imagine a library where the librarian accidentally leaves the door unlocked and the catalog of rare books is available for anyone to browse. This is what happens when the QdrantApiKey is exposed; unauthorized users can freely access and manipulate the core information stored in the database. An attacker could gain full read/write access to your Qdrant vector database, leading to the complete compromise of your semantic search functionality. This means they could not only retrieve sensitive information but also modify or delete any documents stored, potentially leaking confidential data to the public. That's a security nightmare waiting to happen!

Put simply

Imagine a library where the librarian accidentally leaves the door unlocked and the catalog of rare books is available for anyone to browse. This is what happens when the QdrantApiKey is exposed; unauthorized users can freely access and manipulate the core information stored in the database. This vulnerability allows unauthenticated users to access the QdrantApiKey via the `/api/setup-complete` endpoint, which can grant them unauthorized access to the vector database that AnythingLLM relies on for its search and retrieval operations.

What to do

An attacker could gain full read/write access to your Qdrant vector database, leading to the complete compromise of your semantic search functionality. This means they could not only retrieve sensitive information but also modify or delete any documents stored, potentially leaking confidential data to the public. That's a security nightmare waiting to happen! To secure your setup, immediately update AnythingLLM to version 1.10.0 or later. Review your API configurations to ensure that sensitive keys are not exposed, and limit access to your API endpoints to authenticated users only. A security audit of your current setup is also recommended! You've got this! With these steps, you'll strengthen your defenses in no time. 🛡️

The record
Technical detail
CVSS v4.0
8.7 · HIGH
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
EPSS
0.01686 · 76.8th percentile
Weakness
CWE-201 · Insertion of Sensitive Information Into Sent Data
Published
2026-01-26T23:22Z
EPSS history
Timeline
  • 26 JAN 23:22Z
    AnythingLLM has key leak in `systemSettings.js`
    cvelistv5