highCVSS 8.1NVD status: Analyzed

CVE-2024-1560

MLflow: A path traversal vulnerability exists in the mlflow/mlflow repository, specifically within the artifact deletion functionality.

ComponentMLflow
Severityhigh (CVSS 8.1)
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Published (NVD)2024-04-16
Last modified2026-06-17
Affected versions
mlflow <= 2.9.2
Fixed insee the vendor advisory
WeaknessCWE-22
CISA KEVnot listed

NVD description

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.

Does CVE-2024-1560 hit the version you run?Paste your docker-compose.yml, requirements.txt or package.json. The scanner checks your pinned versions against this CVE and every other one we track for MLflow.
Check my stack

What to do

  • NVD lists no fixed version yet: follow the vendor advisory below and keep MLflow off the public internet until a fix ships.
  • Do not expose the component's API or UI to the internet without authentication in front of it.

Sources

Read more

Other MLflow CVEs

All MLflow CVEs