CVE-2025-8850
HighCVSS 8.8Exploitation Probability (EPSS)
Low risk33th percentile - higher than 33% of all known CVEs
Summary
In danny-avila/librechat version 0.7.9, there is an insecure API design issue in the 2-Factor Authentication (2FA) flow. The system allows users to disable 2FA without requiring a valid OTP or backup code, bypassing the intended verification process. This vulnerability occurs because the backend does not properly validate the OTP or backup code when the API endpoint '/api/auth/2fa/disable' is directly accessed.
Risk Assessment
The risk includes the possibility of an authenticated user weakening the security of their own account, which may facilitate later unauthorized account takeover, although it does not lead to full compromise.
Recommendation
It is recommended to update LibreChat to a version that fixes this issue and to implement proper validation of OTP and backup codes on the server side.
Other vulnerabilities in LibreChat
See all- 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.
- CVE-2026-54024Medium
A vulnerability in LibreChat before version 0.8.4-rc1 allows an authenticated user to upload arbitrarily large files via the conversation import endpoint, potentially exhausting server disk space and memory. The issue stems from missing file size limits in a separate multer instance for this endpoint and a disabled application-level size check by default.
Original NVD description (English source)
In danny-avila/librechat version 0.7.9, there is an insecure API design issue in the 2-Factor Authentication (2FA) flow. The system allows users to disable 2FA without requiring a valid OTP or backup code, bypassing the intended verification process. This vulnerability occurs because the backend does not properly validate the OTP or backup code when the API endpoint '/api/auth/2fa/disable' is directly accessed. This flaw can be exploited by authenticated users to weaken the security of their own accounts, although it does not lead to full account compromise.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS