CVE-2026-2611

CRITICALCVSS 9.69.6—
EchelonGraph scoreMEDIUM confidence

Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-19. a secondary CVSS source baseline 9.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: adp:redhat-sadp, epss, ghsa
Elevated
9.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: 9.6Exploit: Elevated riskExposed: 0

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

In MLflow version 3.9.0, the MLflow Assistant feature introduced improper origin validation in its /ajax-api endpoints. This vulnerability allows a remote attacker to exploit cross-origin requests from a malicious webpage to interact with the MLflow Assistant running on a victim's local machine. By bypassing the loopback-only restriction, the attacker can modify the Assistant's configuration to enable full access, which in turn allows the execution of arbitrary commands via the Claude Code sub-agent. This issue is resolved in version 3.10.0.

CVSS v3
9.6
EG Score
9.6(medium)
EG Risk
59(Track*)
EG Risk 59/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
Severity96% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

May 19, 2026

Last Modified

July 15, 2026

Advisory Details (2)

Auto-updated Aug 23, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit 8f9c8a53af90 (mlflow/mlflow)

Fix landed in mlflow/mlflow commit 8f9c8a53af90 — awaiting tagged release

https://github.com/mlflow/mlflow/commit/8f9c8a53af90842944101eb8b7d60706822c81bc
generic

huntr - The world's first bug bounty platform for AI/ML

https://huntr.com/bounties/8462addd-b464-4a84-b6a2-5529604e6e5a

Vendor Advisories for CVE-2026-2611(1)

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

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
mlflow3.10.0rc0, 3.9.03.10.0—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 44× 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.

Showing the most recent 100 of 183 total refreshes for this CVE.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-24 14:17 UTCEPSS rescore
  3. 2026-08-23 17:11 UTCEG score recompute
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-21 23:40 UTCEG score recompute
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-20 22:55 UTCEPSS rescore
  9. 2026-08-20 19:07 UTCEG score recompute
  10. 2026-08-19 17:03 UTCEPSS rescore
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-17 14:40 UTCEG score recompute
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 10:02 UTCEG score recompute
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 03:37 UTCEG score recompute
  17. 2026-08-16 02:14 UTCEPSS rescore
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 02:10 UTCEG score recompute
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-12 16:22 UTCEG score recompute
  22. 2026-08-12 13:50 UTCEPSS rescore
  23. 2026-08-11 13:55 UTCEG score recompute
  24. 2026-08-11 00:40 UTCEG score recompute
  25. 2026-08-11 00:00 UTCEPSS rescore
