CVE-2026-44653: CWE-201: Insertion of Sensitive Information Into Sent Data in danny-avila LibreChat
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.
AI Analysis
Technical Summary
CVE-2026-44653 is a vulnerability in danny-avila's LibreChat (up to and including version 0.8.3) where users with VIEW access to an MCP server can access decrypted admin-managed secrets through the API endpoints GET /api/mcp/servers and GET /api/mcp/servers/:serverName. The API responses include plaintext values for sensitive fields such as apiKey.key and oauth.client_secret, enabling unauthorized disclosure of provider credentials. The vulnerability is classified under CWE-201 (Insertion of Sensitive Information Into Sent Data). A patch is included in version 0.8.4 that prevents returning these secrets to non-owners by redacting or replacing them with placeholders.
Potential Impact
The vulnerability allows users with limited VIEW permissions to obtain plaintext admin-managed secrets, including API keys and OAuth client secrets, which can lead to unauthorized access to underlying AI provider services. This compromises confidentiality but does not affect integrity or availability. There are no known exploits in the wild as of the publication date.
Mitigation Recommendations
Upgrade LibreChat to version 0.8.4 or later, which contains a patch that prevents returning decrypted admin-managed secrets to users without ownership privileges. Additional recommended mitigations include redacting sensitive fields such as apiKey.key and oauth.client_secret from API responses or returning only boolean indicators of secret presence. If configuration editing without re-entry of secrets is required, secrets should be preserved server-side and replaced with placeholders in API responses. Patch status is not explicitly confirmed in the advisory, but version 0.8.4 is stated to contain the fix.
CVE-2026-44653: CWE-201: Insertion of Sensitive Information Into Sent Data in danny-avila LibreChat
Description
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.
CVSS v3.1
Score 6.5medium
Affected software
pkg:github/danny-avila/LibreChatRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-44653 is a vulnerability in danny-avila's LibreChat (up to and including version 0.8.3) where users with VIEW access to an MCP server can access decrypted admin-managed secrets through the API endpoints GET /api/mcp/servers and GET /api/mcp/servers/:serverName. The API responses include plaintext values for sensitive fields such as apiKey.key and oauth.client_secret, enabling unauthorized disclosure of provider credentials. The vulnerability is classified under CWE-201 (Insertion of Sensitive Information Into Sent Data). A patch is included in version 0.8.4 that prevents returning these secrets to non-owners by redacting or replacing them with placeholders.
Potential Impact
The vulnerability allows users with limited VIEW permissions to obtain plaintext admin-managed secrets, including API keys and OAuth client secrets, which can lead to unauthorized access to underlying AI provider services. This compromises confidentiality but does not affect integrity or availability. There are no known exploits in the wild as of the publication date.
Mitigation Recommendations
Upgrade LibreChat to version 0.8.4 or later, which contains a patch that prevents returning decrypted admin-managed secrets to users without ownership privileges. Additional recommended mitigations include redacting sensitive fields such as apiKey.key and oauth.client_secret from API responses or returning only boolean indicators of secret presence. If configuration editing without re-entry of secrets is required, secrets should be preserved server-side and replaced with placeholders in API responses. Patch status is not explicitly confirmed in the advisory, but version 0.8.4 is stated to contain the fix.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-07T15:30:10.876Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a1f64cce29bf47b5010d699
Added to database: 06/02/2026, 23:18:36 UTC
Last enriched: 06/10/2026, 11:03:39 UTC
Last updated: 07/18/2026, 17:31:43 UTC
Views: 103
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.