NVD / CVE Program· CNA @huntr_ai

CVE-2024-0520: Remote Code Execution due to Full Controlled File Write in mlflow/mlflow

Noroxi assessment

Priority: Monitor (action score 36/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: 2.4% (FIRST EPSS); higher than 84% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
Fixed version: mlflow mlflow/mlflow 2.9.0.

Low priority for now. Upgrade to mlflow mlflow/mlflow 2.9.0 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

A vulnerability in mlflow/mlflow version 8.2.1 allows for remote code execution due to improper neutralization of special elements used in an OS command ('Command Injection') within the `mlflow.data.http_dataset_source.py` module. Specifically, when loading a dataset from a source URL with an HTTP scheme, the filename extracted from the `Content-Disposition` header or the URL path is used to generate the final file path without proper sanitization. This flaw enables an attacker to control the file path fully by utilizing path traversal or absolute path techniques, such as '../../tmp/poc.txt' or '/tmp/poc.txt', leading to arbitrary file write. Exploiting this vulnerability could allow a malicious user to execute commands on the vulnerable machine, potentially gaining access to data and model information. The issue is fixed in version 2.9.0.

HighCVSS 8.8 · v3.1—Proof of concept Fix available

Published: Jun 6, 2024
Updated: Jun 17, 2026
EPSS: 2.4% · 84th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 35 / 40 · 8.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 1 / 30 · 2.4%

CISA SSVC decision

Exploitation: proof of concept
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 8.8
CNA · @huntr_ai: 10.0; 1.2 point gap

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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 2.9.0

Versions reported by the vendor

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

mlflow mlflow/mlflow
- unspecified and later · before 2.9.0affected

Package-level exposure

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

Ecosystem	Package	Affected range	Fix
PyPI	mlflow	before 2.9.0	2.9.0

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-2024-37060Jun 4, 2024 · Deserialization of untrusted data can occur in versions of the MLflow platform running version 1.27.0 or newer, enabling a maliciously craft
35Monitor
← EarlierCVE-2024-37061Jun 4, 2024 · Remote Code Execution can occur in versions of the MLflow platform running version 1.11.0 or newer, enabling a maliciously crafted MLproject
35Monitor
Later →CVE-2024-2928Jun 6, 2024 · Local File Inclusion (LFI) via URI Fragment Parsing in mlflow/mlflow
37Monitor

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
mlflow mlflow/mlflow	2.9.0 · description	Vendor (CNA)
PyPI:mlflow	2.9.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	2025-08-18

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.

PublishedJun 6, 2024
First PoCAug 18, 2025+437 d
TodayNov 4, 2026+881 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

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

mlflow/mlflowcommit 400c226

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-11201510 days apartMLflow Tracking Server Model Creation Directory Traversal Remote Code Execution Vulnerability
47Plan
CVE-2023-6753177 days apartPath Traversal in mlflow/mlflow
35Monitor
CVE-2024-156052 days apartPath Traversal Vulnerability in mlflow/mlflow
32Monitor
CVE-2024-148352 days apartPath Traversal Vulnerability in mlflow/mlflow
31Monitor
CVE-2023-6015203 days apartMLflow Arbitrary File Upload
31Monitor
CVE-2024-155852 days apartPath Traversal Vulnerability in mlflow/mlflow
30Monitor

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.
A user must open a link or visit a page.
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: Required
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:R/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/mlflow/mlflow/commit/400c226953b4568f4361bc0a0c223511652c2b9d

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

All records

Noroxi analysis

What does it mean in your environment?

We use this product, ask for help

Data sources and verification

CNA: @huntr_ai

CVE.org (CNA)Oct 15, 2025, 12:50 PM UTC
CISA ADPOct 15, 2025, 12:50 PM UTC
NVDJun 17, 2026, 2:53 AM UTC
FIRST EPSSNov 3, 2026, 12:00 AM UTC
OSV / GHSANov 4, 2026, 3:18 AM UTC
PoC-in-GitHubNov 4, 2026, 3:18 AM UTC

Each line is when that source was last processed for this record.