LibreChat unauthorized file access via chat attachment IDs
- Exploited
- No known exploitation
- Fix
- Fixed in 0.8.7
- Who is exposed
- Not reported
Summary
LibreChat, a self-hosted ChatGPT-style chat app, lets a logged-in attacker reach another user's uploaded file over the network by attaching it to a chat using its file ID, which can be obtained from a shared conversation. The attack can expose text extracted from the victim's document to the AI model and remove the file's expiration setting, and it requires a user to take some action.
Written by a model
Original description
LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. Prior to 0.8.7, packages/data-schemas/src/methods/file.ts updateFileUsage accepts chat attachment files[].file_id values without restricting the lookup to the authenticated owner. An authenticated attacker who obtains another user's file identifier, including through GET /api/share/{shareId} for a shared conversation, can attach that file to a chat, causing extracted document text to enter the model context. The same operation can remove expiration metadata from the victim file. 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-54043 (LibreChat: Unauthorized File Content Access via Chat Attachment file_id), 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-54043 (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-54043 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-54043 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-wwj3-x5mw-wq7x
- https://github.com/LibreChat-AI/LibreChat/pull/13557
- https://github.com/LibreChat-AI/LibreChat/commit/75bbefb1c8561328eb8372e1a6ca94fc66ebcb45
- 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-54043
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-54043"}.Affected versions
- LibreChat-AI LibreChatfixed in 0.8.7
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.3/10CVSS 6.3
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 7
| Kind | Source |
|---|---|
| Vendor advisory 2Establishes: Affected and fixed versions. | |
| Advisory | GitHub · LibreChat-AI/LibreChat · Advisory GHSA-wwj3-x5mw-wq7x |
| Link | librechat.ai · changelog/v0.8.7 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-54043 |
| Record | NVD · CVE-2026-54043 |
| Other links 3 | |
| Repository | GitHub · LibreChat-AI/LibreChat · Pull request #13557 |
| Repository | GitHub · LibreChat-AI/LibreChat · Commit 75bbefb1 |
| Repository | GitHub · LibreChat-AI/LibreChat · Release v0.8.7 |
Questions about CVE-2026-54043
Is CVE-2026-54043 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-54043?
LibreChat: before 0.8.7.
Source: cve.now feed data
How do I fix CVE-2026-54043?
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-54046LibreChat: Unauthenticated User Enumeration via Email Verification Endpoint
- CVE-2026-124768Multiple Vulnerabilities in XOne's XOneManager
No corrections so far. Something wrong on this page? Report an error.