CVE-2026-54036: LibreChat 2FA Bypass via Unprotected Endpoint—Patch to 0.8.4-rc1

Technical summary

The GET /api/auth/2fa/enable endpoint in LibreChat fails to enforce proper authorization checks when 2FA is already active on an account. The endpoint does not verify current TOTP tokens or backup codes before modifying authentication state. When called by an authenticated session (PR:L in the CVSS vector), it performs four dangerous operations: overwrites the TOTP secret, generates and replaces all backup codes, sets twoFactorEnabled to false, and likely returns new credentials to the caller—all within a single unprotected transaction. The vulnerability stems from missing step-up authentication (CWE-306) at a sensitive endpoint. No user interaction is required; a passive session token is sufficient. The fix in 0.8.4-rc1 presumably adds TOTP or backup code verification before allowing 2FA reconfiguration.

Business impact

Organizations using LibreChat for internal AI interactions face a direct threat to account takeover resistance. If an attacker gains a user's session token through phishing, malware, or network compromise, they can immediately neutralize that account's 2FA defense, ensuring persistent unauthorized access even if the user detects the breach and changes their password. For compliance and audit purposes, this vulnerability violates the principle of strong authentication controls and may trigger incident reporting obligations under frameworks like SOC 2, HIPAA, or GDPR if customer or regulated data flows through LibreChat instances.

Affected systems

LibreChat prior to version 0.8.4-rc1 is affected. The vulnerability exists in the authentication subsystem and affects any LibreChat instance where 2FA has been enabled. Self-hosted and cloud-based deployments are equally vulnerable if running an unpatched version. Users relying on LibreChat as their primary AI gateway should prioritize updates.

Exploitability

Exploitability is moderate and requires pre-existing access (a valid session token). The attacker does not need to interact with the victim or bypass network defenses; they can trigger the exploit programmatically via a single HTTP request. The high AC (Attack Complexity) value in the CVSS reflects the prerequisite of obtaining a session token, but modern session theft vectors (XSS, credential stuffing, malware) make this a realistic secondary attack once initial compromise occurs. No special tools or deep knowledge of LibreChat internals are needed.

Remediation

Upgrade LibreChat to version 0.8.4-rc1 or later immediately. This is a session-based compromise that does not require password reset alone; users should assume that if their session was exposed, an attacker may have already accessed and disabled 2FA. After patching, audit 2FA settings across all accounts and consider issuing a security notice advising users to review recent login activity and confirm their 2FA configuration.

Patch guidance

Apply the 0.8.4-rc1 release or any subsequent stable version. Verify the patch by confirming the version string in your LibreChat instance (typically visible in UI footer or via API endpoint). Test 2FA functionality after patching: attempt to call /api/auth/2fa/enable when 2FA is already active and confirm that it now requires TOTP or backup code verification before proceeding. Restart services if running a containerized deployment.

Detection guidance

Monitor logs for repeated calls to the /api/auth/2fa/enable endpoint from a single session or IP address, especially if followed by successful TOTP secret or backup code changes. Implement alerting on any 2FA disable or reset event that lacks corresponding TOTP verification logs. Check for audit trails showing discrepancies between user-initiated 2FA changes and actual endpoint calls. In LibreChat's database, query the user authentication log for instances where twoFactorEnabled transitioned from true to false without a documented verification step.

Why prioritize this

Although the CVSS score is medium (5.3), this vulnerability directly undermines a primary security control—two-factor authentication. Any organization running LibreChat should treat this as high priority for patching because the impact (loss of 2FA integrity) is disproportionate to the technical complexity of exploitation. Session compromise is increasingly common, and 2FA bypass is a known precursor to full account takeover in multi-factor environments.

Risk score, explained

The CVSS 5.3 score reflects the requirement for a pre-existing authenticated session (lowering the score from critical to medium) and the fact that confidentiality is not directly impacted. However, the integrity impact is rated HIGH because the attacker can permanently modify the authentication posture of an account. The score appropriately captures that this is not a pre-auth remote code execution, but it underplays the organizational risk when 2FA is the last defense against session-based attacks. Security teams should weight this higher than the raw score suggests in their own risk models.

Frequently asked questions