Vulnerability database · updated every 15 minutes

New vulnerabilities in the software websites run.

CVEs and security advisories for WordPress, its plugins and themes, npm, PyPI and the servers behind websites, merged from NVD, the CVE Program, GitHub, OSV.dev and WPVulnerability, with CISA's list of the ones attackers exploit.

Free · right away or once a day · unsubscribe in one click
Tracked
55,384
Published in 7 days
1,885
Critical in 30 days
489
Actively exploited
542
Clear filters

Results for “MLflow”

89 vulnerabilities
  1. High 8.8

    CVE-2024-37058 · MLflow

    Deserialization of untrusted data can occur in versions of the MLflow platform running version 2.5.0 or newer, enabling a maliciously uploaded Langchain AgentExecutor model to run arbitrary code on an end user’s system when interacted with.

    Published 4 Jun 2024 · NVD
  2. High 8.8

    CVE-2024-37057 · MLflow

    Deserialization of untrusted data can occur in versions of the MLflow platform running version 2.0.0rc0 or newer, enabling a maliciously uploaded Tensorflow model to run arbitrary code on an end user’s system when interacted with.

    Published 4 Jun 2024 · NVD
  3. High 8.8

    CVE-2024-37056 · MLflow

    Deserialization of untrusted data can occur in versions of the MLflow platform running version 1.23.0 or newer, enabling a maliciously uploaded LightGBM scikit-learn model to run arbitrary code on an end user’s system when interacted with.

    Published 4 Jun 2024 · NVD
  4. High 8.8

    CVE-2024-37055 · MLflow

    Deserialization of untrusted data can occur in versions of the MLflow platform running version 1.24.0 or newer, enabling a maliciously uploaded pmdarima model to run arbitrary code on an end user’s system when interacted with.

    Published 4 Jun 2024 · NVD
  5. High 8.8

    CVE-2024-37054 · MLflow

    Deserialization of untrusted data can occur in versions of the MLflow platform running version 0.9.0 or newer, enabling a maliciously uploaded PyFunc model to run arbitrary code on an end user’s system when interacted with.

    Published 4 Jun 2024 · NVD
  6. High 8.8

    CVE-2024-37053 · MLflow

    Deserialization of untrusted data can occur in versions of the MLflow platform running version 1.1.0 or newer, enabling a maliciously uploaded scikit-learn model to run arbitrary code on an end user’s system when interacted with.

    Published 4 Jun 2024 · NVD
  7. High 8.8

    CVE-2024-37052 · MLflow

    Deserialization of untrusted data can occur in versions of the MLflow platform running version 1.1.0 or newer, enabling a maliciously uploaded scikit-learn model to run arbitrary code on an end user’s system when interacted with.

    Published 4 Jun 2024 · NVD
  8. Medium 5.4

    CVE-2024-4263 · MLflow

    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…

    Published 16 May 2024 · Fixed in 2.12.1 · NVD
  9. High 7.5

    CVE-2024-3848 · MLflow

    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…

    Published 16 May 2024 · Fixed in 2.12.1 · NVD
  10. Critical 9.3

    CVE-2024-3573 · MLflow

    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…

    Published 16 Apr 2024 · Fixed in 2.10.0 · NVD
  11. High 7.5

    CVE-2024-1594 · MLflow

    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 read arbitrary files on the server in the context of the server's process. This issue is similar to CVE-2023-6909 but…

    Published 16 Apr 2024 · Fixed in 2.11.3 · NVD
  12. High 7.5

    CVE-2024-1593 · MLflow

    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 or directories. This vulnerability allows for arbitrary data smuggling into the 'params' part of the URL, enabling…

    Published 16 Apr 2024 · Fixed in 2.11.3 · NVD
  13. High 8.1

    CVE-2024-1560 · MLflow

    A path traversal vulnerability exists in the mlflow/mlflow repository, specifically within the artifact deletion functionality. Attackers can bypass path validation by exploiting the double decoding process in the `_delete_artifact_mlflow_artifacts` handler and `local_file_uri_to_path` function, allowing for the deletion of arbitrary directories on the server's filesystem. This vulnerability is…

    Published 16 Apr 2024 · NVD
  14. High 7.5

    CVE-2024-1558 · MLflow

    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 bypasses the `_validate_non_local_source_contains_relative_paths(source)` function's checks, allowing for arbitrary file…

    Published 16 Apr 2024 · Fixed in 2.12.1 · NVD
  15. High 7.5

    CVE-2024-1483 · MLflow

    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…

    Published 16 Apr 2024 · Fixed in 2.12.1 · NVD
  16. Critical 9.6

    CVE-2024-27133 · MLflow

    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.

    Published 23 Feb 2024 · NVD
  17. Critical 9.6

    CVE-2024-27132 · MLflow

    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.

    Published 23 Feb 2024 · NVD
  18. High 7.5

    CVE-2023-6977 · MLflow

    This vulnerability enables malicious users to read sensitive files on the server.

    Published 20 Dec 2023 · Fixed in 2.9.2 · NVD
  19. High 8.8

    CVE-2023-6976 · MLflow

    This vulnerability is capable of writing arbitrary files into arbitrary locations on the remote filesystem in the context of the server process.

    Published 20 Dec 2023 · Fixed in 2.9.2 · NVD
  20. Critical 9.8

    CVE-2023-6975 · MLflow

    A malicious user could use this issue to get command execution on the vulnerable machine and get access to data & models information.

    Published 20 Dec 2023 · Fixed in 2.9.2 · NVD
  21. Critical 9.8

    CVE-2023-6974 · MLflow

    A malicious user could use this issue to access internal HTTP(s) servers and in the worst case (ie: aws instance) it could be abuse to get a remote code execution on the victim machine.

    Published 20 Dec 2023 · Fixed in 2.9.2 · NVD
  22. High 8.8

    CVE-2023-6940 · MLflow

    with only one user interaction(download a malicious config), attackers can gain full command execution on the victim system.

    Published 19 Dec 2023 · Fixed in 2.9.2 · NVD
  23. High 7.5

    CVE-2023-6909 · MLflow

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

    Published 18 Dec 2023 · Fixed in 2.9.2 · NVD
  24. High 8.1

    CVE-2023-6831 · MLflow

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

    Published 15 Dec 2023 · Fixed in 2.9.2 · NVD
  25. High 8.8

    CVE-2023-6753 · MLflow

    Path Traversal in GitHub repository mlflow/mlflow prior to 2.9.2.

    Published 13 Dec 2023 · Fixed in 2.9.2 · NVD
  26. High 8.8

    CVE-2023-6709 · MLflow

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

    Published 12 Dec 2023 · Fixed in 2.9.2 · NVD
  27. Medium 6.1

    CVE-2023-6568 · MLflow

    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…

    Published 7 Dec 2023 · NVD
  28. High 7.5

    CVE-2023-43472 · MLflow

    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.

    Published 5 Dec 2023 · NVD
  29. Critical 9.8

    CVE-2023-6014 · MLflow

    An attacker is able to arbitrarily create an account in MLflow bypassing any authentication requirment.

    Published 16 Nov 2023 · NVD
  30. High 7.5

    CVE-2023-6015 · MLflow

    MLflow allowed arbitrary files to be PUT onto the server.

    Published 16 Nov 2023 · Fixed in 2.8.1 · NVD
  31. High 7.8

    CVE-2023-4033 · MLflow

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

    Published 1 Aug 2023 · Fixed in 2.6.0 · NVD
  32. Critical 10.0

    CVE-2023-3765 · MLflow

    Absolute Path Traversal in GitHub repository mlflow/mlflow prior to 2.5.0.

    Published 19 Jul 2023 · Fixed in 2.5.0 · NVD
  33. Critical 9.8

    CVE-2023-2780 · MLflow

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

    Published 17 May 2023 · Fixed in 2.3.1 · NVD
  34. High 7.5

    CVE-2023-30172 · MLflow

    A directory traversal vulnerability in the /get-artifact API method of the mlflow platform up to v2.0.1 allows attackers to read arbitrary files on the server via the path parameter.

    Published 11 May 2023 · Fixed in 2.0.1 · NVD
  35. Critical

    GHSA-83fm-w79m-64r5 · MLflow

    Remote file access vulnerability in `mlflow server` and `mlflow ui` CLIs

    Published 28 Apr 2023 · Fixed in 2.3.1 · Project advisories (GitHub)
  36. High 7.5

    CVE-2023-2356 · MLflow

    Relative Path Traversal in GitHub repository mlflow/mlflow prior to 2.3.1.

    Published 28 Apr 2023 · Fixed in 2.3.1 · NVD
  37. Low 3.3

    CVE-2023-1176 · MLflow

    Remote file existence check vulnerability in `mlflow server` and `mlflow ui` CLIs

    Published 24 Mar 2023 · Fixed in 2.2.1, 2.2.2 · NVD, Project advisories (GitHub)
  38. Critical 9.8

    CVE-2023-1177 · MLflow

    Remote file access vulnerability in `mlflow server` and `mlflow ui` CLIs

    Published 24 Mar 2023 · Fixed in 2.2.1 · NVD, Project advisories (GitHub)
  39. High 7.5

    CVE-2022-0736 · MLflow

    Insecure Temporary File in GitHub repository mlflow/mlflow prior to 1.23.1.

    Published 23 Feb 2022 · Fixed in 1.23.1 · NVD

