CVE-2026-2033
MLflow Tracking Server artifact handler path traversal enables unauthenticated RCE.
Is CVE-2026-2033 being exploited?
Not confirmed. CVE-2026-2033 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.7% probability of exploitation in the next 30 days.
How severe is CVE-2026-2033?
CVE-2026-2033 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-2033?
Yes. A fix has been recorded for CVE-2026-2033. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-2033 affect?
CVE-2026-2033 affects MLflow Tracking Server. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-2033?
Patch/upgrade to fixed MLflow version.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via unsanitized artifact paths on MLflow Tracking Server with no auth.
Immediate action required
- affected3.1.1 and 5b9c01925c2e2a8cf0951f155a6a468ff99cfe0f
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.