CVE-2026-22252: danny-avila LibreChat · Improper Authorization
Affects danny-avila LibreChatSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical : upgrade to 0.8.2-rc2 as a priority.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 4.2% chance of exploitation in 30 days – higher than 90% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.8.2-rc2
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade danny-avila LibreChat to 0.8.2-rc2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| danny-avilaLibreChat | Affected
| Fixed in
|
GitHubdanny-avila/LibreChatpkg:github/danny-avila/LibreChatOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediate upgrade to LibreChat version v0.8.2-rc2 or later, which contains the fix for this vulnerability. 2. Restrict access to the MCP stdio transport API to trusted and minimal user groups to reduce the attack surface. 3. Implement strong authentication and authorization controls around LibreChat deployments, ensuring only fully trusted users have access. 4. Monitor API usage logs for unusual or suspicious command execution attempts indicative of exploitation. 5. Employ container security best practices such as running containers with least privilege, using container runtime security tools, and isolating LibreChat containers from critical infrastructure. 6. Conduct regular vulnerability scanning and penetration testing focusing on containerized AI/chatbot services. 7. Educate administrators and developers on secure deployment and update practices for LibreChat and similar AI tools. 8. If immediate patching is not possible, consider disabling or restricting the MCP stdio transport feature until patched.
Description
LibreChat is a ChatGPT clone with additional features. Prior to v0.8.2-rc2, LibreChat's MCP stdio transport accepts arbitrary commands without validation, allowing any authenticated user to execute shell commands as root inside the container through a single API request. This vulnerability is fixed in v0.8.2-rc2.