How severe is CVE-2024-3573?

CVE-2024-3573 has a CVSS 3.x base score of 9.3, 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 low, and availability none.

Is CVE-2024-3573 being actively exploited?

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

What products are affected by CVE-2024-3573?

CVE-2024-3573 affects Lfprojects Mlflow. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2024-3573?

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-2024-3573 have an EU (EUVD) identifier?

Yes. CVE-2024-3573 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-1218.

When was CVE-2024-3573 published?

CVE-2024-3573 was published on 2024-04-16 and last updated on 2026-06-17.

CVE-2024-3573

CVE-2024-3573 is a critical-severity vulnerability in Lfprojects Mlflow with a CVSS 3.x base score of 9.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-22.

Key facts

Severity: Critical (CVSS 3.x base score 9.3)
EPSS exploit prediction: 1% (50th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2024-1218
Weakness: CWE-22
Affected product: Lfprojects Mlflow
Published: 2024-04-16
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2024-3573?: 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.
How severe is CVE-2024-3573?: CVE-2024-3573 has a CVSS 3.x base score of 9.3, 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 low, and availability none.
Is CVE-2024-3573 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (50th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-3573?: CVE-2024-3573 affects Lfprojects Mlflow. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-3573?: 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-2024-3573 have an EU (EUVD) identifier?: Yes. CVE-2024-3573 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-1218.
When was CVE-2024-3573 published?: CVE-2024-3573 was published on 2024-04-16 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-11201 — Critical (CVSS 9.8): MLflow Tracking Server Model Creation Directory Traversal Remote Code Execution Vulnerability. This vulnerability…
CVE-2025-11200 — Critical (CVSS 9.8): MLflow Weak Password Requirements Authentication Bypass Vulnerability. This vulnerability allows remote attackers to…

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 →