# CVE-2023-3765: Absolute Path Traversal in mlflow/mlflow

> An absolute path traversal vulnerability in MLflow allows attackers to read arbitrary files from the server filesystem.

- **Severity:** Critical 10.0 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jul 2023
- **Updated:** 24 Oct 2024
- **Also known as:** BIT-mlflow-2023-3765, GHSA-fmxj-6h9g-6vw3, PYSEC-2023-308

## What is CVE-2023-3765?

CVE-2023-3765 is a critical path traversal vulnerability in Lfprojects Mlflow, published on 19 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Absolute Path Traversal in GitHub repository mlflow/mlflow prior to 2.5.0.

Weakness: CWE-36 (Absolute Path Traversal)

## Which versions are affected by CVE-2023-3765?

4 open source packages ship an affected version, including mlflow. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mlflow` | Bitnami | All versions | 2.5.0 |
| `mlflow` | PyPI | All versions | 2.5.0 |
| `mlflow` | PyPI | All versions | 2.5.0 |
| `mlflow` | PyPI | All versions | 2.5.0 |

Products: Lfprojects Mlflow.

## How do I fix CVE-2023-3765?

Upgrade mlflow to 2.5.0 or later.

## Is CVE-2023-3765 being exploited?

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

Public exploit code:

- MLflow Absolute Path Traversal (nuclei): http/cves/2023/CVE-2023-3765.yaml

## Other vulnerabilities in Lfprojects Mlflow

- [CVE-2026-64849](https://insights.sbomify.com/CVE-2026-64849/): MLflow Server-Side Request Forgery (critical 9.3, exploited in the wild)
- [CVE-2025-15379](https://insights.sbomify.com/CVE-2025-15379/): Command Injection in mlflow/mlflow (critical 10.0)
- [CVE-2024-0520](https://insights.sbomify.com/CVE-2024-0520/): Remote Code Execution due to Full Controlled File Write in mlflow/mlflow (critical 10.0)
- [CVE-2023-6977](https://insights.sbomify.com/CVE-2023-6977/): Path Traversal: '\..\filename' (critical 10.0)
- [CVE-2023-6709](https://insights.sbomify.com/CVE-2023-6709/): Improper Neutralization of Special Elements Used in a Template Engine in mlflow/mlflow (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-3765 and fix it if it is affected.

What it is: CVE-2023-3765 is a critical path traversal vulnerability in Lfprojects Mlflow, published on 19 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3765 exists.

Affected packages and fixed versions:
- mlflow (Bitnami): affected all versions; fixed in 2.5.0
- mlflow (PyPI): affected all versions; fixed in 2.5.0
- mlflow (PyPI): affected all versions; fixed in 2.5.0
- mlflow (PyPI): affected all versions; fixed in 2.5.0

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

## Sources

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

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