Mlflow vulnerabilitiesAnd the versions its exploited flaws hit.
Mlflow is made by Lfprojects. We track 53 published vulnerabilities in it, across 134 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 19 August 2026. If you run Mlflow, check your version against the exploited flaws below and patch those first.
The most recent Mlflow flaw added to the known-exploited list is CVE-2026-64849, on 19 August 2026. We keep watching the known-exploited list.
Which versions of Mlflow do the exploited flaws hit?
Each exploited flaw lists the versions it affects, usually as ranges. "3.3.0 to before 3.15.0" means from 3.3.0 up to, but not including, 3.15.0. Find your version, then patch.
- CVE-2026-64849Exploited list, 19 Aug 2026
MLflow Server-Side Request Forgery Vulnerability
3.3.0 to before 3.15.0
Which Mlflow vulnerabilities are being exploited?
1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 9.3MLflow Server-Side Request Forgery Vulnerability
MLflow contains a server-side request forgery vulnerability that can allow attackers to reach internal or cloud metadata services and receive response_status and response_body.
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.
- 70%CVE-2023-1177Critical
Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.2.1.
- 68%CVE-2023-3765Critical
Absolute Path Traversal in GitHub repository mlflow/mlflow prior to 2.5.0.
- 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.
- 26%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.
- 11%CVE-2025-0453High
In mlflow/mlflow version 2.17.2, the `/graphql` endpoint is vulnerable to a denial of service attack.
- 9.8%
MLflow is an open source AI engineering platform for agents, large language models, and machine learning models.
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 flaw being exploited affects software Acme tracks
MLflow contains a server-side request forgery vulnerability that can allow attackers to reach internal or cloud metadata services and receive response_status and response_body.
- Matched to
- Mlflow on Acme's software list
- What to do
- Patch first, then check for signs of use
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. The most recent Mlflow flaw added to the known-exploited list is CVE-2026-64849, on 19 August 2026.
1 is on the list of flaws known to be exploited. The most recently added is CVE-2026-64849.
Each flaw names its own versions, usually as ranges. The newest, CVE-2026-64849, affects 3.3.0 to before 3.15.0. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence 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.