Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-22252: CWE-285: Improper Authorization in danny-avila LibreChat

0
Critical
VulnerabilityCVE-2026-22252cvecve-2026-22252cwe-285
Published: Mon Jan 12 2026 (01/12/2026, 18:01:48 UTC)
Source: CVE Database V5
Vendor/Project: danny-avila
Product: LibreChat

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.

AI-Powered Analysis

AILast updated: 01/12/2026, 18:38:14 UTC

Technical Analysis

CVE-2026-22252 is a critical security vulnerability identified in the LibreChat project, a ChatGPT clone with extended features. The vulnerability stems from improper authorization (CWE-285) in the MCP stdio transport mechanism prior to version v0.8.2-rc2. Specifically, this component accepts arbitrary shell commands from authenticated users without validating their legitimacy or permissions. As a result, any user with authentication credentials can execute arbitrary shell commands as the root user inside the container hosting LibreChat. This is achieved through a single crafted API request, making exploitation straightforward and highly impactful. The vulnerability affects all versions before v0.8.2-rc2 and has a CVSS v3.1 score of 9.1, reflecting its critical severity. The attack vector is network-based with low attack complexity, requiring only privileges of an authenticated user but no user interaction. The scope is changed as the vulnerability allows container root-level command execution, potentially leading to full system compromise if container breakout is possible. Although no known exploits are reported in the wild yet, the ease of exploitation and high privileges granted make this a significant threat. The vulnerability is fixed in LibreChat v0.8.2-rc2 by implementing proper command validation and authorization checks in the MCP stdio transport. Organizations running vulnerable versions should prioritize patching to prevent potential compromise.

Potential Impact

The impact on European organizations is substantial due to the ability of an authenticated user to execute arbitrary root-level commands inside the container. This can lead to full compromise of the LibreChat container environment, including data theft, service disruption, and lateral movement within the network if container breakout vulnerabilities exist. Confidentiality is at high risk as attackers can access sensitive chat data and potentially other containerized services. Integrity is compromised since attackers can modify or delete data and system files. Availability is also threatened as attackers can disrupt or disable the LibreChat service or the host container. Given the increasing adoption of AI chatbots and containerized applications in Europe, organizations using LibreChat without patching are vulnerable to targeted attacks or insider threats exploiting this flaw. The vulnerability's network accessibility and low complexity increase the risk of exploitation in multi-tenant or cloud environments common in European enterprises.

Mitigation Recommendations

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.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-07T05:19:12.921Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69653c31da2266e838f5b98a

Added to database: 1/12/2026, 6:23:45 PM

Last enriched: 1/12/2026, 6:38:14 PM

Last updated: 1/13/2026, 7:09:26 AM

Views: 11

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats