What is the CVSS score of CVE-2026-24477?

CVE-2026-24477 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.0%.

Is there a public PoC exploit available for CVE-2026-24477?

Yes, a public proof-of-concept exploit is available for CVE-2026-24477. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-24477?

Within 24 hours: Audit all AnythingLLM deployments to identify affected versions (≤1.10.0) and document systems processing sensitive data. Within 7 days: Implement network segmentation to restrict AnythingLLM access, disable semantic search features if operationally feasible, and establish enhanced monitoring for suspicious queries. Within 30 days: Evaluate alternative solutions, plan upgrade path to patched version when available, and conduct security assessment of any potentially compromised data.

Anythingllm CVE-2026-24477

HIGH

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

2026-01-27 security-advisories@github.com

Information Disclosure AI / ML Anythingllm Mintplexlabs

7.5

CVSS 3.1 · GitHub Advisory

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Access /api/setup-complete endpoint
Exploit

Retrieve exposed QdrantApiKey in plain text
Execution

Authenticate to Qdrant instance
Impact

Read/write vector database contents

Vulnerability Assessment

Weakness	CWE CWE-201 OWASP Top 10:2025 A01:2025 - Broken Access Control ASVS 5.0 V14 - Data Protection Outbound data filtering
Exploitation Conditions	AnythingLLM prior to version 1.10.0 configured with Qdrant vector database backend and API key. /api/setup-complete endpoint must be accessible to unauthenticated users. No authentication required.
Impact	CVSS 7.5 (HIGH). Attack vector: Network. Complexity: Low. Privileges required: None. User interaction: None. Exploitation no authentication required. Public exploit/POC available.
Exploit ScenarioDerived	An attacker without authentication could exploit this vulnerability to complete compromise of the semantic search / retrieval functionality and indirec.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

Anythingllm versions up to 1.10.0 contains a vulnerability that allows attackers to complete compromise of the semantic search / retrieval functionality and indirec (CVSS 7.5).

RemediationAI

Monitor vendor advisories for a patch. Restrict network access to the affected service where possible.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

affects Anythingllm. 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

Know when Anythingllm gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 7.5 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

PoC Detected

Jan 28, 2026 - 15:59 vuln.today

Public exploit code

CVE Published

Jan 27, 2026 - 00:15 nvd

HIGH 7.5

DescriptionGitHub Advisory

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.

Executive ViewAI

Why It Matters

AnythingLLM versions up to 1.10.0 contain a high-severity vulnerability (CVSS 7.5) that enables attackers to compromise semantic search and retrieval functionality, potentially exposing sensitive data indexed within the system. Organizations using this platform face immediate risk of unauthorized data access and system compromise, particularly if AnythingLLM processes confidential or proprietary information.

Business Impact: High

Compensating Controls

Disable semantic search and retrieval features until patch available; implement Web Application Firewall (WAF) rules to filter malicious query patterns; restrict AnythingLLM network access to authorized users only via VPN/network segmentation; implement strict API rate limiting and input validation; enable comprehensive audit logging for all search queries; consider temporary removal of sensitive data from indexed repositories.

Threat Intelligence Overview

EPSS Score

0.0%

Top 90% exploitable

Exploit

POC

Public exploit code exists

Data Quality

4 sources

Confidence: Medium

NVD

CVE.org

EPSS POC (1)

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC Yes

EPSS 0.0%

Patch available No

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived

Out-of-Cycle

Exploitation· derived

Poc

System Exposure· derived

Open

Automatable· derived

Yes

Human Impact

High

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +38

PoC: +20

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.