Unauthenticated code execution via artifact path traversal
Published Feb 20, 2026 · Updated Feb 20, 2026
Path traversal in MLflow Tracking Server 3.1.1 allows remote attackers to execute arbitrary code through crafted artifact metadata. FileStore._find_run_root accepts a malicious meta.yaml beneath an artifact directory as a run root and uses the attacker-controlled path in file operations. No authentication or user interaction is required; successful exploitation runs code with the tracking service account's privileges.
Summary
What happened
Path traversal in MLflow Tracking Server 3.1.1 allows remote attackers to execute arbitrary code through crafted artifact metadata. FileStore._find_run_root accepts a malicious meta.yaml beneath an artifact directory as a run root and uses the attacker-controlled path in file operations. No authentication or user interaction is required; successful exploitation runs code with the tracking service account's privileges.
The record
- CVE
- CVE-2026-2033
- Published
- Feb 20, 2026
- Updated
- Feb 20, 2026
- Vendor
- MLflow Project
- Product
- MLflow
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 20, 2026CVE publishedPublication date reported by the CVE source.
- Feb 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.1.1 and 5b9c01925c2e2a8cf0951f155a6a468ff99cfe0f
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo