LibreChat account takeover via social login email fallback
- Exploited
- No known exploitation
- Fix
- Fixed in 0.8.6
- Who is exposed
- Specific setups only
Summary
A remote attacker, without logging in, can pre-register an account under a victim's email address, and that account gets linked to the victim's record when the victim later signs in with social login. The attacker can then keep persistent read and write access to data the victim creates in LibreChat.
Written by a model
Original description
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.
Who should check
Teams running LibreChat from 0.7.0 before 0.8.6 with local registration enabled and at least one social login provider configured.
“>= 0.7.0, < 0.8.6”
What to do
Check whether your setup matches what the bug needs.
Local registration is enabled (ALLOW_REGISTRATION=true). At least one social login provider is configured. Affected LibreChat versions are 0.7.0 up to but not including 0.8.6.Upgrade to a fixed version: 0.8.6.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-54039 (LibreChat: Pre-registration account takeover via attacker-controlled `provider` field and social-login email fallback), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-54039 (entry last updated 2026-11-20):
Affected:
- danny-avila LibreChat: from 0.7.0, fixed in 0.8.6
Fixed versions: 0.8.6.
Conditions (all must be true for the bug to be hit):
- Local registration is enabled (ALLOW_REGISTRATION=true). (source: https://github.com/LibreChat-AI/LibreChat/security/advisories/GHSA-wjpf-x42h-cv4m)
- At least one social login provider is configured. (source: https://github.com/LibreChat-AI/LibreChat/security/advisories/GHSA-wjpf-x42h-cv4m)
- Affected LibreChat versions are 0.7.0 up to but not including 0.8.6. (source: https://github.com/LibreChat-AI/LibreChat/security/advisories/GHSA-wjpf-x42h-cv4m)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-54039 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-54039 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/LibreChat-AI/LibreChat/security/advisories/GHSA-wjpf-x42h-cv4m
- https://github.com/LibreChat-AI/LibreChat/pull/13307
- https://github.com/LibreChat-AI/LibreChat/commit/b01d34abe29152e6e7f763089c0d9a6e647d0dba
- https://github.com/LibreChat-AI/LibreChat/releases/tag/v0.8.6
- https://www.librechat.ai/changelog/v0.8.6
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-54039
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-54039"}.Affected versions
- danny-avila LibreChatFrom 0.7.0 · fixed in 0.8.6
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.1/10CVSS 8.1
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
Evidence 7
| Kind | Source |
|---|---|
| Vendor advisory 2Establishes: Affected and fixed versions. | |
| Advisory | GitHub · LibreChat-AI/LibreChat · Advisory GHSA-wjpf-x42h-cv4m |
| Link | librechat.ai · changelog/v0.8.6 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-54039 |
| Record | NVD · CVE-2026-54039 |
| Other links 3 | |
| Repository | GitHub · LibreChat-AI/LibreChat · Pull request #13307 |
| Repository | GitHub · LibreChat-AI/LibreChat · Commit b01d34ab |
| Repository | GitHub · LibreChat-AI/LibreChat · Release v0.8.6 |
Questions about CVE-2026-54039
Is CVE-2026-54039 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
An attacker can pre-register a local account using a victim's email address before the victim signs up. When the victim later signs in with a social login, the attacker keeps local-password access to the same account and its data.
Source: github.com
Which versions are affected by CVE-2026-54039?
LibreChat: from 0.7.0 before 0.8.6.
Source: cve.now feed data
Am I affected, and how do I check?
LibreChat versions 0.7.0 up to but not including 0.8.6 are affected, when local registration is enabled (ALLOW_REGISTRATION=true) and at least one social login provider is configured. You can check the version you run and whether ALLOW_REGISTRATION is set to true in your environment settings.
Source: github.com
How do I fix CVE-2026-54039?
No fixed version is listed in the checked facts, so no upgrade target can be confirmed from them. Check the LibreChat advisory for the current fix status or vendor patch guidance.
Source: github.com
Related
- CVE-2026-32625LibreChat Exfiltrates Server Secrets via MCP Server URL Injection
- CVE-2026-54030LibreChat: Missing Resource Parameter Validation in MCP OAuth Flow
- CVE-2026-54033LibreChat: SSRF via User-Provided Custom Endpoint baseURL — no private IP validation on user-configured API base URLs
- CVE-2026-31942LibreChat has IDOR in API Keys Management that allows any authenticated user to overwrite other users' API keys
- CVE-2026-54042LibreChat: Missing Rate Limiting on 2FA Verification Endpoint Allows TOTP Guessing Attempts
- CVE-2026-54045LibreChat: Password Reset Can Wipe Email-Verification Tokens When Verification Is Enforced
No corrections so far. Something wrong on this page? Report an error.