LibreChat cross-user message injection in message API
- Exploited
- No known exploitation
- Fix
- Fixed in 0.8.6
- Who is exposed
- Not reported
Summary
LibreChat, a self-hosted chat application that supports multiple AI providers, has a flaw in its message API where a logged-in user can store a message in another user's conversation. The attacker can reach it remotely with a low-privilege account and no action from the victim, and the result is that content they write gets placed into the victim's conversation.
Written by a model
Original description
LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. Prior to 0.8.6, POST /api/messages/:conversationId authorizes req.params.conversationId in api/server/middleware/validateMessageReq.js but persists attacker-controlled req.body.conversationId through api/server/routes/messages.js. An authenticated attacker can use an owned conversation in the URL while naming a victim conversation in the body, causing an attacker-controlled message to be stored in the victim conversation. 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-54026 (LibreChat: Cross-User Message Injection via Parameter Confusion), 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-54026 (entry last updated 2026-11-20):
Affected:
- LibreChat-AI 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-54026 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-54026 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-7w78-4qpx-xhfg
- https://github.com/LibreChat-AI/LibreChat/pull/13183
- https://github.com/LibreChat-AI/LibreChat/commit/5b66196f5839e304699f0b54d76bf631a406dad5
- 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-54026
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-54026"}.Affected versions
- LibreChat-AI LibreChatfixed in 0.8.6
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.5/10CVSS 6.5
- 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 29 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 2Establishes: Affected and fixed versions. | |
| Advisory | GitHub · LibreChat-AI/LibreChat · Advisory GHSA-7w78-4qpx-xhfg |
| Link | librechat.ai · changelog/v0.8.6 |
| CVE record 1Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-54026 |
| Other links 3 | |
| Repository | GitHub · LibreChat-AI/LibreChat · Pull request #13183 |
| Repository | GitHub · LibreChat-AI/LibreChat · Commit 5b66196f |
| Repository | GitHub · LibreChat-AI/LibreChat · Release v0.8.6 |
Questions about CVE-2026-54026
Is CVE-2026-54026 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-54026?
LibreChat: before 0.8.6.
Source: cve.now feed data
How do I fix CVE-2026-54026?
Upgrade to a fixed version: 0.8.6.
Source: cve.now feed data
Related
- CVE-2026-54044LibreChat: Shared-Agent Editor Can Exfiltrate Owner Action API Keys via OpenAPI Spec Swap
- 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-54046LibreChat: Unauthenticated User Enumeration via Email Verification Endpoint
- CVE-2026-124768Multiple Vulnerabilities in XOne's XOneManager
- CVE-2026-133663flowintel Insecure Direct Object Reference Allows Cross-Case Data Access and Modification
No corrections so far. Something wrong on this page? Report an error.