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.

• https://github.com/SaiTeja-Erukude/CVE-2026-53995-mlflow-path-traversal
• https://github.com/mlflow/mlflow/pull/26842

• https://github.com/SaiTeja-Erukude/CVE-2026-53995-mlflow-path-traversal
• https://github.com/mlflow/mlflow/pull/26842
• https://www.vulncheck.com/advisories/mlflow-path-traversal-via-trace-id-api

• HIGHCVE-2014-125130PoC
• HIGHCVE-2017-20284
• HIGHCVE-2021-48011PoC
• HIGHCVE-2023-54403PoC
• MEDIUMCVE-2024-58386PoC
• HIGHCVE-2024-58387PoC
• HIGHCVE-2024-58388PoC
• MEDIUMCVE-2025-1280

Related by shared AI tags and CWE weakness class. Browse the full archive.