Skip to main content
VulnerabilityPublished

CVE-2026-54023: LibreChat · Information Exposure

Affects LibreChatSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.0 Medium : upgrade to 0.8.6 when convenient.

Data as of 20 Nov 2026, 20:30 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.06.0
Patch
Available – fixed in 0.8.6
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade LibreChat to 0.8.6.

Affected software

ProductAffectedFixed in
LibreChat-AILibreChatAffected
  • >=0.8.5 <0.8.6
Fixed in
  • 0.8.6

AI-suggested

Upgrade LibreChat to version 0.8.6 or later, where this vulnerability is fixed. No additional mitigation is required once the update is applied.

Description

A vulnerability in LibreChat versions 0.8.5 up to but not including 0.8.6 allows exposure of sensitive OAuth tokens to authenticated users via the GET /api/user endpoint. This occurs because response sanitization was not applied, enabling browser scripts to access OAuth access, ID, and refresh tokens that should remain server-side. The issue is fixed in version 0.8.6.

References

Community reviews

Loading reviews…