CVE-2026-54043
LibreChat chat attachments could read another owner’s file
LibreChat-AI · LibreChat
First documented disclosure · Review checkpoint
Summary
A known file identifier could attach another user’s extracted document text.
Severity and exploitation evidence
Medium · 6.3/10 · CVSS 3.1. Severity source.
Exploitation not established: Public evidence describes a weakness, source correction or controlled demonstration; malicious exploitation against users is not established.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
File-usage lookup/update filters by file_id without request-owner scope.
Conditions required
Authenticated attacker knows a victim file_id, for example from a publicly shared conversation.
Potential impact
Victim text can enter attacker model context; expiration metadata is also removed.
Affected versions and configurations
Before 0.8.7.
Fix and mitigation status
0.8.7.
Practical next steps
Upgrade to 0.8.7 or later and verify the deployed application image includes the correction.
Operating lesson
Scope file retrieval and retention changes to the authenticated owner.
Evidence and limits
Distinct from earlier shared-link sanitization; the vulnerable boundary is the later file lookup/update.0.8.7-rc1 also contains the fix. CNA publication 2026-11-20 is distinct from the earliest reviewed public source. GitHub_M assessment: CVSS 3.1 6.3.
Sources
- GitHub_M CVE authority record
Primary source ·
- LibreChat original advisory
Primary source ·
- Public corrective change
Primary source ·