# CVE-2026-47713: AnythingLLM: Legacy mobile device tokens bypass multi-user workspace scoping after mode migration

> A stale mobile token from single-user mode bypasses multi-user scoping, allowing attackers to read other users' workspace data and chat content.

- **Severity:** Low 2.0 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 28 May 2026
- **Updated:** 29 May 2026
- **Also known as:** GHSA-h349-hp2v-8rhw, MINI-g996-4qwv-wcpf

## What is CVE-2026-47713?

CVE-2026-47713 is a low-severity missing authorization vulnerability in Mintplexlabs Anythingllm, published on 28 May 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

AnythingLLM is an application that turns pieces of content into context that any LLM can use as references during chatting. Prior to 1.13.0, an approved mobile device token created in single-user mode can survive single-user -> multi-user migration even when the device record has userId = null. In multi-user mode, that stale token is still accepted by the mobile authentication middleware. Because no user is attached to the request, downstream mobile handlers fall back to unscoped data-access branches and return workspaces and workspace content without per-user filtering. This permits a pre-migration mobile token to enumerate a workspace assigned only to another user and retrieve victim-owned thread metadata and chat content in multi-user mode. This vulnerability is fixed in 1.13.0.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-47713?

It affects 1 product.


Products: Mintplexlabs Anythingllm.

## How do I fix CVE-2026-47713?

Upgrade to a fixed version.

## Is CVE-2026-47713 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47713 exists.

## Other vulnerabilities in Mintplexlabs Anythingllm

- [CVE-2024-3025](https://insights.sbomify.com/CVE-2024-3025/): Path Traversal in mintplex-labs/anything-llm (critical 9.9)
- [CVE-2024-0455](https://insights.sbomify.com/CVE-2024-0455/): SSRF on AWS deployed instances of AnythingLLM via /metadata (critical 9.9)
- [CVE-2026-32626](https://insights.sbomify.com/CVE-2026-32626/): AnythingLLM has a Streaming Phase XSS to RCE via LLM Response Injection (critical 9.7)
- [CVE-2024-3104](https://insights.sbomify.com/CVE-2024-3104/): Remote Code Execution in mintplex-labs/anything-llm (critical 9.6)
- [CVE-2024-3149](https://insights.sbomify.com/CVE-2024-3149/): SSRF in mintplex-labs/anything-llm (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47713 and fix it if it is affected.

What it is: CVE-2026-47713 is a low-severity missing authorization vulnerability in Mintplexlabs Anythingllm, published on 28 May 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47713 exists.

Affected product: Mintplexlabs Anythingllm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47713/ (Markdown: https://insights.sbomify.com/CVE-2026-47713/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47713
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47713
- OSV: https://osv.dev/vulnerability/CVE-2026-47713

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47713/
Summaries are generated and may contain mistakes; the official description above is the record.