LiveActive security incident?Get immediate response
CVE Record

CVE-2026-2033: MLflow Tracking Server Artifact Handler Directory Traversal Remote Code Execution Vulnerability

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. Was ZDI-CAN-26649.

HighCVSS 8.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-2033 is a high-severity MLflow Tracking Server flaw in artifact path handling. An unauthenticated remote attacker may be able to execute code as the service account. Sources do not show active exploitation or a named fixed release in the provided bundle.

Executive priority

Treat this as high priority for MLflow environments because it can lead to unauthenticated code execution. Focus first on exposed tracking servers and shared research platforms. Current sources do not prove active exploitation, but the potential impact justifies prompt validation and containment.

Technical view

The issue is CWE-22 directory traversal in artifact file path handling. ZDI describes missing validation of user-supplied paths before file operations, enabling remote code execution. CVSS is 8.1 with network attack vector, no privileges, no user interaction, high confidentiality, integrity, and availability impact, but high attack complexity.

Likely exposure

Exposure is most likely where MLflow Tracking Server is deployed, reachable over a network, and running MLflow 3.1.1 or the cited commit 5b9c01925c2e2a8cf0951f155a6a468ff99cfe0f.

Exploitation context

The source bundle says authentication is not required. It does not provide evidence of active exploitation, and CISA KEV status is false. Exploitation is rated high complexity, so urgency is significant but not automatically equivalent to widespread exploitation.

Researcher notes

Evidence is strongest for vulnerability class, impact, and affected MLflow identifiers from ZDI and CVE data. The provided bundle does not include exploit details, a confirmed fixed release, or KEV listing. Avoid assuming broader MLflow components are affected without vendor confirmation.

Mitigation direction

  • Review MLflow PR #19260 and vendor guidance for fixed versions or workarounds.
  • Restrict MLflow Tracking Server access to trusted users and networks while assessing exposure.
  • Run the service with least-privilege permissions and avoid broad filesystem write access.
  • Monitor vendor, Red Hat, and CVE records for updated remediation details.
  • Prioritize remediation for internet-facing or shared MLflow tracking deployments.

Validation and detection

  • Inventory MLflow Tracking Server deployments and record MLflow versions.
  • Check whether deployments match MLflow 3.1.1 or the cited affected commit.
  • Review whether tracking servers are reachable from untrusted networks.
  • Confirm artifact storage paths and service account filesystem permissions are constrained.
  • Track vendor advisory status and document whether a fixed version has been applied.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-2033 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.0HighCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9zdi
7.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L3.93.4redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2026-2033Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPmlflow: MLflow Tracking Server Artifact Handler Directory Traversal Remote Code Execution Vulnerability
other:Red Hat severity ratingcvssV3_1
  • 2026-02-20T23:01:00.491Z: Reported to Red Hat.
  • 2026-02-20T22:12:06.040Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MLflowMLflow3.1.1 and 5b9c01925c2e2a8cf0951f155a6a468ff99cfe0funknown
Weakness

CWE details

CWE-22

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.