CVE-2026-79721

HIGHPre-NVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.6Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Code execution can occur in versions of the MLflow platform running version 0.0.1 or newer, enabling a maliciously crafted model artifact to execute arbitrary code on an end user's system when loaded by the project.

CVSS v3
8.6
EG Score
8.6(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity86% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

September 8, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated Sep 8, 2026
No patch confirmed yet.
generic
https://www.hiddenlayer.com/sai-security-advisory/2026-09-mlflow

Vendor Advisories for CVE-2026-79721(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 24× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 13:22 UTCGHSA enrichment
  2. 2026-09-19 01:30 UTCEG score recompute
  3. 2026-09-19 01:30 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 13:39 UTCGHSA enrichment
  6. 2026-09-18 01:47 UTCEG score recompute
  7. 2026-09-18 01:47 UTCGHSA enrichment
  8. 2026-09-17 13:55 UTCGHSA enrichment
  9. 2026-09-17 02:03 UTCGHSA enrichment
  10. 2026-09-16 14:11 UTCEG score recompute
  11. 2026-09-16 14:11 UTCGHSA enrichment
  12. 2026-09-16 14:08 UTCEPSS rescore
  13. 2026-09-16 05:15 UTCEPSS rescore
  14. 2026-09-16 02:19 UTCGHSA enrichment
  15. 2026-09-15 14:27 UTCEG score recompute
  16. 2026-09-15 14:27 UTCGHSA enrichment
  17. 2026-09-15 03:12 UTCEPSS rescore
  18. 2026-09-15 03:12 UTCEPSS rescore
  19. 2026-09-15 02:35 UTCGHSA enrichment
  20. 2026-09-14 14:43 UTCGHSA enrichment
  21. 2026-09-14 02:51 UTCEG score recompute
  22. 2026-09-14 02:51 UTCGHSA enrichment
  23. 2026-09-13 14:59 UTCGHSA enrichment
  24. 2026-09-13 03:07 UTCGHSA enrichment
  25. 2026-09-12 15:15 UTCEG score recompute
Show 16 more
  1. 2026-09-12 15:15 UTCGHSA enrichment
  2. 2026-09-12 03:23 UTCGHSA enrichment
  3. 2026-09-11 15:31 UTCEG score recompute
  4. 2026-09-11 15:31 UTCGHSA enrichment
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 03:39 UTCGHSA enrichment
  8. 2026-09-10 15:47 UTCEG score recompute
  9. 2026-09-10 15:47 UTCGHSA enrichment
  10. 2026-09-10 03:55 UTCGHSA enrichment
  11. 2026-09-09 16:03 UTCGHSA enrichment
  12. 2026-09-09 07:24 UTCGHSA enrichment
  13. 2026-09-08 19:33 UTCEG score recompute
  14. 2026-09-08 19:02 UTCEG score recompute
  15. 2026-09-08 18:31 UTCEG score recompute
  16. 2026-09-08 18:29 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-79721?
CVE-2026-79721 is a high vulnerability published on September 8, 2026. Code execution can occur in versions of the MLflow platform running version 0.0.1 or newer, enabling a maliciously crafted model artifact to execute arbitrary code on an end user's system when loaded by the project.
When was CVE-2026-79721 disclosed?
CVE-2026-79721 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-79721 actively exploited?
CVE-2026-79721 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.9% of all scored CVEs.
What is the CVSS score of CVE-2026-79721?
CVE-2026-79721 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-79721?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-79721, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-79721

Explore →

Is Your Infrastructure Affected by CVE-2026-79721?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs