Skip to content
major vulnerability· requires attention

RCE in MLflow, a widely used ML platform; enables host compromise and supply‑chain style attacks across organizations.

AI/ML

CVE-2026-79721

8.6
High
EPSS 0.29%Sep 11, 2026

Remote code execution via malicious MLflow model artifact.

common questions

Is CVE-2026-79721 being exploited?

Not confirmed. CVE-2026-79721 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 0.29% probability of exploitation in the next 30 days.

How severe is CVE-2026-79721?

CVE-2026-79721 is rated High with a CVSS score of 8.6. 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-79721?

Not known from our data. No patch reference has been recorded for CVE-2026-79721, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-79721 affect?

CVE-2026-79721 affects MLflow (>= 0.0.1), MLflow Projects, Environments that load third-party model artifacts. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-79721?

Stop loading untrusted models, isolate ML runtimes, enforce artifact signing, apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
MLflow (>= 0.0.1)MLflow ProjectsEnvironments that load third-party model artifacts
impact

Arbitrary code execution on host when loading a crafted model artifact; attacker can run commands, steal data, and pivot.

action required

Immediate action required

affected versions
mlflow mlflow
  • affected>= 0.0.1 and <= *

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free