CVE-2026-54039
LibreChat registration allowed attacker-chosen OAuth providers
LibreChat-AI · LibreChat
First documented disclosure · Review checkpoint
Summary
A pre-registered account could retain attacker password access when a victim later used social login.
Severity and exploitation evidence
High · 8.1/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
Registration persists provider from unparsed input and social login trusts a matching provider string during email fallback.
Conditions required
Local registration enabled, a social provider configured, attacker knows victim email, and victim later signs in with that provider.
Potential impact
Attacker and victim can share an account containing subsequent conversations, files and AI configuration.
Affected versions and configurations
0.7.0 through before 0.8.6.
Fix and mitigation status
0.8.6.
Practical next steps
Upgrade to 0.8.6 or later and verify the deployed application image includes the correction.
Operating lesson
Persist only validated profile fields; obtain identity-provider bindings from trusted server state.
Evidence and limits
First-user administrative promotion is conditional and separate. A distinct unverified provider-email trust report remains open. CNA publication 2026-11-20 is distinct from the earliest reviewed public source. GitHub_M assessment: CVSS 3.1 8.1.
Sources
- GitHub_M CVE authority record
Primary source ·
- LibreChat original advisory
Primary source ·
- Public corrective change
Primary source ·