LibreChat user enumeration in email verification endpoint
- Exploited
- No known exploitation
- Fix
- Fixed in 0.8.7
- Who is exposed
- Not reported
Summary
LibreChat, an AI chat application, has a flaw in its email verification endpoint that lets anyone on the network, without logging in, find out which email addresses have accounts and whether each is verified. An attacker can use that list to target phishing or credential attacks.
Written by a model
Original description
LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. Prior to 0.8.7, unauthenticated POST /api/user/verify requests in api/server/routes/user.js call api/server/services/AuthService.js verifyEmail and return distinct responses for unknown, verified, and unverified email addresses and the route lacks request throttling. A remote attacker can submit candidate addresses with invalid tokens to enumerate registered accounts and verification state, supporting targeted phishing or credential attacks. This issue is fixed in version 0.8.7.
What to do
Upgrade to a fixed version: 0.8.7.
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-54046 (LibreChat: Unauthenticated User Enumeration via Email Verification Endpoint), 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-54046 (entry last updated 2026-11-20):
Affected:
- LibreChat-AI LibreChat: fixed in 0.8.7
Fixed versions: 0.8.7.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-54046 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-54046 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-449m-g56j-h8hj
- https://github.com/LibreChat-AI/LibreChat/pull/13558
- https://github.com/LibreChat-AI/LibreChat/commit/8c71dbcb320cdbea2770317ef77dacce4bb068bf
- https://github.com/LibreChat-AI/LibreChat/releases/tag/v0.8.7
- https://www.librechat.ai/changelog/v0.8.7
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-54046
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-54046"}.Affected versions
- LibreChat-AI LibreChatfixed in 0.8.7
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
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-449m-g56j-h8hj |
| Link | librechat.ai · changelog/v0.8.7 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-54046 |
| Record | NVD · CVE-2026-54046 |
| Other links 3 | |
| Repository | GitHub · LibreChat-AI/LibreChat · Pull request #13558 |
| Repository | GitHub · LibreChat-AI/LibreChat · Commit 8c71dbcb |
| Repository | GitHub · LibreChat-AI/LibreChat · Release v0.8.7 |
Questions about CVE-2026-54046
Is CVE-2026-54046 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
Which versions are affected by CVE-2026-54046?
LibreChat: before 0.8.7.
Source: cve.now feed data
How do I fix CVE-2026-54046?
Upgrade to a fixed version: 0.8.7.
Source: cve.now feed data
Related
- CVE-2026-54044LibreChat: Shared-Agent Editor Can Exfiltrate Owner Action API Keys via OpenAPI Spec Swap
- CVE-2026-54026LibreChat: Cross-User Message Injection via Parameter Confusion
- CVE-2026-54038LibreChat: Server-Side ReDoS via Unescaped Regex in Principal Search
- CVE-2026-54031LibreChat: MCP OAuth requests can follow redirects to internal URLs after SSRF validation
- CVE-2026-19134A vulnerability in OpenText OpenText Directory Services (OTDS) allows Black Box Reverse Engineering.
- CVE-2026-63399Coop: Unauthenticated org provisioning via GraphQL Mutation.createOrg
No corrections so far. Something wrong on this page? Report an error.