CVE-2024-3573

What it is

mlflow/mlflow is vulnerable to Local File Inclusion (LFI) due to improper parsing of URIs, allowing attackers to bypass checks and read arbitrary files on the system. The issue arises from the 'is_local_uri' function's failure to properly handle URIs with empty or 'file' schemes, leading to the misclassification of URIs as non-local. Attackers can exploit this by crafting malicious model versions with specially crafted 'source' parameters, enabling the reading of sensitive files within at least two directory levels from the server's root.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure.

Exploit odds

0.7% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2024-04-16 00:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 07:44 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.7% in the next 30 days (EPSS).
• Severity: 9.3 CRITICAL (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2024-04-16 00:15 UTC

Last modified

2026-06-17 07:44 UTC

Exploit probability

0.7% · EPSS, next 30 days

Weakness

CWE-29

Record status

Analyzed

Affected

• Lfprojects Mlflow < 2.10.0

Attack profile CVSS 3.1 · 9.3

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Changed

Confidentiality

High

Integrity

Low

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2024-3573.md and follow it. Check whether this project is affected by CVE-2024-3573. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge