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-2025-69222: CWE-918: Server-Side Request Forgery (SSRF) in danny-avila LibreChat

0
Critical
VulnerabilityCVE-2025-69222cvecve-2025-69222cwe-918
Published: Wed Jan 07 2026 (01/07/2026, 21:17:17 UTC)
Source: CVE Database V5
Vendor/Project: danny-avila
Product: LibreChat

Description

LibreChat is a ChatGPT clone with additional features. Version 0.8.1-rc2 is prone to a server-side request forgery (SSRF) vulnerability due to missing restrictions of the Actions feature in the default configuration. LibreChat enables users to configure agents with predefined instructions and actions that can interact with remote services via OpenAPI specifications, supporting various HTTP methods, parameters, and authentication methods including custom headers. By default, there are no restrictions on accessible services, which means agents can also access internal components like the RAG API included in the default Docker Compose setup. This issue is fixed in version 0.8.1-rc2.

AI-Powered Analysis

AILast updated: 01/07/2026, 21:47:45 UTC

Technical Analysis

CVE-2025-69222 is a Server-Side Request Forgery (SSRF) vulnerability classified under CWE-918, affecting the LibreChat open-source ChatGPT clone developed by danny-avila. The vulnerability exists in versions 0.8.1-rc2 and 0.8.2-rc2 due to the default configuration of the Actions feature, which allows agents configured with predefined instructions to perform HTTP requests to remote services using OpenAPI specifications. This feature supports various HTTP methods, parameters, and authentication mechanisms, including custom headers, but lacks restrictions on which services can be accessed. Consequently, an attacker with at least limited privileges can exploit this to send crafted requests to internal services, such as the Retrieval-Augmented Generation (RAG) API included in the default Docker Compose setup. This can lead to unauthorized internal network access, data exposure, and potential partial denial of service. The vulnerability has a CVSS v3.1 score of 9.1 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L), indicating network exploitable with low attack complexity, requiring privileges but no user interaction, and causing high confidentiality impact, partial integrity, and availability impacts with scope change. The issue was publicly disclosed in early 2026 and fixed in versions beyond 0.8.2-rc2. No known exploits have been reported in the wild yet, but the nature of the vulnerability makes it a high-risk target for attackers aiming to pivot within internal networks or exfiltrate sensitive data.

Potential Impact

For European organizations, this SSRF vulnerability poses significant risks, especially for those deploying LibreChat in environments with sensitive internal APIs or data. Exploitation could allow attackers to bypass perimeter defenses and access internal services not intended to be exposed externally, leading to data breaches, intellectual property theft, or disruption of AI services. Given the integration of LibreChat with AI workflows, compromised internal APIs could also lead to manipulation of AI outputs or leakage of proprietary training data. The vulnerability’s ability to cause partial denial of service further threatens availability of critical AI-driven communication platforms. Organizations relying on default configurations without network segmentation or strict access controls are particularly vulnerable. The risk is amplified in sectors with high AI adoption such as finance, healthcare, and research institutions prevalent in Europe. Additionally, the vulnerability could be leveraged in multi-stage attacks targeting cloud-hosted AI services or hybrid on-premises/cloud deployments common in European enterprises.

Mitigation Recommendations

To mitigate this vulnerability, organizations should immediately upgrade LibreChat to versions later than 0.8.2-rc2 where the issue is fixed. Beyond patching, it is critical to implement strict network segmentation to isolate internal APIs like the RAG API from agents and external-facing components. Configure the Actions feature to whitelist only trusted external services and restrict HTTP methods and headers to the minimum necessary. Employ robust authentication and authorization controls on all internal APIs to prevent unauthorized access even if SSRF attempts occur. Monitor network traffic for unusual internal requests originating from LibreChat agents. Conduct regular security audits and penetration tests focusing on SSRF and internal service exposure. Additionally, consider deploying Web Application Firewalls (WAFs) with SSRF detection capabilities and enforce least privilege principles for users configuring agents. Finally, educate developers and administrators about secure configuration practices for AI platforms and the risks of SSRF.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-12-29T19:03:19.357Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 695ed0f72efadb62cf84560f

Added to database: 1/7/2026, 9:32:39 PM

Last enriched: 1/7/2026, 9:47:45 PM

Last updated: 1/9/2026, 12:01:17 AM

Views: 17

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