CVE-2026-54026
LibreChat message writes trusted an unauthorized conversation identifier
LibreChat-AI · LibreChat
First documented disclosure · Review checkpoint
Summary
Authenticated callers could inject messages into another user’s conversation.
Severity and exploitation evidence
Medium · 6.5/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
Authorization checks the URL conversation ID but persistence uses the request-body ID.
Conditions required
Authenticated attacker owns a conversation and knows a victim conversation identifier.
Potential impact
Cross-user conversation integrity loss; further data leakage/XSS is not established by the accepted scope.
Affected versions and configurations
Before 0.8.6.
Fix and mitigation status
0.8.6.
Practical next steps
Upgrade to 0.8.6 or later and verify the deployed application image includes the correction.
Operating lesson
Use the same authorized resource identifier for validation, reads and writes.
Evidence and limits
The public correction forces the URL ID and adds owner scoping; private discovery on May 13 is not the public disclosure date. CNA publication 2026-11-20 is distinct from the earliest reviewed public source. GitHub_M assessment: CVSS 3.1 6.5.
Sources
- GitHub_M CVE authority record
Primary source ·
- LibreChat original advisory
Primary source ·
- Public corrective change
Primary source ·