CVE-2026-53995

CVSS 8.8 (high) · published 2026-10-19

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

Source: NVD CVE-2026-53995

References

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

Check your software

Connect an AI agent to the FixLane MCP server or ask the Telegram bot to check what you have installed against incidents with a verified fixed version.