Vulnerability in LibreChat (CVE-2026-54036)
Summary
Vulnerability in LibreChat (CVE-2026-54036). Data can be tampered with by attackers. Exploitable via GET /api/auth/2fa/enable. Mitigation: upgrade to 0.8.4-rc1 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.4-rc1, the GET /api/auth/2fa/enable endpoint can be called by an authenticated user (or attacker with a stolen session) even when 2FA is already fully enabled on the account. This endpoint overwrites the existing TOTP secret, generates new backup codes, and sets twoFactorEnabled to false — all without requiring any TOTP or backup code verification. An attacker with a valid session token can completely take over a victim's 2FA, locking the legitimate user out of their own two-factor authentication. This vulnerability is fixed in 0.8.4-rc1.
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-54036 has been found in LibreChat.
Attackers can target a specific entry point like GET /api/auth/2fa/enable over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 5.3/10.
What to do: upgrade LibreChat to 0.8.4-rc1 or later.
If unsure, ask your IT team or search "LibreChat CVE-2026-54036" on the vendor's site.
CVE-2026-54036 (LibreChat) — CWE-306 / CVSS v3 5.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/auth/2fa/enable
Patched: 0.8.4-rc1 — 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-306) exists in LibreChat. Attackers reach the vulnerable code path via GET /api/auth/2fa/enable.
Check the vendor advisory for the affected versions of LibreChat. Attack surface: GET /api/auth/2fa/enable.
Severity: Medium (CVSS 5.3/10). Data can be tampered with by attackers.
Update to 0.8.4-rc1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/auth/2fa/enable requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/auth/2fa/enable' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/auth/2fa/enableへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade LibreChat to 0.8.4-rc1ステージング環境で 0.8.4-rc1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/auth/2fa/enable on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- exploit github.com