Summary
CVE-2026-53995 is a path traversal vulnerability (CWE-22) in the FileStore tracking backend of MLflow 3.17.1 and earlier. An unauthenticated remote attacker can submit a crafted trace ID to write trace metadata files outside the intended directory. The CVE record lists a CVSS v4.0 score of 8.8 (High).
Technical details
- Root cause: The
POST /api/3.0/mlflow/tracesendpoint accepts a trace ID containing traversal sequences, and the FileStore backend uses it unsanitized when building filesystem paths for trace metadata. - Trigger conditions: The MLflow server uses the FileStore tracking backend. FileStore is the default backend in versions before 3.7.0, so earlier deployments are exposed by default.
- Attack vector: Network, no authentication or user interaction required.
- Impact: Trace metadata files can be written outside the intended directory, limited by the permissions of the server process. The CVE record rates the impact as high on integrity and low on availability.
Affected software
- MLflow versions 0 through 3.17.1 (FileStore tracking backend)
Severity
- CVSS v4.0: 8.8 (High) –
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N - CVSS v3.1 (also listed in the CVE record): 8.2 (High) –
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
Mitigation and recommended actions
- Immediate: the CVE record lists no fixed version. A fix has been proposed upstream (MLflow pull request 26842). Monitor MLflow releases and upgrade once a patched version is available.
- Until a fix is available, do not expose MLflow servers to untrusted networks.
- Put authentication in front of the server, such as a reverse proxy.
- Consider a database-backed tracking store instead of FileStore.
- Run the MLflow server process with minimal filesystem write permissions.

