# CVE-2026-34371: LibreChat Affected by Arbitrary File Write via `execute_code` Artifact Filename Traversal

> Attackers can write arbitrary files via path traversal in artifact filenames, potentially leading to code execution or data modification.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-qrm5-r67f-6692

## What is CVE-2026-34371?

CVE-2026-34371 is a medium-severity path traversal vulnerability in Librechat Librechat, published on 7 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-34371?

It affects 1 product.


Products: Librechat Librechat.

## How do I fix CVE-2026-34371?

No fix has been published for CVE-2026-34371 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-34371 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34371 exists.

## Other vulnerabilities in Librechat Librechat

- [CVE-2026-32625](https://insights.sbomify.com/CVE-2026-32625/): LibreChat Exfiltrates Server Secrets via MCP Server URL Injection (critical 9.6)
- [CVE-2024-11167](https://insights.sbomify.com/CVE-2024-11167/): Improper Access Control in danny-avila/librechat (critical 9.4)
- [CVE-2026-22252](https://insights.sbomify.com/CVE-2026-22252/): LibreChat MCP Stdio Remote Command Execution (critical 9.1)
- [CVE-2025-69222](https://insights.sbomify.com/CVE-2025-69222/): LibreChat is vulnerable to Server-Side Request Forgery due to missing restrictions (critical 9.1)
- [CVE-2024-41704](https://insights.sbomify.com/CVE-2024-41704/): Path traversal in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-34371 and fix it if it is affected.

What it is: CVE-2026-34371 is a medium-severity path traversal vulnerability in Librechat Librechat, published on 7 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34371 exists.

Affected product: Librechat Librechat. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-34371/ (Markdown: https://insights.sbomify.com/CVE-2026-34371/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-34371
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-34371
- OSV: https://osv.dev/vulnerability/CVE-2026-34371

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-34371/
Summaries are generated and may contain mistakes; the official description above is the record.