VYPR

Mlflow

by Mlflow

pypi: mlflow

Source repositories

CVEs (95)

  • CVE-2023-6709HigDec 12, 2023
    risk 0.50cvss 8.8epss 0.01

    Improper Neutralization of Special Elements Used in a Template Engine in GitHub repository mlflow/mlflow prior to 2.9.2.

  • CVE-2024-1594HigApr 16, 2024
    risk 0.49cvss 7.5epss 0.01

    A path traversal vulnerability exists in the mlflow/mlflow repository, specifically within the handling of the `artifact_location` parameter when creating an experiment. Attackers can exploit this vulnerability by using a fragment component `#` in the artifact location URI to…

  • CVE-2024-1593HigApr 16, 2024
    risk 0.49cvss 7.5epss 0.01

    A path traversal vulnerability exists in the mlflow/mlflow repository due to improper handling of URL parameters. By smuggling path traversal sequences using the ';' character in URLs, attackers can manipulate the 'params' portion of the URL to gain unauthorized access to files…

  • CVE-2024-1558HigApr 16, 2024
    risk 0.49cvss 7.5epss 0.01

    A path traversal vulnerability exists in the `_create_model_version()` function within `server/handlers.py` of the mlflow/mlflow repository, due to improper validation of the `source` parameter. Attackers can exploit this vulnerability by crafting a `source` parameter that…

  • CVE-2024-1483HigApr 16, 2024
    risk 0.49cvss 7.5epss 0.03

    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…

  • CVE-2023-6909HigDec 18, 2023
    risk 0.49cvss 7.5epss 0.90

    Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.9.2.

  • CVE-2026-118628HigNov 4, 2026
    risk 0.46cvss 8.2epss 0.00

    MLflow get-artifacts Server-Side Request Forgery Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of MLflow. Authentication is not required to exploit this vulnerability. The specific…

  • CVE-2026-53995HigOct 19, 2026
    risk 0.46cvss 8.2epss 0.01

    MLflow before 3.18.0 contains a path traversal vulnerability in the FileStore tracking backend that allows unauthenticated attackers to control filesystem paths by submitting a crafted trace ID containing traversal sequences to the POST /api/3.0/mlflow/traces endpoint. Attackers…

  • CVE-2026-8147HigJul 2, 2026
    risk 0.46cvss 8.1epss 0.01

    In MLflow versions prior to 3.14.0, when running with authentication enabled, the trace API endpoints lack proper authorization validators. This allows any authenticated user to bypass experiment-level authorization controls on all trace operations, including reading, deleting,…

  • CVE-2025-15381HigMar 27, 2026
    risk 0.46cvss 7.1epss 0.00

    In the latest version of mlflow/mlflow, when the `basic-auth` app is enabled, tracing and assessment endpoints are not protected by permission validators. This allows any authenticated user, including those with `NO_PERMISSIONS` on the experiment, to read trace information and…

  • CVE-2025-14279HigJan 12, 2026
    risk 0.46cvss 8.1epss 0.00

    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…

  • CVE-2023-6831HigDec 15, 2023
    risk 0.46cvss 8.1epss 0.03

    Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.9.2.

  • CVE-2024-3848HigMay 16, 2024
    risk 0.45cvss 7.5epss 0.43

    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…

  • CVE-2026-118627HigNov 4, 2026
    risk 0.44cvss 7.8epss 0.00

    MLflow SHAP load_explainer Deserialization of Untrusted Data Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of MLflow. User interaction is required to exploit this vulnerability in that the…

  • CVE-2026-118623HigNov 4, 2026
    risk 0.44cvss 7.8epss 0.00

    MLflow PickleEvaluationArtifact Deserialization of Untrusted Data Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of MLflow. User interaction is required to exploit this vulnerability in that the…

  • CVE-2026-4137HigMay 18, 2026
    risk 0.44cvss 7.8epss 0.00

    In mlflow/mlflow versions prior to 3.11.0, the `get_or_create_nfs_tmp_dir()` function in `mlflow/utils/file_utils.py` creates temporary directories with world-writable permissions (0o777), and the `_create_model_downloading_tmp_dir()` function in `mlflow/pyfunc/__init__.py`…

  • CVE-2026-0596HigMar 31, 2026
    risk 0.44cvss 7.8epss 0.01

    A command injection vulnerability exists in mlflow/mlflow when serving a model with `enable_mlserver=True`. The `model_uri` is embedded directly into a shell command executed via `bash -c` without proper sanitization. If the `model_uri` contains shell metacharacters, such as…

  • CVE-2023-4033HigAug 1, 2023
    risk 0.44cvss 7.8epss 0.01

    OS Command Injection in GitHub repository mlflow/mlflow prior to 2.6.0.

  • CVE-2026-4035HigJun 3, 2026
    risk 0.43cvss 7.7epss 0.01

    A vulnerability in mlflow/mlflow versions prior to 3.11.0 allows for the resolution of environment variables in AI Gateway secrets, which can be exploited to exfiltrate sensitive server-side environment credentials to an attacker-controlled endpoint. This issue arises because…

  • CVE-2024-2928HigJun 6, 2024
    risk 0.43cvss 7.5epss 0.22

    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…