LibreChat is a ChatGPT clone with additional features. From 0.8.2 to 0.8.2-rc3, The MCP (Model Context Protocol) OAuth callback endpoint accepts the redirect from the identity provider and stores OAuth tokens for the user who initiated the flow, without verifying that the browser hitting the redirect URL is logged in or that the logged-in user matches the initiator. An attacker can send the authorization URL to a victim; when the victim completes the flow, the victim’s OAuth tokens are stored on the attacker’s LibreChat account, enabling account takeover of the victim’s MCP-linked services (e.g. Atlassian, Outlook). This vulnerability is fixed in 0.8.3-rc1.
CVE-2026-31944
This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.6
- EG Score
- 7.6(low)
- EG Risk
- 39(Track)EG Risk 39/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity76% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 16%
- KEV
- Not listed
Published
March 13, 2026
Last Modified
June 17, 2026
References (1)
- security-advisories@githubhttps://github.com/danny-avila/LibreChat/security/advisories/GHSA-vf7j-7mrx-hp7g
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 1× in last 7d / 1× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 13:38 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-306
- CVE-2011-10013EG 10.0CRITICAL
- CVE-2014-125124EG 10.0CRITICAL
- CVE-2017-2637EG 10.0EPSS p91CRITICAL
- CVE-2010-5326EG 10.0 KEVEPSS p97CRITICAL
- CVE-2007-0956EG 10.0EPSS p98HIGH
- CVE-2017-12822EG 9.9CRITICAL
- CVE-2016-8355EG 9.9CRITICAL
- CVE-2012-10030EG 9.8CRITICAL
- CVE-2014-3449EG 9.8CRITICAL
- CVE-2006-0062EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-31944?
When was CVE-2026-31944 disclosed?
Is CVE-2026-31944 actively exploited?
What is the CVSS score of CVE-2026-31944?
How do I remediate CVE-2026-31944?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-31944
Is Your Infrastructure Affected by CVE-2026-31944?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.