Answer in brief
CVE-2026-54039 records a High severity (CVSS 8.1) vulnerability in LibreChat: Pre-registration account takeover via attacker-controlled `provider` field and social-login email fallback. The current sources do not mark it as known exploited. The current feed maps danny-avila/LibreChat (generic), LibreChat-AI/LibreChat (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps danny-avila/LibreChat (generic), LibreChat-AI/LibreChat (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| danny-avila/LibreChatgeneric | >=0.7.0 <0.8.6 | 0.8.6 |
| LibreChat-AI/LibreChatgeneric | >=0.7.0 <0.8.6 | 0.8.6 |
Published upstream
Nov 20, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 20, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 20, 2026
LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. From 0.7.0 until 0.8.6, when local registration is enabled and at least one social provider is configured, POST /api/auth/register passes an unparsed request object into api/server/services/AuthService.js, allowing an unauthenticated attacker to persist a forged provider value for a known victim email. The api/strategies/socialLogin.js email-fallback path then accepts the planted record when the victim signs in because it compares the stored provider name without requiring the provider subject identifier. The victim OAuth session and the attacker local-password session become bound to the same user record, giving the attacker persistent read and write access to data created by the victim. The first-user administrator role is an additional conditional impact only on a fresh deployment. This issue is fixed in version 0.8.6.
Quoted source text, attributed separately from HOL analysis.