Critical

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_loc

  • Disclosed: 16.04.2024
  • Updated: 11.10.2026 12:20

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.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) mlflow < 2.10.0 2.10.0

References

CVSS score 9.3/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
Weakness (CWE)
CWE-29
Platform
Python (PyPI)
Package
mlflow
Disclosed
16.04.2024
Updated
11.10.2026 12:20

Sources and licenses

OSV / GitHub Advisory Database - GHSA-hq88-wg7q-gp4g - CC BY 4.0

OSV / GitHub Advisory Database - PYSEC-2024-243 - PyPA Advisory Database; CC BY 4.0

Vulnerability history: mlflow

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (82) in the archive
Total entries
82
First → latest
02.2022 09.2026
Without a fix
18
Exploited in attacks
1

Severity breakdown

  • Critical 20
  • High 48
  • Medium 13
  • Low 1

Disclosures per year

  1. 2022: 1
  2. 2023: 22
  3. 2024: 24
  4. 2025: 8
  5. 2026: 27
Severity:
  1. 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_loc this entry
    Critical · 9.3 CVE-2024-3573 < 2.10.0 2.10.0
  2. High · 7.1 CVE-2026-71211 >= 3.13.0, <= 3.15.2 no fix
  3. High · 8.1 CVE-2026-8147 >= 2.14.0rc0, < 3.13.0rc0 3.13.0rc0
  4. High · 7.0 CVE-2026-4137 >= 1.26.0, < 3.11.0 3.11.0
  5. Critical · 10.0 CVE-2025-15379 < 3.8.1 3.8.1
  6. Critical · 9.6 CVE-2025-15036 < 3.9.0rc0 3.9.0rc0
  7. High · 8.1 CVE-2025-15381 <= 3.8.1 no fix
  8. High · 8.1 CVE-2025-15031 < 3.9.0rc0 3.9.0rc0
  9. High · 7.5 CVE-2025-14287 < 3.8.0rc0 3.8.0rc0
  10. Critical · 9.8 CVE-2026-2635 < 3.8.0rc0 3.8.0rc0
Show more (20) Showing 21 of 68

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.