Skip to content
Fencer Intel
medium 5.3

CVE-2026-54046 json

LibreChat: Unauthenticated User Enumeration via Email Verification Endpoint

published 3d ago modified 17h ago also GHSA-449m-g56j-h8hj , EUVD-2026-131852

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository LibreChat-AI/LibreChat. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 57%
public exploits
0
none known

Summary

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.

Patch / fix

Is CVE-2026-54046 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
partial
Assessed
18h ago

Exploit prediction

0.81% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-21).

Exploits and checks

  • github.com https://github.com/LibreChat-AI/LibreChat/security/advisories/GHSA-449m-g56j-h8hj referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected products

  • LibreChat-AI LibreChat

Classification

Weakness
  • CWE-203 Observable Discrepancy
  • CWE-799 Improper Control of Interaction Frequency

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of LibreChat-AI/LibreChat published their own advisory on GitHub. Reviewed sources take precedence over it.