Skip to main content
Public proof of conceptFix available

CVE-2025-11201

A public proof of concept exists; no exploitation attested.

  • Published2025-10-29
  • Fixed in2025-06-10
  • WeaknessCWE-22

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2025-10-2920:15CVE publishedNVD
  2. 2026-10-2319:23First public proof of conceptPoC-in-GitHub
  3. 2026-10-2319:23EPSS crossed 10 %FIRST EPSS

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2025-11201?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2025-11201?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Lfprojects mlflow
BranchAffectedFixed in
2025.x< 2025-06-102025-06-10

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update Lfprojects mlflow to 2025-06-10

Advisories and patches

Detection

read 2026-10-23 19:24 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
1 repository, unverifiedrmhowe425/POC-CVE-2025-11201
PoC-in-GitHub

Sources

  • CISA-ADPSSVC decisionnone2025-10-31
  • OpenCVESSVC decisionnone—
  • NVDCVSS 3.19.8read 2026-10-23
  • CNACVSS 3.08.1read 2026-10-23
  • CNAweakness (CWE)CWE-22read 2026-10-23
  • FIRST EPSSEPSS score26.3 %read 2026-10-23
  • PoC-in-GitHubproof of concept1read 2026-10-23

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2025-10-29
Last Modified
2026-10-19
NVD status
Analyzed

Frequently asked questions

What is CVE-2025-11201?

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.

Is CVE-2025-11201 actively exploited?

Active exploitation of CVE-2025-11201 has not been confirmed. Its EPSS score was 26.3% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2025-11201?

CVE-2025-11201 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month