# CVE-2026-44654: LibreChat: Shared-agent editor can globally delete owner's file records — breaks owner's other private agents

> A shared-agent editor can globally delete files used by the owner's private agents, causing those agents to break due to missing file references.

- **Severity:** Medium 5.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jun 2026
- **Updated:** 3 Jun 2026
- **Also known as:** GHSA-f8jg-v856-mf6q

## What is CVE-2026-44654?

CVE-2026-44654 is a medium-severity missing authorization vulnerability in Librechat Librechat, published on 2 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. In versions up to and including 0.8.3, a shared-agent editor can delete file records through `DELETE /api/files` that the owner has reused across multiple agents. The deletion removes the file globally — not just from the shared agent — breaking the owner's other private agents that reference the same `file_id`. The private agent retains a stale `file_id` reference that no longer resolves. A shared-agent editor can destroy files that the owner uses across multiple agents. The owner's private agents — which the attacker has no access to — break silently with stale `file_id` references. This is a cross-agent integrity violation: editing access to one agent should not affect another. Version 0.8.4 contains a patch.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Librechat Librechat.

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

No fix has been published for CVE-2026-44654 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-44654 being exploited?

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

## Other vulnerabilities in Librechat Librechat

- [CVE-2026-32625](https://insights.sbomify.com/CVE-2026-32625/): LibreChat Exfiltrates Server Secrets via MCP Server URL Injection (critical 9.6)
- [CVE-2024-11167](https://insights.sbomify.com/CVE-2024-11167/): Improper Access Control in danny-avila/librechat (critical 9.4)
- [CVE-2026-22252](https://insights.sbomify.com/CVE-2026-22252/): LibreChat MCP Stdio Remote Command Execution (critical 9.1)
- [CVE-2025-69222](https://insights.sbomify.com/CVE-2025-69222/): LibreChat is vulnerable to Server-Side Request Forgery due to missing restrictions (critical 9.1)
- [CVE-2024-41704](https://insights.sbomify.com/CVE-2024-41704/): Path traversal in n/a (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44654 is a medium-severity missing authorization vulnerability in Librechat Librechat, published on 2 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44654 exists.

Affected product: Librechat Librechat. 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-44654/ (Markdown: https://insights.sbomify.com/CVE-2026-44654/index.md)
```

## Sources

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

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