Overview 6 matches · 0 in Waratek scope · 0 protected · 1 exploited · 0 CISA KEV · 1 public PoC · 1 EPSS ≥ 0.5
6matches
0in Waratek scope0.0%
0protected0.0%
1exploited16.7%
0CISA KEV0.0%
1public PoC16.7%
1EPSS ≥ 0.516.7%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
0
0.0%
Not applicable
6
100.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
6
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
1
16.7%
Working exploit published
0
0.0%
Proof of concept only
1
16.7%
Forecast only
0
0.0%
No public exploit
4
66.7%
split by
peak 2 / quarter
Q2 241
Not applicable1
High1
not blocked1
No public exploit1
Q3 240
Q4 240
Q1 251
Not applicable1
High1
not blocked1
Proof of concept only1
Q2 251
Not applicable1
Medium1
not blocked1
No public exploit1
Q3 250
Q4 252
Not applicable2
Critical2
not blocked2
Exploited1
No public exploit1
Q1 261
Not applicable1
High1
not blocked1
No public exploit1
Q2 24Q3 24Q4 24Q1 25Q2 25Q3 25Q4 25Q1 26
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2025-14279 | High | 2026-01-12 | Not applicable | No public exploit | MLFlow versions up to and including 3.4.0 are vulnerable to DNS rebinding attacks due to a lack of Origin header validation in the MLFlow REST server. This vulnerability allows malicious websites to bypass Same-Origin Policy protections and execute unauthorized calls against REST endpoints. An attacker can query, update, and delete experiments via the affected endpoints, leading to potential data exfiltration, destruction, or manipulation. The issue is resolved in version 3.5.0. |
| CVE-2025-11201 | Critical | 2025-10-29 | Not applicable | Exploited | MLflow Tracking Server Model Creation Directory Traversal Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of MLflow Tracking Server. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of model file paths. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to execute code in the context of the service account. Was ZDI-CAN-26921. |
| CVE-2025-11200 | Critical | 2025-10-29 | Not applicable | No public exploit | MLflow Weak Password Requirements Authentication Bypass Vulnerability. This vulnerability allows remote attackers to bypass authentication on affected installations of MLflow. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of passwords. The issue results from weak password requirements. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-26916. |
| CVE-2025-52967 | Medium | 2025-06-23 | Not applicable | No public exploit | gateway_proxy_handler in MLflow before 3.1.0 lacks gateway_path validation. |
| CVE-2025-0453 | High | 2025-03-20 | Not applicable | Proof of concept only | In mlflow/mlflow version 2.17.2, the `/graphql` endpoint is vulnerable to a denial of service attack. An attacker can create large batches of queries that repeatedly request all runs from a given experiment. This can tie up all the workers allocated by MLFlow, rendering the application unable to respond to other requests. This vulnerability is due to uncontrolled resource consumption. |
| CVE-2024-37059 | High | 2024-06-04 | Not applicable | No public exploit | Deserialization of untrusted data can occur in versions of the MLflow platform running version 0.5.0 or newer, enabling a maliciously uploaded PyTorch model to run arbitrary code on an end user’s system when interacted with. |