CVE-2026-31943: danny-avila LibreChat · Server-Side Request Forgery (SSRF)
Affects danny-avila LibreChatSource CVE Database V5
Not known to be exploited · CVSS 8.5 High : upgrade to 0.8.3 soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.8.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.
What to do
Upgrade LibreChat and danny-avila/LibreChat to 0.8.3.
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
A patch is available in LibreChat version 0.8.3 that fixes the SSRF vulnerability by correctly detecting IPv4-mapped IPv6 addresses. Users should upgrade to version 0.8.3 or later to remediate this issue. There is no indication that temporary mitigations or workarounds are provided by the vendor. Since this is not a cloud-hosted service, remediation depends on applying the official fix.
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.