MLflow 3.17.1 and prior Path Traversal via Trace ID 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 | unknown |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Mlflow | Mlflow |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-wqmh-qccw-pqwf | MLflow FileStore trace IDs allow path traversal and arbitrary file writes |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.625% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Lfprojects
Lfprojects mlflow |
|
| CPEs | cpe:2.3:a:lfprojects:mlflow:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Lfprojects
Lfprojects mlflow |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | MLflow 3.17.1 Path Traversal via Trace ID API | MLflow 3.17.1 and prior Path Traversal via Trace ID API |
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mlflow
Mlflow mlflow |
|
| Vendors & Products |
Mlflow
Mlflow mlflow |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | MLflow 3.17.1 and earlier contains a path traversal vulnerability in the FileStore tracking backend that allows unauthenticated attackers to control filesystem paths by submitting a crafted trace ID containing traversal sequences to the POST /api/3.0/mlflow/traces endpoint. Attackers can exploit FileStore.start_trace() to write trace_info.yaml, request_metadata, and tag files with attacker-controlled metadata outside the intended experiment trace directory, subject to the server process's filesystem permissions. FileStore is the default tracking backend before MLflow 3.7.0 and opt-in thereafter (the default changed to a SQLite database), so deployments in the earlier part of the affected range are vulnerable without special configuration while later ones are affected only when FileStore is explicitly selected. | |
| Title | MLflow 3.17.1 Path Traversal via Trace ID API | |
| Weaknesses | CWE-22 | |
| References |
| |
| Metrics |
cvssV3_1
|