CVE-2026-32717
Unauthorized Access via Browser Extension API Key in AnythingLLM
Publication date: 2026-03-16
Last updated on: 2026-03-16
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| mintplexlabs | anythingllm | to 1.11.1 (inc) |
Helpful Resources
Exploitability
| 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 Powered Q&A
Can you explain this vulnerability to me?
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.
How can this vulnerability impact me? :
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.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know