Search for packages
| purl | pkg:pypi/mlflow@2.9.1 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-36at-75qp-sqay
Aliases: BIT-mlflow-2023-6709 CVE-2023-6709 GHSA-cxfr-5q3r-2rc2 PYSEC-2023-281 |
Improper Neutralization of Special Elements Used in a Template Engine in GitHub repository mlflow/mlflow prior to 2.9.2. |
Affected by 16 other vulnerabilities. |
|
VCID-48xy-zsv8-8ube
Aliases: BIT-mlflow-2023-6831 CVE-2023-6831 GHSA-554w-xh4j-8w64 PYSEC-2023-253 |
Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.9.2. |
Affected by 16 other vulnerabilities. |
|
VCID-5qe9-6ecs-syek
Aliases: BIT-mlflow-2024-27133 CVE-2024-27133 GHSA-3v79-q7ph-j75h PYSEC-2024-241 |
Insufficient sanitization in MLflow leads to XSS when running a recipe that uses an untrusted dataset. This issue leads to a client-side RCE when running the recipe in Jupyter Notebook. The vulnerability stems from lack of sanitization over dataset table fields. |
Affected by 8 other vulnerabilities. |
|
VCID-6x4v-udkg-z3es
Aliases: BIT-mlflow-2024-27132 CVE-2024-27132 GHSA-6749-m5cp-6cg7 PYSEC-2024-240 |
Insufficient sanitization in MLflow leads to XSS when running an untrusted recipe. This issue leads to a client-side RCE when running an untrusted recipe in Jupyter Notebook. The vulnerability stems from lack of sanitization over template variables. |
Affected by 8 other vulnerabilities. |
|
VCID-96st-1wwr-4ken
Aliases: BIT-mlflow-2025-1474 CVE-2025-1474 GHSA-4rj2-9gcx-5qhx PYSEC-2025-17 |
In mlflow/mlflow version 2.18, an admin is able to create a new user account without setting a password. This vulnerability could lead to security risks, as accounts without passwords may be susceptible to unauthorized access. Additionally, this issue violates best practices for secure user account management. The issue is fixed in version 2.19.0. |
Affected by 3 other vulnerabilities. |
|
VCID-gr3d-61ds-j7ej
Aliases: BIT-mlflow-2024-3573 CVE-2024-3573 GHSA-hq88-wg7q-gp4g PYSEC-2024-243 |
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 by 8 other vulnerabilities. |
|
VCID-njg8-d2r5-rfax
Aliases: BIT-mlflow-2024-4263 CVE-2024-4263 GHSA-p4jx-q62p-x5jr PYSEC-2024-51 |
A broken access control vulnerability exists in mlflow/mlflow versions before 2.10.1, where low privilege users with only EDIT permissions on an experiment can delete any artifacts. This issue arises due to the lack of proper validation for DELETE requests by users with EDIT permissions, allowing them to perform unauthorized deletions of artifacts. The vulnerability specifically affects the handling of artifact deletions within the application, as demonstrated by the ability of a low privilege user to delete a directory inside an artifact using a DELETE request, despite the official documentation stating that users with EDIT permission can only read and update artifacts, not delete them. |
Affected by 7 other vulnerabilities. |
|
VCID-pugd-v7em-sbec
Aliases: BIT-mlflow-2026-33865 CVE-2026-33865 GHSA-fh64-r2vc-xvhr PYSEC-2026-93 |
MLflow is vulnerable to Stored Cross-Site Scripting (XSS) caused by unsafe parsing of YAML-based MLmodel artifacts in its web interface. An authenticated attacker can upload a malicious MLmodel file containing a payload that executes when another user views the artifact in the UI. This allows actions such as session hijacking or performing operations on behalf of the victim. This issue affects MLflow version through 3.10.1 |
Affected by 0 other vulnerabilities. |
|
VCID-qb49-yrtm-mfhm
Aliases: BIT-mlflow-2023-6753 CVE-2023-6753 GHSA-v945-r3rc-6fjm PYSEC-2023-309 |
Path Traversal in GitHub repository mlflow/mlflow prior to 2.9.2. |
Affected by 16 other vulnerabilities. |
|
VCID-qnyj-3qc7-p7bp
Aliases: BIT-mlflow-2026-33866 CVE-2026-33866 GHSA-46r5-x6jq-v8g6 PYSEC-2026-94 |
MLflow is vulnerable to an authorization bypass affecting the AJAX endpoint used to download saved model artifacts. Due to missing access‑control validation, a user without permissions to a given experiment can directly query this endpoint and retrieve model artifacts they are not authorized to access. This issue affects MLflow version through 3.10.1 |
Affected by 0 other vulnerabilities. |
|
VCID-r2kq-hqdf-6ugh
Aliases: BIT-mlflow-2024-3848 CVE-2024-3848 GHSA-rfqq-wq6w-72jm PYSEC-2024-244 |
A path traversal vulnerability exists in mlflow/mlflow version 2.11.0, identified as a bypass for the previously addressed CVE-2023-6909. The vulnerability arises from the application's handling of artifact URLs, where a '#' character can be used to insert a path into the fragment, effectively skipping validation. This allows an attacker to construct a URL that, when processed, ignores the protocol scheme and uses the provided path for filesystem access. As a result, an attacker can read arbitrary files, including sensitive information such as SSH and cloud keys, by exploiting the way the application converts the URL into a filesystem path. The issue stems from insufficient validation of the fragment portion of the URL, leading to arbitrary file read through path traversal. |
Affected by 5 other vulnerabilities. |
|
VCID-r9df-3b7p-jfcy
Aliases: BIT-mlflow-2024-27134 CVE-2024-27134 GHSA-qpgc-w4mg-6v92 PYSEC-2024-224 |
Excessive directory permissions in MLflow leads to local privilege escalation when using spark_udf. This behavior can be exploited by a local attacker to gain elevated permissions by using a ToCToU attack. The issue is only relevant when the spark_udf() MLflow API is called. |
Affected by 4 other vulnerabilities. |
|
VCID-utmm-2j11-eyh6
Aliases: BIT-mlflow-2024-2928 CVE-2024-2928 GHSA-j46q-5pxx-8vmw PYSEC-2024-242 |
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. |
Affected by 6 other vulnerabilities. |
|
VCID-xge2-eqq3-7bb9
Aliases: BIT-mlflow-2025-52967 CVE-2025-52967 GHSA-wxj7-3fx5-pp9m PYSEC-2025-52 |
gateway_proxy_handler in MLflow before 3.1.0 lacks gateway_path validation. |
Affected by 2 other vulnerabilities. |
|
VCID-xk3w-k96c-3kav
Aliases: BIT-mlflow-2023-6909 CVE-2023-6909 GHSA-5r3q-93q3-f978 PYSEC-2023-252 |
Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.9.2. |
Affected by 16 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-a9rm-cwyd-u3eh | 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. |
BIT-mlflow-2023-6568
CVE-2023-6568 GHSA-vwhf-3v6x-wff8 PYSEC-2023-260 |