← Back
CVE-2026-54029
medium
CVSS 5.3
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**A vulnerability** (CWE-862) exists in librechat. Attackers reach the vulnerable code path via `DELETE /api/messages/` without authentication.
📍 Affected scope
librechat — . Attack surface: DELETE /api/messages/.
🔥 Severity
Severity: Medium (CVSS 5.3/10). Data can be tampered with by attackers
🔧 How to fix
Update to **0.8.4-rc1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
3Hunt 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 があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade librechat to 0.8.4-rc1ステージング環境で 0.8.4-rc1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against DELETE /api/messages/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
References
- exploit [email protected]