Authenticated API-key overwrite via userId body override
Published Jun 2, 2026 · Updated Jun 2, 2026
Missing authorization in LibreChat 0.7.6 and earlier allows remote authenticated users to overwrite other users' API keys via PUT /api/keys. The keys route places req.body after the authenticated userId in an object spread, so a supplied userId replaces the trusted value before findOneAndUpdate. Any regular account can alter another user's provider-key configuration, redirect provider requests through an attacker-controlled key, or interrupt that functionality.
Summary
What happened
Missing authorization in LibreChat 0.7.6 and earlier allows remote authenticated users to overwrite other users' API keys via PUT /api/keys. The keys route places req.body after the authenticated userId in an object spread, so a supplied userId replaces the trusted value before findOneAndUpdate. Any regular account can alter another user's provider-key configuration, redirect provider requests through an attacker-controlled key, or interrupt that functionality.
The record
- CVE
- CVE-2026-31942
- Published
- Jun 2, 2026
- Updated
- Jun 2, 2026
- Vendor
- Danny Avila
- Product
- LibreChat
- Classifications
- CWE-862
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 2, 2026CVE publishedPublication date reported by the CVE source.
- Jun 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.8.3-rc1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-5jcj-rh68-cgj7 attack scenarioproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo