Vulnerability in LibreChat (CVE-2026-54030)
Summary
Vulnerability in LibreChat (CVE-2026-54030). Confidential information can be exposed externally. Mitigation: upgrade to 0.8.5 or later.
Original description
The description as published by the source.
LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. Prior to 0.8.5, LibreChat's MCP OAuth implementation does not validate that the resource parameter from OAuth Protected Resource metadata (RFC 9728) matches the configured MCP server URL, allowing a malicious MCP server to steal access tokens intended for a legitimate server. This vulnerability is fixed in 0.8.5.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54030 has been found in LibreChat.
Confidential information can be exposed externally. CVSS score: 8.0/10.
What to do: upgrade LibreChat to 0.8.5 or later.
If unsure, ask your IT team or search "LibreChat CVE-2026-54030" on the vendor's site.
CVE-2026-54030 (LibreChat) — CWE-346 / CVSS v3 8.0
Attack vector: remote (network-reachable) / unauthenticated
Patched: 0.8.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-346) exists in LibreChat.
Check the vendor advisory for the affected versions of LibreChat.
Severity: High (CVSS 8.0/10). Confidential information can be exposed externally.
Update to 0.8.5.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'LibreChat' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'LibreChat' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
LibreChatを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade LibreChat to 0.8.5ステージング環境で 0.8.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- exploit github.com