LibreChat plaintext password exposure in login error logs
- Exploited
- No known exploitation
- Fix
- Fixed in 0.8.6
- Who is exposed
- Not reported
Summary
LibreChat writes the plaintext password from a failed login attempt into its logs, so anyone who can read the application's output or error logs can recover that password. A remote attacker can trigger the failure without logging in by sending a direct invalid login request, though the normal browser form makes this less likely.
Written by a model
Original description
LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. Prior to 0.8.6, the POST /api/auth/login local-login validation path in api/strategies/localStrategy.js logs req.body, including the submitted plaintext password, during a Zod validation failure. The standard browser form validation makes this path less likely through the normal interface, but a direct invalid login request can reach it, and the logging formatter does not redact the password stored in metadata. A principal with access to application stdout, error logs, or journal output can recover the submitted credential. This issue is fixed in version 0.8.6.
What to do
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-54041 (LibreChat: Plaintext password logged on login validation error), 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-54041 (entry last updated 2026-11-20):
Affected:
- danny-avila LibreChat: fixed in 0.8.6
Fixed versions: 0.8.6.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-54041 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-54041 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-63w5-cp9j-q463
- https://github.com/LibreChat-AI/LibreChat/pull/12926
- https://github.com/LibreChat-AI/LibreChat/commit/85fa881e3c36c0bb1bdc6b08655a493eca40eb36
- 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-54041
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-54041"}.Affected versions
- danny-avila LibreChatfixed in 0.8.6
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity3.1/10CVSS 3.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 25 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-63w5-cp9j-q463 |
| Link | librechat.ai · changelog/v0.8.6 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-54041 |
| Record | NVD · CVE-2026-54041 |
| Other links 3 | |
| Repository | GitHub · LibreChat-AI/LibreChat · Pull request #12926 |
| Repository | GitHub · LibreChat-AI/LibreChat · Commit 85fa881e |
| Repository | GitHub · LibreChat-AI/LibreChat · Release v0.8.6 |
Questions about CVE-2026-54041
Is CVE-2026-54041 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-54041?
LibreChat: before 0.8.6.
Source: cve.now feed data
How do I fix CVE-2026-54041?
Upgrade to a fixed version: 0.8.6.
Source: cve.now feed data
Related
- CVE-2026-32625LibreChat Exfiltrates Server Secrets via MCP Server URL Injection
- CVE-2026-54039LibreChat: Pre-registration account takeover via attacker-controlled `provider` field and social-login email fallback
- 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
No corrections so far. Something wrong on this page? Report an error.