CVE-2026-2033: Mlflow Remote Code Execution Vulnerability

HIGH
Advisory Identifier: GHSA-q2r8-vmq7-fpx2
CVSS 8.1
CWE-22
Published
Advisory Summary

CVE-2026-2033 is a HIGH (CVSS 8.1) remote code execution vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting Mlflow libraries in the PyPI ecosystem. The issue involves mlflow tracking server artifact handler directory traversal remote code execution vulnerability. Remediation is available by upgrading affected packages to version 3.8.0rc0.

CVE-2026-2033 at a Glance

CVE Identifier CVE-2026-2033
GHSA Identifier GHSA-q2r8-vmq7-fpx2
Severity HIGH
CVSS v3.1 Base Score 8.1
CWE Classification CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Affected Product Mlflow
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 8.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-2033

To remediate this vulnerability, upgrade all affected Mlflow dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

mlflow fixed: 3.8.0rc0
pip install mlflow>=3.8.0rc0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show mlflow

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-2033, inspect your installed packages using pip:

pip show mlflow

Analyze the terminal output to locate any version of Mlflow in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.8.0rc0), your application is affected.

Note: The pip show mlflow command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In Mlflow, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

MLflow Tracking Server Artifact Handler 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 artifact 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.

CVE-2026-2033 Affected Mlflow Versions

1 component(s)
Fixed Versions:
3.8.0rc0
Product / Package Ecosystem Affected Versions Fixed Version
mlflow
PyPI
< 3.8.0rc0
3.8.0rc0

References

Frequently Asked Questions

What is CVE-2026-2033?
CVE-2026-2033 is a security vulnerability in Mlflow involving MLflow Tracking Server Artifact Handler Directory Traversal Remote Code Execution Vulnerability under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
Which Mlflow versions are affected?
Affected versions include releases prior to 3.8.0rc0 across affected packages: mlflow.
What version fixes CVE-2026-2033?
Upgrading to 3.8.0rc0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is mlflow affected?
Yes, mlflow is affected in releases prior to 3.8.0rc0. Upgrade your dependency to 3.8.0rc0 or later.
What is the CVSS score of CVE-2026-2033?
CVE-2026-2033 has a CVSS v3.1 base score of 8.1 (HIGH) with vector string CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-2033?
CVE-2026-2033 is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.).
How can I check PyPI dependencies for CVE-2026-2033?
Run the dependency tree command: 'pip show mlflow'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-q2r8-vmq7-fpx2",
  "modified" : "2026-03-17T20:03:07Z",
  "published" : "2026-02-21T00:31:43Z",
  "aliases" : [ "CVE-2026-2033" ],
  "summary" : "MLflow Tracking Server Artifact Handler Directory Traversal Remote Code Execution Vulnerability",
  "details" : "MLflow Tracking Server Artifact Handler 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.\n\nThe specific flaw exists within the handling of artifact 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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "mlflow"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.8.0rc0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-2033"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/mlflow/mlflow/pull/19260"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/mlflow/mlflow/commit/5bf2ec2bd4222a18d78631183ac7f6b752afe8a4"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/mlflow/mlflow"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/mlflow/mlflow/releases/tag/v3.8.0rc0"
  }, {
    "type" : "WEB",
    "url" : "https://www.zerodayinitiative.com/advisories/ZDI-26-105"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-17T20:03:07Z",
    "nvd_published_at" : "2026-02-20T23:16:03Z"
  }
}