MLflow < 3.18.0 Path Traversal via model_id in log_outputs API
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| mlflow | mlflow | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Mlflow | Mlflow |
|
||||||||
| Mlflow | Mlflow/mlflow |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mlflow
Mlflow mlflow Mlflow mlflow/mlflow |
|
| Vendors & Products |
Mlflow
Mlflow mlflow Mlflow mlflow/mlflow |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | MLflow before 3.18.0 using the FileStore backend contains a path traversal vulnerability that allows unauthenticated remote attackers to write files outside the intended run directory by supplying a malicious model_id parameter to the log outputs API. Attackers can exploit the unvalidated model_id containing ../ sequences via the POST /api/3.0/mlflow/runs/outputs endpoint to create directories and write a meta.yaml file at arbitrary filesystem locations, limited only by the server account's permissions. FileStore was the default backend before 3.7.0 and is opt-in afterward through MLFLOW_ALLOW_FILE_STORE. | |
| Title | MLflow < 3.18.0 Path Traversal via model_id in log_outputs API | |
| Weaknesses | CWE-22 | |
| References |
| |
| Metrics |
cvssV3_1
|