Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2025-11201: Unauthenticated Path Traversal RCE in MLflow Tracking Server Model Creation

Published Oct 29, 2025 · Updated 4 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 1 in a dayToday
CVSS9.8Critical · v3.1
EPSS60.3%99th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Lfprojects
IdentifiersCVE-2025-11201CWE-22 · Improper Limitation of a Pathname…

CVE-2025-11201 is a directory traversal vulnerability in MLflow Tracking Server's model creation process. Insufficient validation of the user-controlled source parameter permits crafted model version creation requests to escape the intended artifact directory during file operations. This enables arbitrary file writes and can lead to remote code execution when attacker-written files are subsequently loaded by Python. Exploitation requires no authentication, and code executes with the privileges of the MLflow service account. Affected versions are those before 2.22.4 and prerelease versions from 3.0.0rc0 up to, but excluding, 3.0.0.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Unauthenticated remote attackers can write files outside the intended artifact directory, subject to the service account's filesystem permissions, and potentially execute arbitrary code as that account. Successful exploitation can compromise accessible model artifacts, application data, credentials, and machine-learning intellectual property. The extent of system compromise depends on the service account's privileges and access.

Mitigation

If you can’t patch tonight, do this now.

Until patched, restrict access to the MLflow Tracking Server and its model creation endpoints to trusted networks and authorized users. Apply least privilege to the service account and limit its filesystem write permissions, particularly to locations from which Python may load executable content. These measures reduce exposure but do not correct the path validation flaw.

Remediation

Patch, then assume compromise.

Upgrade affected MLflow installations to version 2.22.4 or later in the 2.x release line, or version 3.0.0 or later in the 3.x release line.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LfprojectsMlflowapplication
FAQ

Frequently asked questions

Is CVE-2025-11201 exploited in the wild?
As of Nov 13, 2026, Mallory has no reports of CVE-2025-11201 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-11201?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2025-11201, the earliest disclosed Sep 27, 2026.
Is there a patch for CVE-2025-11201?
Upgrade affected MLflow installations to version 2.22.4 or later in the 2.x release line, or version 3.0.0 or later in the 3.x release line.
What products are affected by CVE-2025-11201?
Lfprojects Mlflow.
How severe is CVE-2025-11201?
CVE-2025-11201 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 60.3% (99th percentile) as of Nov 13, 2026.
Activity feed

Recent activity

12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity9Community discussion across Reddit, Mastodon, and other social sources.