CVE-2026-53995
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.
Weakness
- CWE-22: Improper Limitation of a Pathname to a Restricted Directory
CISA SSVC decision points
| Exploitation | poc |
|---|---|
| Automatable | yes |
| Technical impact | partial |
| Scored | 2026-10-19 |
Timeline
- 2026-10-19Published by the CNA21:05 UTC
- 2026-10-19CISA SSVC decision recordedsame day
- 2026-10-20GitHub advisory published (GHSA-wqmh-qccw-pqwf)1 day after publication
Exploit and advisory records
GitHub advisory GHSA-wqmh-qccw-pqwf, affected packages:
| Package | Vulnerable versions | Fixed in |
|---|---|---|
| PyPI mlflow | before 3.17.2 | 3.17.2 |
Affected products
Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.
| Product | Vulnerable versions | Fixed in |
|---|---|---|
| lfprojects mlflow | before 3.18.0fixed in 3.18.0 | 3.18.0 |
| mlflow mlflow | from 0 before 3.18.0fixed in 3.18.0 | 3.18.0 |
References
- https://github.com/mlflow/mlflow/commit/d64cc8b673f71d29d93a7845fc179946ad56a881
- https://github.com/mlflow/mlflow/pull/26842
- https://github.com/SaiTeja-Erukude/CVE-2026-53995-mlflow-path-traversal
- https://github.com/mlflow/mlflow/releases/tag/v3.18.0
- https://www.vulncheck.com/advisories/mlflow-path-traversal-via-trace-id-api
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cve_lookup/CVE-2026-53995'curl 'https://api.contrastcyber.com/cve_risk_score/CVE-2026-53995'curl 'https://api.contrastcyber.com/cve_exploit/CVE-2026-53995'curl 'https://api.contrastcyber.com/cve_products/CVE-2026-53995'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- OWASP Top 10 categories by the OWASP Foundation (CC BY 3.0).
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).