Path Traversal in LibreChat (CVE-2026-34371)
Summary
Path traversal in LibreChat (CVE-2026-34371). Data can be tampered with by attackers. Mitigation: upgrade to 0.8.4 or later.
Original description
The description as published by the source.
LibreChat is a ChatGPT clone with additional features. Prior to 0.8.4, LibreChat trusts the name field returned by the execute_code sandbox when persisting code-generated artifacts. On deployments using the default local file strategy, a malicious artifact filename containing traversal sequences (for example, ../../../../../app/client/dist/poc.txt) is concatenated into the server-side destination path and written with fs.writeFileSync() without sanitization. This gives any user who can trigger execute_code an arbitrary file write primitive as the LibreChat server user. This vulnerability is fixed in 0.8.4.
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-34371 has been found in LibreChat.
Data can be tampered with by attackers. CVSS score: 6.3/10.
What to do: upgrade LibreChat to 0.8.4 or later.
If unsure, ask your IT team or search "LibreChat CVE-2026-34371" on the vendor's site.
CVE-2026-34371 (LibreChat) — CWE-22 / CVSS v3 6.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.8.4 — 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.
Path traversal (CWE-22) exists in LibreChat.
Check the vendor advisory for the affected versions of LibreChat.
Severity: Medium (CVSS 6.3/10). Data can be tampered with by attackers.
Update to 0.8.4.
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.4ステージング環境で 0.8.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- exploit github.com