# CVE-2024-52787: libre-chat Path Traversal vulnerability

> Attackers can execute path traversal via crafted filenames in the upload_documents method of libre-chat, potentially reading or modifying arbitrary files.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Nov 2024
- **Updated:** 27 Nov 2024
- **Also known as:** GHSA-3864-rp2m-2qfj, PYSEC-2026-1537

## What is CVE-2024-52787?

CVE-2024-52787 is a critical path traversal vulnerability in n/a, published on 25 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in the upload_documents method of libre-chat v0.0.6 allows attackers to execute a path traversal via supplying a crafted filename in an uploaded file.

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

## Which versions are affected by CVE-2024-52787?

3 open source packages ship an affected version, including libre-chat.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libre-chat` | PyPI | All versions to 0.0.6 | None |
| `libre-chat` | PyPI | All versions to 0.0.6 | None |
| `libre-chat` | PyPI | All versions to 0.0.6 | None |

## How do I fix CVE-2024-52787?

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

## Is CVE-2024-52787 being exploited?

There is no known exploitation of CVE-2024-52787 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-52787 and fix it if it is affected.

What it is: CVE-2024-52787 is a critical path traversal vulnerability in n/a, published on 25 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-52787 in the wild and no public exploit code.

Affected packages and fixed versions:
- libre-chat (PyPI): affected all versions up to 0.0.6; no fix listed
- libre-chat (PyPI): affected all versions up to 0.0.6; no fix listed
- libre-chat (PyPI): affected all versions up to 0.0.6; no fix listed

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-2024-52787/ (Markdown: https://insights.sbomify.com/CVE-2024-52787/index.md)
```

## Sources

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

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