Where it comes from

The list holds every advisory UpHeron reads for the software it watches: WordPress and every plugin and theme its plugin reports, the packages in monitored repositories and manifests, and the servers and frameworks found on monitored websites. One vulnerability from several sources is one entry, under its CVE.

  • NVD, the US National Vulnerability Database. This product uses the NVD API but is not endorsed or certified by the NVD.
  • New and changed records of the CVE Program, read every 15 minutes, so a rating or fix added after a CVE is published reaches the list, and its alerts, within the hour. CVE content © 1999–2026 The MITRE Corporation, used under the CVE terms of use; CVE® is a registered trademark of The MITRE Corporation.
  • OSV.dev, with the GitHub Advisory Database (CC BY 4.0).
  • WPVulnerability (CC0) for WordPress plugins and themes, and WordPress's own security advisories.
  • Node.js's own security release posts, read every 15 minutes, which name its vulnerabilities the day they are fixed, days before their CVE records.
  • The security advisories projects publish on GitHub, and the CVEs libraries such as Brotli name in their release notes, which also count for the runtimes that bundle them.
  • CISA's Known Exploited Vulnerabilities catalog.

Each day's new ones, grouped, and every critical one as soon as we find it: on the blog.

Run WordPress? The UpHeron plugin alerts you the day one of these affects your own site.