CVE-2026-31943: CWE-918: Server-Side Request Forgery (SSRF) in danny-avila LibreChat
LibreChat is a ChatGPT clone with additional features. Prior to version 0.8.3, `isPrivateIP()` in `packages/api/src/auth/domain.ts` fails to detect IPv4-mapped IPv6 addresses in their hex-normalized form, allowing any authenticated user to bypass SSRF protection and make the server issue HTTP requests to internal network resources — including cloud metadata services (e.g., AWS `169.254.169.254`), loopback, and RFC1918 ranges. Version 0.8.3 fixes the issue.
AI Analysis
Technical Summary
CVE-2026-31943 is a Server-Side Request Forgery (SSRF) vulnerability identified in the LibreChat project, a ChatGPT clone with extended features. The root cause lies in the isPrivateIP() function located in packages/api/src/auth/domain.ts, which is responsible for preventing SSRF attacks by blocking requests to private or internal IP addresses. However, prior to version 0.8.3, this function fails to recognize IPv4-mapped IPv6 addresses when they are presented in their hex-normalized form. This oversight allows any authenticated user to bypass the SSRF protection mechanism. Consequently, an attacker can trick the server into issuing HTTP requests to internal network endpoints that are normally inaccessible externally. These endpoints include critical infrastructure such as cloud provider metadata services (e.g., AWS at 169.254.169.254), localhost (loopback) addresses, and private IP ranges defined by RFC1918. Access to cloud metadata services can enable attackers to retrieve sensitive credentials or configuration data, potentially leading to further compromise. The vulnerability has a CVSS v3.1 score of 8.5, reflecting its high severity due to network attack vector, low attack complexity, required privileges (authenticated user), no user interaction, and a scope change with high confidentiality impact. No known exploits are reported in the wild yet. The issue was publicly disclosed on March 27, 2026, and fixed in LibreChat version 0.8.3. Users of affected versions are strongly advised to upgrade to the patched release to remediate the vulnerability.
Potential Impact
The exploitation of this SSRF vulnerability can have significant impacts on organizations using vulnerable LibreChat versions. Attackers with valid authentication can leverage the flaw to access internal network resources that are otherwise protected, including cloud metadata services. This can lead to unauthorized disclosure of sensitive information such as cloud instance credentials, internal APIs, and configuration data, severely compromising confidentiality. Integrity may be partially affected if attackers use retrieved credentials to pivot or escalate privileges within the network. Availability impact is minimal as the vulnerability does not directly enable denial-of-service conditions. Given the potential to access critical internal services and sensitive data, the overall risk is high. Organizations relying on LibreChat for internal or external chatbot services, especially those hosted in cloud environments, face increased risk of lateral movement and data breaches if unpatched. The requirement for authentication limits exposure somewhat but does not eliminate risk, especially in environments with many users or weak authentication controls.
Mitigation Recommendations
To mitigate CVE-2026-31943, organizations should immediately upgrade LibreChat to version 0.8.3 or later, where the isPrivateIP() function correctly detects IPv4-mapped IPv6 addresses and enforces SSRF protections. Additionally, organizations should implement strict network segmentation and firewall rules to limit server access to sensitive internal resources and cloud metadata endpoints. Employing network-level egress filtering can prevent unauthorized outbound requests from application servers. Monitoring and logging HTTP requests originating from LibreChat servers can help detect anomalous SSRF attempts. Enforce strong authentication and least privilege principles to reduce the number of users who can exploit this vulnerability. If upgrading is temporarily not possible, consider disabling or restricting features that allow user-controlled URLs or requests within LibreChat. Conduct regular security assessments and penetration testing focused on SSRF vectors to identify and remediate similar issues proactively.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, France, Netherlands, Japan, South Korea, India
CVE-2026-31943: CWE-918: Server-Side Request Forgery (SSRF) in danny-avila LibreChat
Description
LibreChat is a ChatGPT clone with additional features. Prior to version 0.8.3, `isPrivateIP()` in `packages/api/src/auth/domain.ts` fails to detect IPv4-mapped IPv6 addresses in their hex-normalized form, allowing any authenticated user to bypass SSRF protection and make the server issue HTTP requests to internal network resources — including cloud metadata services (e.g., AWS `169.254.169.254`), loopback, and RFC1918 ranges. Version 0.8.3 fixes the issue.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-31943 is a Server-Side Request Forgery (SSRF) vulnerability identified in the LibreChat project, a ChatGPT clone with extended features. The root cause lies in the isPrivateIP() function located in packages/api/src/auth/domain.ts, which is responsible for preventing SSRF attacks by blocking requests to private or internal IP addresses. However, prior to version 0.8.3, this function fails to recognize IPv4-mapped IPv6 addresses when they are presented in their hex-normalized form. This oversight allows any authenticated user to bypass the SSRF protection mechanism. Consequently, an attacker can trick the server into issuing HTTP requests to internal network endpoints that are normally inaccessible externally. These endpoints include critical infrastructure such as cloud provider metadata services (e.g., AWS at 169.254.169.254), localhost (loopback) addresses, and private IP ranges defined by RFC1918. Access to cloud metadata services can enable attackers to retrieve sensitive credentials or configuration data, potentially leading to further compromise. The vulnerability has a CVSS v3.1 score of 8.5, reflecting its high severity due to network attack vector, low attack complexity, required privileges (authenticated user), no user interaction, and a scope change with high confidentiality impact. No known exploits are reported in the wild yet. The issue was publicly disclosed on March 27, 2026, and fixed in LibreChat version 0.8.3. Users of affected versions are strongly advised to upgrade to the patched release to remediate the vulnerability.
Potential Impact
The exploitation of this SSRF vulnerability can have significant impacts on organizations using vulnerable LibreChat versions. Attackers with valid authentication can leverage the flaw to access internal network resources that are otherwise protected, including cloud metadata services. This can lead to unauthorized disclosure of sensitive information such as cloud instance credentials, internal APIs, and configuration data, severely compromising confidentiality. Integrity may be partially affected if attackers use retrieved credentials to pivot or escalate privileges within the network. Availability impact is minimal as the vulnerability does not directly enable denial-of-service conditions. Given the potential to access critical internal services and sensitive data, the overall risk is high. Organizations relying on LibreChat for internal or external chatbot services, especially those hosted in cloud environments, face increased risk of lateral movement and data breaches if unpatched. The requirement for authentication limits exposure somewhat but does not eliminate risk, especially in environments with many users or weak authentication controls.
Mitigation Recommendations
To mitigate CVE-2026-31943, organizations should immediately upgrade LibreChat to version 0.8.3 or later, where the isPrivateIP() function correctly detects IPv4-mapped IPv6 addresses and enforces SSRF protections. Additionally, organizations should implement strict network segmentation and firewall rules to limit server access to sensitive internal resources and cloud metadata endpoints. Employing network-level egress filtering can prevent unauthorized outbound requests from application servers. Monitoring and logging HTTP requests originating from LibreChat servers can help detect anomalous SSRF attempts. Enforce strong authentication and least privilege principles to reduce the number of users who can exploit this vulnerability. If upgrading is temporarily not possible, consider disabling or restricting features that allow user-controlled URLs or requests within LibreChat. Conduct regular security assessments and penetration testing focused on SSRF vectors to identify and remediate similar issues proactively.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-10T15:10:10.656Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69c6de373c064ed76fea1d62
Added to database: 3/27/2026, 7:44:55 PM
Last enriched: 3/27/2026, 8:00:15 PM
Last updated: 3/28/2026, 1:00:57 AM
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.