# CVE-2024-0520: Remote Code Execution due to Full Controlled File Write in mlflow/mlflow

> Attackers can achieve remote code execution via arbitrary file write in MLflow by exploiting path traversal in dataset loading.

- **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:** 6 Jun 2024
- **Updated:** 15 Oct 2025
- **Also known as:** BIT-mlflow-2024-0520, GHSA-5q6c-ffvg-xcm9, PYSEC-2024-239

## What is CVE-2024-0520?

CVE-2024-0520 is a critical path traversal vulnerability in Lfprojects Mlflow, published on 6 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in mlflow/mlflow version 8.2.1 allows for remote code execution due to improper neutralization of special elements used in an OS command ('Command Injection') within the `mlflow.data.http_dataset_source.py` module. Specifically, when loading a dataset from a source URL with an HTTP scheme, the filename extracted from the `Content-Disposition` header or the URL path is used to generate the final file path without proper sanitization. This flaw enables an attacker to control the file path fully by utilizing path traversal or absolute path techniques, such as '../../tmp/poc.txt' or '/tmp/poc.txt', leading to arbitrary file write. Exploiting this vulnerability could allow a malicious user to execute commands on the vulnerable machine, potentially gaining access to data and model information. The issue is fixed in version 2.9.0.

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

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

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


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

Products: Lfprojects Mlflow.

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

Upgrade mlflow to a fixed version for your release line: 2.9.1 or 2.9.0.

## Is CVE-2024-0520 being exploited?

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

Public exploit code:

- https://github.com/chan-068/CVE-2024-0520_try (github_poc): https://github.com/chan-068/CVE-2024-0520_try

## 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-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)
- [CVE-2023-6015](https://insights.sbomify.com/CVE-2023-6015/): MLflow Arbitrary File Upload (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-0520 is a critical path traversal vulnerability in Lfprojects Mlflow, published on 6 Jun 2024. 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-2024-0520 exists.

Affected packages and fixed versions:
- mlflow (Bitnami): affected all versions; fixed in 2.9.1
- mlflow (PyPI): affected all versions; fixed in 2.9.0
- mlflow (PyPI): affected all versions; fixed in 2.9.0
- mlflow (PyPI): affected all versions; fixed in 2.9.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-2024-0520/ (Markdown: https://insights.sbomify.com/CVE-2024-0520/index.md)
```

## Sources

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

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