NVD / CVE Program· CNA zdi

CVE-2025-11201: MLflow Tracking Server Model Creation Directory Traversal Remote Code Execution Vulnerability

Noroxi assessment

Priority: Plan (action score 47/100)

Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 26.2% (FIRST EPSS); higher than 97.9% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: mlflow (PyPI) 3.0.0, 2.22.4.

Add it to your regular patch cycle. Upgrade to mlflow (PyPI) 3.0.0, 2.22.4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

CriticalCVSS 9.8 · v3.1—Proof of concept Fix available

Published: Oct 29, 2025
Updated: Oct 19, 2026
EPSS: 26.2% · 97th percentile
CWE: CWE-22

Report tools

JSON

Action score

Plan

Add it to your regular patch cycle.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 8 / 30 · 26.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 9.8
CNA · zdi: 8.1; 1.7 point gap

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
lfprojects	mlflow	cpe:2.3:a:lfprojects:mlflow

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

lfprojects mlflowbefore 2025-06-10

Versions reported by the vendor

Affected version ranges reported by the assigning authority (zdi). Independent of NVD's CPE analysis and usually ahead of it.

MLflow MLflow
- 2.21.3affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
PyPI	mlflow	from 3.0.0rc0 · before 3.0.0	3.0.0
PyPI	mlflow	before 2.22.4	2.22.4

Same product

lfprojects: all records

Other highest-scoring records for the same primary product.

CVE-2026-64849MLflow: Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed via unvalidated HTTP redirects (and DNS rebinding)KEV
70This week
CVE-2023-3765Absolute Path Traversal in mlflow/mlflow
60This week
CVE-2023-1177Path Traversal: '\..\filename' in mlflow/mlflow
60This week

Published before and after this one in the same product

← EarlierCVE-2025-52967Jun 23, 2025 · gateway_proxy_handler in MLflow before 3.1.0 lacks gateway_path validation.
23Monitor
← EarlierCVE-2025-11200Oct 29, 2025 · MLflow Weak Password Requirements Authentication Bypass Vulnerability
39Monitor
Later →CVE-2025-14279Jan 12, 2026 · DNS Rebinding Vulnerability in mlflow/mlflow
32Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
PyPI:mlflow	2.22.4	Package registry (OSV)
PyPI:mlflow	3.0.0	Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:0	2026-09-27

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedOct 29, 2025
First PoCSep 27, 2026+332 d
TodayOct 29, 2026+365 d

EPSS, last 120 days-1% in 7 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

B-Step62/mlflowcommit 2e02bc7

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2025-15031140 days apartPath Traversal Vulnerability in mlflow/mlflow
36Monitor
CVE-2024-0520510 days apartRemote Code Execution due to Full Controlled File Write in mlflow/mlflow
36Monitor
CVE-2026-2614194 days apartArbitrary File Read via Prompt Tag Source Validation Bypass in mlflow/mlflow
31Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:47 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/B-Step62/mlflow/commit/2e02bc7bb70df243e6eb792689d9b8eba0013161

Show all references (1 more)

www.zerodayinitiative.com/advisories/ZDI-25-931/

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records