Path Traversal in Mlflow
CVE-2026-53995
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.
Vulnerability class: Path Traversal (Directory Traversal)
Published .
CVSS v3 metric
CVSS v3 base score 8.2 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
Weakness classification (CWE)
References
- github.com/SaiTeja-Erukude/CVE-2026-53995-mlflow-path-traversal (technical-description, exploit)
- github.com/mlflow/mlflow/pull/26842 (issue-tracking)
- www.vulncheck.com/advisories/mlflow-path-traversal-via-trace-id-api (third-party-advisory)
Frequently asked questions
- What is CVE-2026-53995?
- CVE-2026-53995 is a high-severity vulnerability in Mlflow, classified under Path Traversal. CVSS score: 8.2/10. Published 2026-10-19.
- How severe is CVE-2026-53995?
- High severity. CVSS v3 base score is 8.2 out of 10.