Show 75 more
  1. 2026-08-09 14:27 UTCEG score recompute
  2. 2026-08-09 13:46 UTCEPSS rescore
  3. 2026-08-09 01:38 UTCEG score recompute
  4. 2026-08-08 16:37 UTCEPSS rescore
  5. 2026-08-07 19:15 UTCEG score recompute
  6. 2026-08-06 14:23 UTCEG score recompute
  7. 2026-08-06 13:46 UTCEPSS rescore
  8. 2026-08-05 21:24 UTCEG score recompute
  9. 2026-08-05 19:17 UTCEPSS rescore
  10. 2026-08-04 15:10 UTCEPSS rescore
  11. 2026-08-03 17:00 UTCEG score recompute
  12. 2026-08-03 10:36 UTCEPSS rescore
  13. 2026-08-02 02:36 UTCEG score recompute
  14. 2026-08-02 02:26 UTCEPSS rescore
  15. 2026-08-01 18:04 UTCEG score recompute
  16. 2026-08-01 04:16 UTCEPSS rescore
  17. 2026-07-30 16:27 UTCEPSS rescore
  18. 2026-07-30 01:30 UTCEPSS rescore
  19. 2026-07-28 15:36 UTCEPSS rescore
  20. 2026-07-26 14:54 UTCEPSS rescore
  21. 2026-07-26 14:54 UTCEPSS rescore
  22. 2026-07-25 14:18 UTCEPSS rescore
  23. 2026-07-25 14:17 UTCEPSS rescore
  24. 2026-07-24 14:17 UTCEPSS rescore
  25. 2026-07-23 14:18 UTCEPSS rescore
  26. 2026-07-23 14:18 UTCEPSS rescore
  27. 2026-07-23 03:07 UTCEG score recompute
  28. 2026-07-22 14:08 UTCEPSS rescore
  29. 2026-07-22 14:08 UTCEPSS rescore
  30. 2026-07-21 15:24 UTCEPSS rescore
  31. 2026-07-21 15:24 UTCEPSS rescore
  32. 2026-07-20 17:08 UTCEPSS rescore
  33. 2026-07-20 17:08 UTCEPSS rescore
  34. 2026-07-19 14:31 UTCEPSS rescore
  35. 2026-07-19 14:31 UTCEPSS rescore
  36. 2026-07-19 02:29 UTCEPSS rescore
  37. 2026-07-18 10:04 UTCEPSS rescore
  38. 2026-07-18 10:04 UTCEPSS rescore
  39. 2026-07-17 23:59 UTCOSV refresh
  40. 2026-07-16 17:03 UTCEPSS rescore
  41. 2026-07-16 17:03 UTCEPSS rescore
  42. 2026-07-15 16:57 UTCEPSS rescore
  43. 2026-07-15 16:57 UTCEPSS rescore
  44. 2026-07-15 02:00 UTCEPSS rescore
  45. 2026-07-15 02:00 UTCEPSS rescore
  46. 2026-07-13 22:30 UTCEPSS rescore
  47. 2026-07-13 06:13 UTCEPSS rescore
  48. 2026-07-13 06:13 UTCEPSS rescore
  49. 2026-07-12 05:46 UTCEPSS rescore
  50. 2026-07-11 08:27 UTCEPSS rescore
  51. 2026-07-09 19:10 UTCEPSS rescore
  52. 2026-07-08 15:15 UTCEPSS rescore
  53. 2026-07-07 13:46 UTCEPSS rescore
  54. 2026-07-06 16:27 UTCEPSS rescore
  55. 2026-07-06 16:27 UTCEPSS rescore
  56. 2026-07-06 02:23 UTCEPSS rescore
  57. 2026-07-06 02:23 UTCEPSS rescore
  58. 2026-07-05 02:30 UTCEPSS rescore
  59. 2026-07-04 06:31 UTCEPSS rescore
  60. 2026-07-01 15:06 UTCEPSS rescore
  61. 2026-06-30 23:22 UTCEPSS rescore
  62. 2026-06-29 14:06 UTCEPSS rescore
  63. 2026-06-29 14:06 UTCEPSS rescore
  64. 2026-06-28 14:07 UTCEPSS rescore
  65. 2026-06-28 14:07 UTCEPSS rescore
  66. 2026-06-28 04:56 UTCEPSS rescore
  67. 2026-06-28 04:56 UTCEPSS rescore
  68. 2026-06-27 03:08 UTCEPSS rescore
  69. 2026-06-25 13:49 UTCEPSS rescore
  70. 2026-06-25 13:49 UTCEPSS rescore
  71. 2026-06-24 14:05 UTCEPSS rescore
  72. 2026-06-23 21:33 UTCEPSS rescore
  73. 2026-06-23 21:33 UTCEPSS rescore
  74. 2026-06-22 14:25 UTCEPSS rescore
  75. 2026-06-22 14:25 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-2611?
CVE-2026-2611 is a critical vulnerability published on May 19, 2026. In MLflow version 3.9.0, the MLflow Assistant feature introduced improper origin validation in its /ajax-api endpoints. This vulnerability allows a remote attacker to exploit cross-origin requests from a malicious webpage to interact with the MLflow Assistant running on a victim's local machine. By…
When was CVE-2026-2611 disclosed?
CVE-2026-2611 was first published in the National Vulnerability Database on May 19, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-2611 actively exploited?
CVE-2026-2611 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 68.8% of all scored CVEs.
What is the CVSS score of CVE-2026-2611?
CVE-2026-2611 has a CVSS v3 base score of 9.6 (NVD).
How do I remediate CVE-2026-2611?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-2611, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-2611

Explore →

Is Your Infrastructure Affected by CVE-2026-2611?

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

Start Free Scan →Browse All CVEs