LiveActive security incident?Get immediate response
CVE Record

CVE-2026-2611: Improper Origin Validation in mlflow/mlflow

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.

CriticalCVSS 9.6Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

MLflow 3.9.0 introduced an Assistant feature that did not properly validate request origins. If a user running the Assistant visits a malicious webpage, that page could interact with the local Assistant and change settings that allow command execution. The issue is fixed in MLflow 3.10.0.

Executive priority

Prioritize remediation quickly for teams using MLflow Assistant. The business risk is workstation compromise from normal web browsing, potentially exposing model assets, credentials, code, and local systems. Urgency is high even without confirmed active exploitation.

Technical view

The vulnerability affects MLflow Assistant /ajax-api endpoints through improper origin validation. A cross-origin webpage can bypass the intended loopback-only restriction against a victim’s local Assistant, modify Assistant configuration to enable full access, and reach arbitrary command execution through the Claude Code sub-agent. CVSS is 9.6 with user interaction required.

Likely exposure

Most relevant exposure is developer or workstation environments running MLflow 3.9.0 with MLflow Assistant active locally. Public internet exposure is not established by the sources. The attack path depends on a victim visiting attacker-controlled content while the local Assistant is reachable.

Exploitation context

The sources describe a remote, user-interaction attack through a malicious webpage. The bundle does not show CISA KEV listing or confirmed active exploitation. Treat exploitability as serious because the described impact reaches arbitrary command execution after configuration manipulation.

Researcher notes

Focus validation on MLflow 3.9.0 Assistant behavior and origin enforcement around /ajax-api. The public bundle attributes remediation to commit 8f9c8a53 and MLflow 3.10.0. Do not assume broader MLflow versions or Red Hat product impact beyond listed source evidence.

Mitigation direction

  • Upgrade MLflow to version 3.10.0 or later.
  • Identify systems running MLflow 3.9.0 with Assistant enabled.
  • Consult MLflow or distribution guidance for supported temporary controls.
  • Prioritize developer workstations that browse the web while running MLflow Assistant.

Validation and detection

  • Inventory installed MLflow versions across workstations and ML environments.
  • Confirm whether MLflow Assistant and /ajax-api endpoints are present.
  • Verify remediated systems report MLflow 3.10.0 or later.
  • Review available local logs for unexpected Assistant configuration changes.
Prepared
Confidence
high
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-346: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-940: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-2611 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.6 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.6CVSS 3.0CriticalCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H2.86@huntr_ai
9.6CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H2.86redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

9.6Critical
CVSS 3.1 vector shape for CVE-2026-2611Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPmlflow: MLflow: Arbitrary Code Execution via Improper Origin Validation
other:Red Hat severity ratingcvssV3_1
  • 2026-05-19T11:01:40.655Z: Reported to Red Hat.
  • 2026-05-19T09:16:42.745Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
mlflowmlflow/mlflowunspecifiedListed
Weakness

CWE details

CWE-346CWE-940

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-346 · source CWE mapping

Origin Validation Error

Origin Validation Error represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs
CWE-940 · source CWE mapping

Improper Verification of Source of a Communication Channel

Improper Verification of Source of a Communication Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs