# CVE-2026-55611: Missing authorization in anything-llm

> Authenticated managers or admins can delete any user's parsed files across all workspaces by enumerating file IDs due to missing ownership checks.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-r872-gr59-vf5w, MINI-4x3f-v546-cm8r

## What is CVE-2026-55611?

CVE-2026-55611 is a missing authorization vulnerability in Mintplex-Labs anything-llm, published on 24 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

AnythingLLM is an application that turns pieces of content into context that any LLM can use as references during chatting. From 1.11.1 until 1.14.1, userId/workspaceId scoping to the parsed-files read/delete paths was added. However, the POST /api/workspace/:slug/embed-parsed-file/:fileId flow still deletes the target file by primary key only, with no ownership check, inside two finally{} blocks that run even when the ownership-checked read fails. As a result a manager or admin (multi-user mode) can delete any other user's parsed file in any workspace — including workspaces they are not a member of — by enumerating integer fileIds. The server even returns "File not found" while still deleting the file. This vulnerability is fixed in 1.14.1.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-55611 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55611 is a missing authorization vulnerability in Mintplex-Labs anything-llm, published on 24 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55611 exists.

Affected product: Mintplex-Labs anything-llm. 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-55611/ (Markdown: https://insights.sbomify.com/CVE-2026-55611/index.md)
```

## Sources

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

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