CVE-2026-32717
Awaiting Analysis Awaiting Analysis - Queue
Unauthorized Access via Browser Extension API Key in AnythingLLM

Publication date: 2026-03-16

Last updated on: 2026-03-16

Assigner: GitHub, Inc.

Description
AnythingLLM is an application that turns pieces of content into context that any LLM can use as references during chatting. In 1.11.1 and earlier, in multi-user mode, AnythingLLM blocks suspended users on the normal JWT-backed session path, but it does not block them on the browser extension API key path. If a user already has a valid brx-... browser extension API key, that key continues to work after suspension. As a result, a suspended user can still access browser extension endpoints, read reachable workspace metadata, and continue upload or embed operations even though normal authenticated requests are rejected.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-16
Last Modified
2026-03-16
Generated
2026-06-16
AI Q&A
2026-03-16
EPSS Evaluated
2026-06-14
NVD
CVE-2026-32717
EUVD
EUVD-2026-12176
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
mintplexlabs anythingllm to 1.11.1 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in AnythingLLM versions 1.11.1 and earlier when running in multi-user mode. Normally, suspended users are blocked from accessing the application via the standard JWT-backed session path. However, suspended users are not blocked when using the browser extension API key path. If a suspended user already possesses a valid browser extension API key, they can continue to use it to access browser extension endpoints.

As a result, suspended users can still read accessible workspace metadata and perform upload or embed operations through the browser extension API, even though their normal authenticated requests are rejected.

Impact Analysis

The impact of this vulnerability is that suspended users retain partial access to the system through the browser extension API key path. They can continue to read workspace metadata and perform upload or embed operations despite being suspended.

This could lead to unauthorized access to sensitive information and unauthorized actions within the application, potentially compromising data integrity and confidentiality.

Compliance Impact

I don't know

Detection Guidance

I don't know

Mitigation Strategies

I don't know

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-32717. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart