Security readout for executives and security teams
Plain-English summary
CVE-2026-2033 is a high-severity MLflow Tracking Server issue where unsafe artifact path handling can let a remote unauthenticated attacker run code as the service account. Business risk is highest where MLflow tracking endpoints are reachable from untrusted networks.
Executive priority
Treat as a priority remediation item for MLflow environments, especially exposed tracking servers. The issue combines unauthenticated remote access with potential code execution, but current sources do not show confirmed exploitation.
Technical view
The flaw is a CWE-22 directory traversal in MLflow Tracking Server artifact file path handling. ZDI reports insufficient validation before file operations, enabling arbitrary code execution in the service context. CVSS is 8.1 with network attack vector, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is likely limited to organizations running affected MLflow Tracking Server versions, specifically MLflow 3.1.1 and commit 5b9c01925c2e2a8cf0951f155a6a468ff99cfe0f as listed. Internet-facing or broadly reachable tracking servers carry the most urgent risk.
Exploitation context
The source bundle says authentication is not required. It does not cite active exploitation, and KEV is false. No exploit details or weaponization guidance should be inferred from the available evidence.
Researcher notes
Evidence is strongest for the vulnerability class, impact, and affected identifiers from ZDI and CVE data. Public source details provided here do not establish fixed versions, real-world exploitation, or Red Hat product impact beyond linked tracking entries.
Mitigation direction
- Identify all MLflow Tracking Server instances and their exposed network paths.
- Check MLflow vendor guidance and PR 19260 for the supported fix path.
- Remove public or untrusted access to MLflow tracking endpoints where possible.
- Run MLflow services with least-privilege service accounts.
- Monitor logs for unusual artifact path access or unexpected file operations.
Validation and detection
- Confirm whether MLflow 3.1.1 or the listed commit is deployed.
- Verify tracking server artifact endpoints are not internet-accessible unless required.
- Review MLflow release notes and vendor advisory status before patching.
- Check service account permissions and reduce filesystem write access.
- Look for suspicious artifact requests without reproducing exploit behavior.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupExecution 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 lookupFile 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 lookupCVE-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- 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
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9zdiCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L3.93.4redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
7.3HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Base CVSS 3.0 score
8.1HighVector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-02-20T23:01:00.491Z: Reported to Red Hat.
- 2026-02-20T22:12:06.040Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- ZDI-26-105CVE reference, zdi · x_research-advisory
- vendor-provided URLCVE reference, zdi · vendor-advisory
- https://access.redhat.com/security/cve/CVE-2026-2033CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2441508CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-2033.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.