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.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.6Exploit: NoneExposed: 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)
EPSS
29.2%
KEV
Not listed

Published

May 19, 2026

Last Modified

June 27, 2026

Advisory Details (2)

Auto-updated May 19, 2026
No patch confirmed yet.
generic

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

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

Block CORS for ajax paths (#20832) · mlflow/mlflow@8f9c8a5 · GitHub

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

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 9× in last 7d / 82× 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 209 total refreshes for this CVE.

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

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 June 27, 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 29.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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