CVE-2026-44653
MediumCVSS 6.5Exploitation Probability (EPSS)
Low risk20th percentile - higher than 20% of all known CVEs
Summary
LibreChat versions up to and including 0.8.3 allow users with only VIEW access to an MCP server to retrieve the server's decrypted admin-managed secrets through GET /api/mcp/servers and GET /api/mcp/servers/:serverName. The returned config includes plaintext values for apiKey.key and oauth.client_secret. This allows viewers of a shared MCP server to exfiltrate the underlying provider credentials. Version 0.8.4 contains a patch.
Risk Assessment
Users with limited permissions can access sensitive API keys and OAuth secrets, potentially leading to unauthorized access to external AI services.
Recommendation
Update LibreChat to version 0.8.4 or later, which does not return decrypted secrets to non-owner users.
Other vulnerabilities in LibreChat
See all- CVE-2025-69220High
LibreChat version 0.8.1-rc2 does not enforce proper access control for file uploads to an agents file context and file search. An authenticated attacker with access to the agent ID can change the behavior of arbitrary agents by uploading new files, even without permissions for that agent. Fixed in version 0.8.2-rc2.
- CVE-2026-32625Critical
LibreChat up to version 0.8.3 has a vulnerability in the MCP server integration that resolves ${VAR} placeholders from process.env during Zod schema validation of user-supplied MCP URLs. An authenticated user can create a malicious MCP configuration that sends critical secrets (CREDS_KEY, CREDS_IV, JWT_SECRET, MONGO_URI) to an attacker-controlled server.
- CVE-2026-22252Critical
LibreChat prior to v0.8.2-rc2 has a vulnerability in the MCP stdio transport that accepts arbitrary commands without validation, allowing any authenticated user to execute shell commands as root inside the container through a single API request. This vulnerability is fixed in v0.8.2-rc2.
- CVE-2025-69222Critical
LibreChat version 0.8.1-rc2 is prone to SSRF due to missing restrictions in the Actions feature by default. Agents can access internal services like the RAG API in the default Docker Compose setup.
- CVE-2026-54040Medium
A vulnerability in LibreChat prior to 0.8.4-rc1 allows an attacker with a stolen session token to regenerate all 2FA backup codes without requiring any TOTP token or existing backup code. This enables bypassing 2FA login or disabling 2FA entirely.
- CVE-2026-54037Medium
A vulnerability in LibreChat prior to 0.8.4-rc1 allows an authenticated user to bypass rate limiters added for the /fork endpoint by using the /duplicate endpoint, which performs the same expensive database operations but lacks any rate limiter. This can lead to server resource exhaustion.
- CVE-2026-54033High
LibreChat before version 0.8.4-rc1 allows authenticated users to set a custom URL for OpenAI-compatible API endpoints. This URL is used to construct HTTP requests without any SSRF validation, enabling traffic to be directed to internal network addresses.
- CVE-2026-54030High
A vulnerability in LibreChat before version 0.8.5 allows a malicious MCP server to steal access tokens intended for a legitimate server. The MCP OAuth implementation does not validate that the resource parameter from OAuth Protected Resource metadata (RFC 9728) matches the configured MCP server URL.
- CVE-2026-54029Medium
A vulnerability in LibreChat before version 0.8.4-rc1 allows any authenticated user to delete any other user's messages. The delete endpoint lacks a user constraint, enabling an attacker to use their own conversation ID and the victim's message ID to permanently remove messages.
- CVE-2026-54025Medium
LibreChat prior to version 0.8.4-rc1 has a vulnerability due to missing HTML escaping of double-quote characters in image alt text in Markdown. An attacker can inject malicious HTML code that executes in the victim's browser.
Original NVD description (English source)
LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. In versions up to and including 0.8.3, users with only `VIEW` access to an MCP server can retrieve the server's decrypted admin-managed secrets through `GET /api/mcp/servers` and `GET /api/mcp/servers/:serverName`. The returned config includes plaintext values for `apiKey.key` and `oauth.client_secret`. This allows viewers of a shared MCP server to exfiltrate the underlying provider credentials. Version 0.8..4 contains a patch. Other remediations include: never returning decrypted admin-managed secrets to non-owners; redacting apiKey.key and oauth.client_secret from all API responses consider returning only boolean presence indicators for secrets, similar to the auth-values route pattern; and, if owners need to edit configs without re-entering secrets, preserving secrets server-side and returning placeholders instead of plaintext.