Mlflow vulnerabilitiesRanked by how likely they are to be used.
Mlflow is made by Lfprojects. We track 53 published vulnerabilities in it, across 134 versions. None of them is on the list of flaws known to be exploited today. If you run Mlflow, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Mlflow vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Mlflow's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Mlflow flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 90%CVE-2023-6909High
Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.9.2.
- 71%CVE-2023-3765Critical
Absolute Path Traversal in GitHub repository mlflow/mlflow prior to 2.5.0.
- 69%CVE-2023-1177Critical
Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.2.1.
- 48%CVE-2023-6018Critical
An attacker can overwrite any file on the server hosting MLflow without any authentication.
- 43%CVE-2024-3848High
A path traversal vulnerability exists in mlflow/mlflow version 2.11.0, identified as a bypass for the previously addressed CVE-2023-6909.
- 37%CVE-2023-43472High
An issue in MLFlow versions 2.8.1 and before allows a remote attacker to obtain sensitive information via a crafted request to REST API.
- 27%CVE-2025-11201Critical
MLflow Tracking Server Model Creation Directory Traversal Remote Code Execution Vulnerability.
- 22%CVE-2024-2928High
A Local File Inclusion (LFI) vulnerability was identified in mlflow/mlflow, specifically in version 2.9.2, which was fixed in version 2.11.3.
- 6.3%CVE-2023-2780Critical
Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.3.1.
- 4.4%CVE-2023-6015High
MLflow allowed arbitrary files to be PUT onto the server.
Running Mlflow? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.9.2.
- Matched to
- Mlflow on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 53 published vulnerabilities listed under the name Mlflow, across 134 versions.
None of Mlflow's vulnerabilities is on the list of flaws known to be exploited today.
Create a EdgeProtect account and track Mlflow. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.