MLflow
MLflow Tracking Server Model Creation Directory Traversal Remote Code Execution Vulnerability
MLflow Tracking Server Model Creation Directory Traversal Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of MLflow Tracking Server. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of model file paths. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to execute code in the context of the service account. Was ZDI-CAN-26921.
Affected versions and mitigation
From the CVE record, GitHub Security Advisories and the vendor's references.Affected
- 2.21.3
Mitigation
Upgrade mlflow to 3.0.0 or later.
Upgrade mlflow to 2.22.4 or later.
References
- Vendor advisory github.com/B-Step62/mlflow/commit/2e02bc7bb70d…
Timeline
Days relative to CVE publicationFirst public PoC 332 days after publication; not in CISA KEV. First PoC: rmhowe425/POC-CVE-2025-11201 (created 27 Sep 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| rmhowe425/POC-CVE-2025-11201 | 27 Sep 2026 +332 d | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| nuclei template | nuclei template: MLflow Tracking Server - Unauthenticated Model Source Path Traversal RCE | 11 Nov 2026 | 14 Nov 2026 |