CVE-2026-53995

LOWCVSS 8.8 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

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.

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-22

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • 1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-11-07: 111-07
Referenced assets1 URL
Full discourse1 post
  • AI Cyber Brief@justelite

    CVE-2026-53995: unauthenticated path traversal lets anyone write files outside the trace folder on MLflow servers using FileStore. PoC is public. Fixed only in 3.18.0 (3.17.2 lacks it). Update, restrict access, move to a database backend. https://aicyberbrief.com/article/mlflow-3-18-0-fixes-a-flaw-that-let-anyone-write-files-on-servers-using-the-filestore-backend-update-now

    0002074
    1.8K followersView on X

Explore more