CVE-2026-2611
Lfprojects Mlflow vulnerability
- Published19 May 2026
Description
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 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:HAffected products
Remediation
References
- https://access.redhat.com/security/cve/CVE-2026-2611
- https://bugzilla.redhat.com/show_bug.cgi?id=2479797
- https://github.com/mlflow/mlflow/commit/8f9c8a53af90842944101eb8b7d60706822c81bc
- https://huntr.com/bounties/8462addd-b464-4a84-b6a2-5529604e6e5a
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-2611.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-2611 being actively exploited?
CVE-2026-2611 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.41%.
How severe is CVE-2026-2611?
CVE-2026-2611 has a CVSS 3.1 base score of 9.6, rated critical. EPSS estimates a 0.41% probability of exploitation.
Which products are affected by CVE-2026-2611?
Affected products include Lfprojects Mlflow.
How do I fix CVE-2026-2611?
Upgrade affected software to a fixed version, for example Lfprojects Mlflow 3.10.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-2611 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.