You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
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.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [email protected].
Title: LibreChat de danny-avila, Description: LibreChat es un clon mejorado de ChatGPT que soporta múltiples proveedores de IA. En versiones hasta la 0.8.3 inclusive, los usuarios con acceso solo de 'VIEW' a un servidor MCP pueden recuperar los secretos descifrados administrados por el administrador del servidor a través de 'GET /api/mcp/servers' y 'GET /api/mcp/servers/:serverName'. La configuración devuelta incluye valores en texto plano para 'apiKey.key' y 'oauth.client_secret'. Esto permite a los espectadores de un servidor MCP compartido exfiltrar las credenciales del proveedor subyacente. La versión 0.8..4 contiene un parche. Otras soluciones incluyen: nunca devolver secretos descifrados administrados por el administrador a no propietarios; redactar 'apiKey.key' y 'oauth.client_secret' de todas las respuestas de la API; considerar devolver solo indicadores de presencia booleanos para los secretos, similar al patrón de ruta de valores de autenticación; y, si los propietarios necesitan editar configuraciones sin volver a introducir secretos, preservar los secretos en el lado del servidor y devolver marcadores de posición en lugar de texto plano.
New CVE Received from GitHub, Inc.6/02/2026 7:16:38 PM
Action
Type
Old Value
New Value
Added
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.