CVE-2026-54042
LibreChat temporary two-factor challenges lacked attempt throttling
LibreChat-AI · LibreChat
First documented disclosure · Review checkpoint
Summary
Repeated TOTP or backup-code guesses were possible during a temporary challenge.
Severity and exploitation evidence
Medium · 6.8/10 · CVSS 3.1. Severity source.
Exploitation not established: Public evidence describes a weakness, source correction or controlled demonstration; malicious exploitation against users is not established.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
The continuation endpoint had no dedicated attempt limiter.
Conditions required
Valid primary credentials and a valid five-minute temp token.
Potential impact
Full account access if a valid second factor is guessed.
Affected versions and configurations
Before 0.8.7.
Fix and mitigation status
0.8.7.
Practical next steps
Upgrade to 0.8.7 or later and verify the deployed application image includes the correction.
Operating lesson
Throttle the second-factor continuation independently of initial login.
Evidence and limits
Reliability depends on throughput; temp-token issuance remains login-limited. The ±1 window raises per-guess success to about3/1,000,000, not a reduced fixed search space.0.8.7-rc1 also contains the fix. CNA publication 2026-11-20 is distinct from the earliest reviewed public source. GitHub_M assessment: CVSS 3.1 6.8.
Sources
- GitHub_M CVE authority record
Primary source ·
- LibreChat original advisory
Primary source ·
- Public corrective change
Primary source ·