# CVE-2025-69221: LibreChat has Insufficient Access Control for Agent Permission Queries

> An authenticated attacker can read permissions of arbitrary private agents in LibreChat by knowing the agent ID, exposing sensitive configuration data.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 7 Jan 2026
- **Updated:** 7 Jan 2026
- **Also known as:** GHSA-5ccx-4r3h-9qc7

## What is CVE-2025-69221?

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

### Official description

LibreChat is a ChatGPT clone with additional features. Version 0.8.1-rc2 does not enforce proper access control when
querying agent permissions. An authenticated attacker can read the permissions of arbitrary agents, even if they have no permissions for this agent. LibreChat allows the configuration of agents that have a predefined set of instructions and context. Private agents are not visible to other users. However, if an attacker knows the agent ID, they can read the permissions of the agent including the permissions individually assigned to other users. This issue is fixed in version 0.8.2-rc2.

Weakness: CWE-862 (Missing Authorization), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-69221?

It affects 1 product.


Products: Librechat Librechat.

## How do I fix CVE-2025-69221?

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

## Is CVE-2025-69221 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69221 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-2025-69221 and fix it if it is affected.

What it is: CVE-2025-69221 is a medium-severity missing authorization vulnerability in Librechat Librechat, published on 7 Jan 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-2025-69221 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-2025-69221/ (Markdown: https://insights.sbomify.com/CVE-2025-69221/index.md)
```

## Sources

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

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