MLflow
MLflow < 3.18.0 Path Traversal via Trace ID API
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 3.18.0
Fixed in 3.18.0
Mitigation
Upgrade mlflow to 3.18.0 or later.
References
Timeline
Days relative to CVE publicationFirst public PoC 1.9 days before publication; not in CISA KEV. First PoC: SaiTeja-Erukude/CVE-2026-53995-mlflow-path-traversal (created 17 Oct 2026, found by us: 14 Nov 2026).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| SaiTeja-Erukude/CVE-2026-53995-mlflow-path-traversal | 17 Oct 2026 −1.9 d | 14 Nov 2026 | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.
PoC characteristics
What to hunt for in your logs · from 1 PoC repoPOST /api/3.0/mlflow/traces
Regex
Generated from PoC characteristics; not yet reviewed. Matches the request path and query.
(?i)^/api/3\.0/mlflow/traces(?:[?#].*)?$
Suricata
Template generated from PoC characteristics. Review before deploying.
alert http any any -> $HOME_NET any (msg:"GG PoC-Monitor CVE-2026-53995 mlflow mlflow exploit attempt"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/api/3.0/mlflow/traces"; reference:url,poc.griffinguard.io/cve/CVE-2026-53995; classtype:web-application-attack; sid:9698534; rev:1;)
Sigma
Template generated from PoC characteristics. Review before deploying.
title: mlflow mlflow exploit attempt (CVE-2026-53995)
id: gg-pocmon-cve-2026-53995-9698534
status: experimental
description: Request pattern taken from public PoCs for CVE-2026-53995. Generated, not reviewed.
references:
- https://poc.griffinguard.io/cve/CVE-2026-53995
logsource:
category: webserver
detection:
selection:
cs-method: POST
cs-uri-stem|contains|all:
- '/api/3.0/mlflow/traces'
condition: selection
falsepositives:
- Authorized vulnerability scanning
level: high
tags:
- attack.initial_access
- attack.t1190
- cve.2026.53995