Loading vulnerability…
CVE-2026-2033 is a remote code execution vulnerability in MLflow Tracking Server caused by improper validation of user-supplied artifact file paths in the artifact handler. The flaw is a directory traversal condition in which attacker-controlled path input is used in file operations without sufficient restriction or canonicalization. By abusing this path handling weakness, a remote attacker can reach unintended filesystem locations and achieve arbitrary code execution on the server. Exploitation does not require authentication and results in code execution in the security context of the MLflow service account.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical MLflow Tracking Server remote code execution vulnerability, cited only as part of prior vendor security history.
A directory traversal flaw in MLflow Tracking Server’s artifact handler path processing that can be exploited remotely without authentication to achieve arbitrary code execution in the context of the service account.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.