MLflowGHSA-5mvj-wmgj-7q8c
mlflow vulnerable to Path Traversal
High8.1CVE-2024-1560 · Published Apr 16, 2024 · updated Jul 7, 2026
A path traversal vulnerability exists in the mlflow/mlflow repository, specifically within the artifact deletion functionality. Attackers can bypass path validation by exploiting the double decoding process in the `_delete_artifact_mlflow_artifacts` handler and `local_file_uri_to_path` function, allowing for the deletion of arbitrary directories on the server's filesystem. This vulnerability is due to an extra unquote operation in the `delete_artifacts` function of `local_artifact_repo.py`, which fails to properly sanitize user-supplied paths. The issue is present up to version 2.9.2, despite attempts to fix a similar issue in CVE-2023-6831.
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| mlflow PyPI | <= 2.9.2 | No fix yet |
Details and references
- CVSS 3.0
- CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-22
- Also known as
- BIT-mlflow-2024-1560, CVE-2024-1560, PYSEC-2026-1641
More MLflow advisories
All MLflow| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| May 162024 | MLflow has a Local File Read/Path Traversal bypass High7.5May 16, 2024 | High7.5 | 2.12.1 |
| Apr 162024 | mlflow vulnerable to Path TraversalCritical9.3Apr 16, 2024 | Critical9.3 | 2.10.0 |
| Apr 162024 | mlflow vulnerable to Path TraversalHigh7.5Apr 16, 2024 | High7.5 | No fix yet |
| Apr 162024 | mlflow vulnerable to Path TraversalHigh7.5Apr 16, 2024 | High7.5 | 2.12.1 |
| Apr 162024 | mlflow vulnerable to Path TraversalHigh7.5Apr 16, 2024 | High7.5 | No fix yet |
| Apr 162024 | mlflow Path Traversal vulnerabilityHigh7.5Apr 16, 2024 | High7.5 | 2.12.1 |