CVE-2026-54045 in LibreChat
Summary
by MITRE • 11/20/2026
LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. Prior to 0.8.7, POST /api/auth/requestPasswordReset calls deleteTokens by user ID before creating a reset token, while password-reset and email-verification records in packages/data-schemas/src/methods/token.ts have no populated flow type. When password reset is enabled and email verification is enforced, an unauthenticated attacker who knows a target email can repeatedly delete pending verification tokens and prevent account verification until the unverified account expires. This issue is fixed in version 0.8.7.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 11/20/2026
The vulnerability identified in LibreChat prior to version 0.8.7 represents a significant flaw in the authentication and identity management subsystem, specifically affecting the password reset and email verification workflows. LibreChat serves as an enhanced ChatGPT clone supporting multiple AI providers, relying on robust user authentication mechanisms to secure access. The core issue stems from the implementation of the POST /api/auth/requestPasswordReset endpoint, which interacts with token management logic defined in packages/data-schemas/src/methods/token.ts. In versions preceding 0.8.7, this endpoint executes a deleteTokens operation based solely on the user ID before generating and storing a new password reset token. This sequence is problematic because it indiscriminately removes all pending tokens associated with that user identifier without distinguishing between different types of verification processes or accounting for concurrent operations.
The technical flaw is exacerbated by the lack of populated flow type definitions in the data schemas governing password-reset and email-verification records. This absence of strict typing likely contributed to a logic error where the system fails to properly isolate state changes intended for one authentication step from another. When both password reset functionality and mandatory email verification are enabled, an unauthenticated attacker who possesses knowledge of a target user's email address can exploit this race condition or logical gap. By repeatedly invoking the requestPasswordReset endpoint, the attacker triggers the deletion of pending email verification tokens associated with that user ID. Since the system deletes existing tokens before creating new ones for password resets, it inadvertently wipes out any active or pending email verification codes required to complete account activation.
The operational impact of this vulnerability is a denial-of-service condition targeting specific user accounts rather than the entire service infrastructure. An attacker can effectively lock an unverified account by continuously deleting its verification tokens, preventing the legitimate user from ever completing the email verification process. This results in the permanent inability for that user to activate their account until it expires or is manually cleared by an administrator. While this does not allow direct data exfiltration or unauthorized access to existing verified accounts, it disrupts service availability for new users and can be used as a vector for harassment or resource exhaustion against specific targets who are in the process of registering.
From a classification perspective, this vulnerability aligns with CWE-602, Client-Side Enforcement of Server-Side Security, although more accurately it reflects CWE-841: Improper Enforcement of Behavioral Workflow and CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition within the application logic. In terms of MITRE ATT&CK mapping, this behavior corresponds to T1059 Command and Scripting Interpreter if viewed through the lens of automated abuse, but more specifically it falls under Account Manipulation techniques where an attacker impedes legitimate access by altering account state properties. The attack vector is classified as Network-based with Low Complexity since it requires only knowledge of a valid email address and no prior authentication credentials.
Mitigation strategies for this vulnerability involve updating LibreChat to version 0.8.7 or later, which addresses the underlying logic errors in token management. For organizations unable to immediately upgrade, implementing rate limiting on the POST /api/auth/requestPasswordReset endpoint is critical to prevent rapid-fire requests that facilitate the deletion of verification tokens. Additionally, application developers should enforce strict input validation and ensure that token operations are atomic and isolated by type rather than just user ID. Implementing a cooldown period between password reset attempts for the same email address can also mitigate this risk. Furthermore, reviewing and enforcing TypeScript flow types in data schemas ensures that logical constraints are properly defined at compile time, reducing the likelihood of such workflow enforcement failures in future updates.