Technical impact
The vulnerability allows an attacker to read any file on the MLflow server that the process can access. From versions 3.10.0 through 3.17.0, the prompt branch in the _create_model_version() function accepts schemeless relative paths as artifact locations. Because path validation is performed only when a source URL contains a scheme, and the prompt flag is determined by tag presence, an attacker can store a local filesystem path as the model version artifact location. Subsequent calls to /api/2.0/mlflow/model-versions/get-artifact then return the file contents. This results in a confidentiality breach of whatever files the MLflow server process has permission to read, potentially including sensitive configuration, credentials, or data files.
Affected Systems
MLflow by MLflow is affected. All releases from 3.10.0 up to, but not including, 3.17.0 are vulnerable. Version 3.17.0 and later contain the fix.
Risk and Exploitability
With a CVSS score of 7.5, the vulnerability presents a high impact technical weakness. The EPSS score is 2%, and it is not listed in the CISA KEV catalog, so the public exploit probability is low but nonzero. The vulnerability can be exploited by sending crafted requests to an MLflow instance that allows unauthenticated API access, or by any authenticated user in a basic‑auth configuration that can create registered models. The server‑side file read is performed by the MLflow process, so the attack requires no special privileges beyond standard server access. Without any mitigating controls, an attacker could read arbitrary files, exposing data confidentiality.
Github GHSA