Skip to content
Fencer Intel
medium 6.8

CVE-2026-54042 json

LibreChat: Missing Rate Limiting on 2FA Verification Endpoint Allows TOTP Guessing Attempts

published 3d ago modified 17h ago also GHSA-ch3w-5cqg-47qm , EUVD-2026-131850

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository LibreChat-AI/LibreChat. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
6.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 38%
public exploits
0
none known

Summary

LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. Prior to 0.8.7, POST /api/auth/2fa/verify-temp in api/server/routes/auth.js calls verify2FAWithTempToken and accepts repeated TOTP or backup-code guesses without a dedicated attempt limiter. An attacker must first possess valid primary credentials and a valid five-minute temp token, but can then make repeated second-factor attempts and obtain a full session if a valid code is guessed. This issue is fixed in version 0.8.7.

Patch / fix

Is CVE-2026-54042 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-21).

CVSS scores

assigned by version score vector
CNA 3.1 6.8 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected products

  • LibreChat-AI LibreChat

Classification

Weakness
  • CWE-307 Improper Restriction of Excessive Authentication Attempts

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of LibreChat-AI/LibreChat published their own advisory on GitHub. Reviewed sources take precedence over it.