CVE-2026-53995MLflow < 3.18.0 Path Traversal via Trace ID API
Description
MLflow before 3.18.0 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.
Data: CVE.org, NVD, CISA KEV, FIRST EPSS, Ubuntu. Published as the sources state it, in English.
Affected products and versions
| Vendor | Product | Versions | |
|---|---|---|---|
| lfprojects | mlflow | < 3.18.0 | |
| mlflow | mlflow | < 3.18.0 |
References and patches
- Researcher Disclosure technical-descriptionexploit
- Release Notes release-notes
- Pull Request issue-trackingpatch
- Patch Commit issue-trackingpatch
- VulnCheck Advisory: MLflow 3.17.1 Path Traversal via Trace ID API third-party-advisory