CVE-2026-53995

Description

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.

Severity
HIGH
CVSS v3
8.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L · source cna
CVSS v4
8.8
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 · source cna
Exploit chance (EPSS)
0.625%
chance of exploitation in the next 30 days
higher than 50.6% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
Yes
Exploit references (NVD and CNA): 1
Metasploit modules: 0
Nuclei templates: 0

Weakness

CISA SSVC decision points

Exploitationpoc
Automatableyes
Technical impactpartial
Scored2026-10-19

Timeline

  1. 2026-10-19Published by the CNA21:05 UTC
  2. 2026-10-19CISA SSVC decision recordedsame day
  3. 2026-10-20GitHub advisory published (GHSA-wqmh-qccw-pqwf)1 day after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-wqmh-qccw-pqwf, affected packages:

PackageVulnerable versionsFixed in
PyPI mlflowbefore 3.17.23.17.2

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
lfprojects mlflowbefore 3.18.0fixed in 3.18.03.18.0
mlflow mlflowfrom 0 before 3.18.0fixed in 3.18.03.18.0

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources