CVE-2026-2033
Received Received - Intake
Directory Traversal RCE in MLflow Tracking Server Artifact Handler

Publication date: 2026-02-20

Last updated on: 2026-02-20

Assigner: Zero Day Initiative

Description
MLflow Tracking Server Artifact Handler 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 artifact 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-26649.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-20
Last Modified
2026-02-20
Generated
2026-05-07
AI Q&A
2026-02-21
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
mlflow tracking_server *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-22 The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in the MLflow Tracking Server's artifact handler, specifically in how it processes artifact file paths. Due to improper validation of user-supplied paths before file operations, an attacker can perform a directory traversal attack. This allows remote attackers to execute arbitrary code on the affected server without needing to authenticate.


How can this vulnerability impact me? :

Exploiting this vulnerability enables an attacker to execute arbitrary code remotely on the MLflow Tracking Server. This can lead to full compromise of the server, including unauthorized access, data theft, service disruption, or further attacks within the network. Since no authentication is required, the risk is significant.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


What immediate steps should I take to mitigate this vulnerability?

I don't know


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart