2FA bypass via unverified backup-code regeneration
Published Jun 25, 2026 · Updated Jun 25, 2026
Missing authentication in LibreChat before 0.8.4-rc1 allows remote authenticated users to bypass 2FA via backup-code regeneration. The regenerateBackupCodes function overwrites stored codes and returns new plaintext codes after only requireJwtAuth, without TOTP or backup-code verification. A stolen victim session token is required; the replacement codes permit login verification or 2FA disablement, but no availability impact is reported.
Summary
What happened
Missing authentication in LibreChat before 0.8.4-rc1 allows remote authenticated users to bypass 2FA via backup-code regeneration. The regenerateBackupCodes function overwrites stored codes and returns new plaintext codes after only requireJwtAuth, without TOTP or backup-code verification. A stolen victim session token is required; the replacement codes permit login verification or 2FA disablement, but no availability impact is reported.
The record
- CVE
- CVE-2026-54040
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- Danny Avila
- Product
- LibreChat
- Classifications
- CWE-306, T1556.006
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 25, 2026CVE publishedPublication date reported by the CVE source.
- Jun 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.8.4-rc1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-h59w-x9h4-m6gv proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo