Overview 11 matches · 0 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 1 EPSS ≥ 0.5
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
11
100.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
11
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
11
100.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
0
0.0%
split by
peak 5 / quarter
Q2 231
Not applicable1
Critical1
not blocked1
Working exploit published1
Q3 231
Not applicable1
Critical1
not blocked1
Working exploit published1
Q4 235
Not applicable5
Critical1
High3
Medium1
not blocked5
Working exploit published5
Q1 240
Q2 242
Not applicable2
High2
not blocked2
Working exploit published2
Q3 240
Q4 240
Q1 251
Not applicable1
High1
not blocked1
Working exploit published1
Q2 250
Q3 250
Q4 250
Q1 260
Q2 261
Not applicable1
Critical1
not blocked1
Working exploit published1
Q2 23Q4 23Q2 24Q4 24Q2 25Q4 25Q2 26
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-0545 | Critical | 2026-04-03 | Not applicable | Working exploit published | In mlflow/mlflow, the FastAPI job endpoints under `/ajax-api/3.0/jobs/*` are not protected by authentication or authorization when the `basic-auth` app is enabled. This vulnerability affects the latest version of the repository. If job execution is enabled (`MLFLOW_SERVER_ENABLE_JOB_EXECUTION=true`) and any job function is allowlisted, any network client can submit, read, search, and cancel jobs without credentials, bypassing basic-auth entirely. This can lead to unauthenticated remote code execution if allowed jobs perform privileged actions such as shell execution or filesystem changes. Even if jobs are deemed safe, this still constitutes an authentication bypass, potentially resulting in job spam, denial of service (DoS), or data exposure in job results. |
| CVE-2024-8859 | High | 2025-03-20 | Not applicable | Working exploit published | A path traversal vulnerability exists in mlflow/mlflow version 2.15.1. When users configure and use the dbfs service, concatenating the URL directly into the file protocol results in an arbitrary file read vulnerability. This issue occurs because only the path part of the URL is checked, while parts such as query and parameters are not handled. The vulnerability is triggered if the user has configured the dbfs service, and during usage, the service is mounted to a local directory. |
| CVE-2024-2928 | High | 2024-06-06 | Not applicable | Working exploit published | 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. This vulnerability arises from the application's failure to properly validate URI fragments for directory traversal sequences such as '../'. An attacker can exploit this flaw by manipulating the fragment part of the URI to read arbitrary files on the local file system, including sensitive files like '/etc/passwd'. The vulnerability is a bypass to a previous patch that only addressed similar manipulation within the URI's query string, highlighting the need for comprehensive validation of all parts of a URI to prevent LFI attacks. |
| CVE-2024-1483 | High | 2024-04-16 | Not applicable | Working exploit published | A path traversal vulnerability exists in mlflow/mlflow version 2.9.2, allowing attackers to access arbitrary files on the server. By crafting a series of HTTP POST requests with specially crafted 'artifact_location' and 'source' parameters, using a local URI with '#' instead of '?', an attacker can traverse the server's directory structure. The issue occurs due to insufficient validation of user-supplied input in the server's handlers. |
| CVE-2023-6977 | High | 2023-12-20 | Not applicable | Working exploit published | This vulnerability enables malicious users to read sensitive files on the server. |
| CVE-2023-6831 | High | 2023-12-15 | Not applicable | Working exploit published | Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.9.2. |
| CVE-2023-6568 | Medium | 2023-12-07 | Not applicable | Working exploit published | A reflected Cross-Site Scripting (XSS) vulnerability exists in the mlflow/mlflow repository, specifically within the handling of the Content-Type header in POST requests. An attacker can inject malicious JavaScript code into the Content-Type header, which is then improperly reflected back to the user without adequate sanitization or escaping, leading to arbitrary JavaScript execution in the context of the victim's browser. The vulnerability is present in the mlflow/server/auth/__init__.py file, where the user-supplied Content-Type header is directly injected into a Python formatted string and returned to the user, facilitating the XSS attack. |
| CVE-2023-43472 | High | 2023-12-05 | Not applicable | Working exploit published | 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. |
| CVE-2023-6018 | Critical | 2023-11-16 | Not applicable | Working exploit published | An attacker can overwrite any file on the server hosting MLflow without any authentication. |
| CVE-2023-3765 | Critical | 2023-07-19 | Not applicable | Working exploit published | Absolute Path Traversal in GitHub repository mlflow/mlflow prior to 2.5.0. |
| CVE-2023-2780 | Critical | 2023-05-17 | Not applicable | Working exploit published | Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.3.1. |