cve.bz

CVE-2026-54031 LibreChat: MCP OAuth requests can follow redirects to internal URLs after SSRF validation

6.3 medium

Medium (6.3) in librechat-ai librechat.

On this page
LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. Prior to 0.8.8, packages/api/src/mcp/oauth/handler.ts createOAuthFetch validates only the initial destination for MCP OAuth discovery, registration, token, refresh, and revocation requests, then uses redirect-following fetch behavior without validating each redirect target. An attacker who can initiate MCP OAuth against a controlled endpoint can redirect server requests to internal or private addresses, reaching services that the initial SSRF checks should block. The separate MCP transport path already validates redirects and is not affected. This issue is fixed in version 0.8.8.

Severity

CVSS 3.1

6.3 medium
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Assigned by
GitHub_M (CNA)
NVD analysis
Not in the NVD yet
Record from
the CVE List, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-54031 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-54031?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-54031?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-54031 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
LibreChat-AI LibreChat< 0.8.8

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON