How severe is CVE-2025-11201?

CVE-2025-11201 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2025-11201 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 27% (98th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-11201?

CVE-2025-11201 affects Lfprojects Mlflow. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-11201?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

Does CVE-2025-11201 have an EU (EUVD) identifier?

Yes. CVE-2025-11201 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-36707.

When was CVE-2025-11201 published?

CVE-2025-11201 was published on 2025-10-29 and last updated on 2026-06-17.

CVE-2025-11201

CVE-2025-11201 is a critical-severity vulnerability in Lfprojects Mlflow with a CVSS 3.x base score of 9.8. Its EPSS exploit-prediction score of 27% places it in the 98th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-22.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
EPSS exploit prediction: 27% (98th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-36707
Weakness: CWE-22
Affected product: Lfprojects Mlflow
Published: 2025-10-29
Last modified: 2026-06-17

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.

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.
How severe is CVE-2025-11201?: CVE-2025-11201 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-11201 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 27% (98th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-11201?: CVE-2025-11201 affects Lfprojects Mlflow. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-11201?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2025-11201 have an EU (EUVD) identifier?: Yes. CVE-2025-11201 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-36707.
When was CVE-2025-11201 published?: CVE-2025-11201 was published on 2025-10-29 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:lfprojects:mlflow:*:*:*:*:*:*:*:*

More vulnerabilities in Lfprojects Mlflow

CVE-2025-15036 — Critical (CVSS 10.0): A path traversal vulnerability exists in the `extract_archive_to_dir` function within the…
CVE-2023-3765 — Critical (CVSS 10.0): Absolute Path Traversal in GitHub repository mlflow/mlflow prior to 2.5.0.
CVE-2026-0545 — Critical (CVSS 9.8): In mlflow/mlflow, the FastAPI job endpoints under `/ajax-api/3.0/jobs/*` are not protected by authentication or…
CVE-2025-15379 — Critical (CVSS 9.8): A command injection vulnerability exists in MLflow's model serving container initialization code, specifically in the…
CVE-2025-11200 — Critical (CVSS 9.8): MLflow Weak Password Requirements Authentication Bypass Vulnerability. This vulnerability allows remote attackers to…
CVE-2023-6975 — Critical (CVSS 9.8): A malicious user could use this issue to get command execution on the vulnerable machine and get access to data &…

All CVEs affecting Lfprojects Mlflow →

Other CWE-22 (Path Traversal) vulnerabilities

CVE-2026-48282 — Critical (CVSS 10.0): ColdFusion versions 2025.9, 2023.20 and earlier are affected by an Improper Limitation of a Pathname to a Restricted…
CVE-2026-54917 — Critical (CVSS 10.0): SeaweedFS is a distributed storage system for object storage (S3), file systems, and Iceberg tables. Prior to 4.30, the…
CVE-2026-11429 — Critical (CVSS 10.0): Two endpoints in the Vault Service ScriptsController, shared by Altium Enterprise Server and Altium 365, accept file…
CVE-2026-34909 — Critical (CVSS 10.0): A malicious actor with access to the network could exploit a Path Traversal vulnerability found in UniFi OS devices to…
CVE-2026-7411 — Critical (CVSS 10.0): In Eclipse BaSyx Java Server SDK versions prior to 2.0.0-milestone-10, inadequate path normalization in the Submodel…
CVE-2026-36767 — Critical (CVSS 10.0): A path traversal vulnerability in the /content/images/add endpoint of shopizer v3.2.5 allows attackers write arbitrary…

Browse all CWE-22 (Path Traversal) vulnerabilities →