highCVSS 7.5NVD status: Analyzed

CVE-2024-3848

MLflow: A path traversal vulnerability exists in mlflow/mlflow version 2.11.0, identified as a bypass for the previously addressed CVE-2023-6909.

ComponentMLflow
Severityhigh (CVSS 7.5)
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Published (NVD)2024-05-16
Last modified2026-06-17
Affected versions
mlflow < 2.12.1
Fixed in2.12.1
WeaknessCWE-29CWE-22
CISA KEVnot listed

NVD description

A path traversal vulnerability exists in mlflow/mlflow version 2.11.0, identified as a bypass for the previously addressed CVE-2023-6909. The vulnerability arises from the application's handling of artifact URLs, where a '#' character can be used to insert a path into the fragment, effectively skipping validation. This allows an attacker to construct a URL that, when processed, ignores the protocol scheme and uses the provided path for filesystem access. As a result, an attacker can read arbitrary files, including sensitive information such as SSH and cloud keys, by exploiting the way the application converts the URL into a filesystem path. The issue stems from insufficient validation of the fragment portion of the URL, leading to arbitrary file read through path traversal.

Does CVE-2024-3848 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

  • Upgrade MLflow to 2.12.1 or later.
  • 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