Skip to main content
No exploitation reportedFix available

CVE-2026-2033

No exploitation reported by the sources we read.

  • Published2026-02-20
  • Fixed in3.8.0rc0
  • WeaknessCWE-22

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2026-02-2023:16CVE publishedNVD

Versions per branch

OSV
mlflow
BranchAffectedFixed in
3.8< 3.8.0rc03.8.0rc0

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As zdi, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • MLflowother versions: unknown
    Affected
    • = 3.1.1 and 5b9c01925c2e2a8cf0951f155a6a468ff99cfe0fno fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-02-20

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • mlflowTuxCare:PyPIfrom 2.22.4 · fixed in 2.22.4.post2+tuxcare
  • mlflowTuxCare:PyPIfrom 2.9.1 · fixed in 2.9.1.post1+tuxcare

Vendor advisories

  • CVE-2026-2033 Red Hat Product Security

    mlflow: MLflow Tracking Server Artifact Handler Directory Traversal Remote Code Execution Vulnerability

Full record on NVD

Fix

  1. Update mlflow to 3.8.0rc0

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionnone2026-02-25
  • CNACVSS 3.17.3known since 2026-10-23
  • CNACVSS 3.08.1known since 2026-10-23
  • CNAweakness (CWE)CWE-22known since 2026-10-23
  • FIRST EPSSEPSS score1.8 %2026-11-08
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryHIGH2026-03-17

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Published
2026-02-20
Last Modified
2026-07-15
NVD status
Deferred
GitHub Advisory
GHSA-q2r8-vmq7-fpx2

Frequently asked questions

What is CVE-2026-2033?

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.

Is CVE-2026-2033 actively exploited?

Active exploitation of CVE-2026-2033 has not been confirmed. Its EPSS score was 1.8% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-2033?

CVE-2026-2033 has a CVSS v3 base score of 7.3 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L.

Running mlflow? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record