Advisory

GHSA-wqmh-qccw-pqwf

Also known as: BIT-mlflow-2026-53995, CVE-2026-53995

Summary

MLflow FileStore trace IDs allow path traversal and arbitrary file writes

Details

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-10-20 00:31 UTC
Modified
2026-10-26 08:55 UTC

Affected packages and fixes

mlflow

PyPI · All systems

Affected

  • introduced 0, fixed 3.17.2 (ecosystem)

Fixed versions

3.17.2

Fix

  • Fixed version 3.17.2
    pip install --upgrade mlflow==3.17.2

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences