CVE-2026-54026 is an improper access control vulnerability in LibreChat versions prior to 0.8.6. It allows an authenticated attacker to manipulate message storage by using a conversation ID in the URL that they own while specifying a victim's conversation ID in the request body. This causes attacker-controlled messages to be stored in the victim's conversation. The issue is fixed in LibreChat version 0.8.6.
A regular expression complexity vulnerability (CWE-1333) exists in LibreChat versions from 0.8.6-rc1 up to but not including 0.8.9. An authenticated user with people-picker permission can submit crafted regex patterns that cause catastrophic backtracking, blocking the Node.js event loop and making the service unresponsive. Invalid regex patterns may also cause server errors. This issue is fixed in version 0.8.9.
CVE-2026-54031 is a server-side request forgery (SSRF) vulnerability in LibreChat versions prior to 0.8.8. The issue arises because the OAuth fetch handler validates only the initial destination URL for certain OAuth requests but fails to validate subsequent redirect targets. This allows an attacker who can initiate OAuth requests against a controlled endpoint to cause the server to make requests to internal or private network addresses, bypassing intended SSRF protections. The vulnerability is fixed in LibreChat version 0.8.8.
CVE-2026-54044 is a vulnerability in LibreChat versions prior to 0.8.7 where insufficient protection of credentials allows a collaborator with EDIT permission to redirect an action to an attacker-controlled host. This causes the owner's sensitive credentials, including API keys and OAuth client secrets, to be decrypted and sent to the attacker. The issue is fixed in version 0.8.7.
LibreChat versions prior to 0.8.7 have an information disclosure vulnerability in the unauthenticated POST /api/user/verify endpoint. This endpoint returns distinct responses based on whether an email address is unknown, verified, or unverified, and lacks request throttling. This allows remote attackers to enumerate registered accounts and their verification status by submitting email addresses with invalid tokens. The issue is fixed in version 0.8.7.
CVE-2026-54045 is a vulnerability in LibreChat versions prior to 0.8.7 involving a weak password recovery mechanism. An unauthenticated attacker who knows a target's email can repeatedly delete pending verification tokens, preventing account verification until the unverified account expires. This issue is fixed in version 0.8.7.
CVE-2026-54042 is a vulnerability in LibreChat versions prior to 0.8.7 where the two-factor authentication (2FA) verification endpoint lacks a proper limiter on repeated attempts. An attacker with valid primary credentials and a temporary token can repeatedly guess TOTP or backup codes without restriction, potentially gaining full session access if a correct code is guessed. This flaw is fixed in version 0.8.7.
A vulnerability in LibreChat versions 0.8.5 up to but not including 0.8.6 allows exposure of sensitive OAuth tokens to authenticated users via the GET /api/user endpoint. This occurs because response sanitization was not applied, enabling browser scripts to access OAuth access, ID, and refresh tokens that should remain server-side. The issue is fixed in version 0.8.6.
LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. Prior to 0.8.7, packages/data-schemas/src/methods/file.ts updateFileUsage accepts chat attachment files[].file_id values without restricting the lookup to the authenticated owner. An authenticated attacker who obtains another user's file identifier, including through GET /api/share/{shareId} for a shared conversation, can attach that file to a chat, causing extracted document text to enter the model context. The same operation can remove expiration metadata from the victim file. This issue is fixed in version 0.8.7.
CVE-2026-54032 is a cross-site scripting (XSS) vulnerability in LibreChat versions prior to 0.8.6. The issue arises because certain user interface components render HTML content from remote or administrator-controlled sources without proper sanitization, allowing malicious scripts to execute in the browser context. This can lead to exposure of browser data or manipulation of displayed content. The vulnerability is fixed in version 0.8.6.
A vulnerability in LibreChat versions 0.7.0 through 0.8.5 allows an unauthenticated attacker to forge a provider value for a victim's email during registration when local registration and social login providers are enabled. This leads to the attacker and victim sharing the same user record, granting the attacker persistent read and write access to the victim's data. The issue is fixed in version 0.8.6.
A vulnerability in LibreChat prior to version 0.8.6 allows sensitive information, specifically plaintext passwords, to be logged during failed login attempts via the local-login validation path. This occurs because the application logs the entire request body without redacting passwords when Zod validation fails. An attacker or unauthorized party with access to application logs can retrieve these credentials. The issue is fixed in version 0.8.6.