CVE-2026-54023
LibreChat user responses exposed server-side OAuth tokens
LibreChat-AI · LibreChat
First documented disclosure · Review checkpoint
Summary
A signed-in browser received its user’s access, ID and refresh tokens.
Severity and exploitation evidence
Medium · 6.0/10 · CVSS 4.0. 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
A response sanitizer omitted federatedTokens/tokenset.
Conditions required
A federated account and browser-context access; exploitation by another party requires a separate path such as XSS.
Potential impact
OAuth credentials intended to remain server-side become accessible to the browser.
Affected versions and configurations
0.8.5 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
Use an explicit public-field allowlist for authentication responses.
Evidence and limits
Earlier auth-refresh sanitization did not cover GET /api/user. CNA publication 2026-11-20 is distinct from the earliest reviewed public source. GitHub_M assessment: CVSS 4.0 6.
Sources
- GitHub_M CVE authority record
Primary source ·
- LibreChat original advisory
Primary source ·
- Public corrective change
Primary source ·