Vulnerability in LibreChat (CVE-2026-54029)
Summary
Vulnerability in LibreChat (CVE-2026-54029). Data can be tampered with by attackers. Exploitable via DELETE /api/messages/. 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 DELETE /api/messages/:conversationId/:messageId endpoint allows any authenticated user to delete any other user's messages. The validateMessageReq middleware only validates that the conversationId belongs to the requesting user, but the handler calls deleteMessages({ messageId }) using only the messageId as the MongoDB filter — without adding a user constraint. An attacker provides their own valid conversationId (to pass validation) and the victim's messageId (to target deletion), resulting in permanent, irrecoverable message deletion. 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-54029 has been found in LibreChat.
Attackers can target a specific entry point like DELETE /api/messages/ 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-54029" on the vendor's site.
CVE-2026-54029 (LibreChat) — CWE-862 / CVSS v3 5.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: DELETE /api/messages/
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-862) exists in LibreChat. Attackers reach the vulnerable code path via DELETE /api/messages/.
Check the vendor advisory for the affected versions of LibreChat. Attack surface: DELETE /api/messages/.
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 DELETE /api/messages/ 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 'DELETE /api/messages/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
DELETE /api/messages/への異常なリクエスト (不正な認証ヘッダ・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 DELETE /api/messages/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- exploit security-advisories@github.com