Security Resilience

CVE-2026-2611

Lfprojects Mlflow 3.9.0 – 3.10.0

Public PoC
Published
19 May 2026
Modified
14 October 2026
Patch / advisory
View advisory
CVSS Score v3.1 9.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
EPSS Score 0.0041 34th percentile
Risk Priority 67 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-2611 is a critical-severity Origin Validation Error (CWE-346) vulnerability in Lfprojects Mlflow. Its CVSS base score is 9.6 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Adversary-in-the-Middle (T1557); ranked at the 34th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

This vulnerability is AI-related — categorised as Enterprise AI Assistants; in the Supply Chain and Deployment risk domain.

The strongest mitigations our analysis identified map to AC-17 (Remote Access) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A07:2025 Authentication Failures

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-346CWE-940

AI Security AnalysisAI

AI Category
Enterprise AI Assistants
Risk Domain
Supply Chain and Deployment
OWASP Top 10 for LLMs 2025
None mapped
Classification Reason
Matched keywords: claude, mlflow

Related Threats

MITRE ATT&CK Enterprise Techniques

T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
attack.mitre.org →
T1557.001 Name Resolution Poisoning and SMB Relay Credential Access
By responding to LLMNR/NBT-NS/mDNS network traffic, adversaries may spoof an authoritative source for name resolution to force communication with an adversary controlled system.
attack.mitre.org →
T1557.002 ARP Cache Poisoning Credential Access
Adversaries may poison Address Resolution Protocol (ARP) caches to position themselves between the communication of two or more networked devices.
attack.mitre.org →
T1557.003 DHCP Spoofing Credential Access
Adversaries may redirect network traffic to adversary-owned systems by spoofing Dynamic Host Configuration Protocol (DHCP) traffic and acting as a malicious DHCP server on the victim network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-14279Same product: Lfprojects Mlflow
CVE-2026-4035Same product: Lfprojects Mlflow
CVE-2026-2393Same product: Lfprojects Mlflow
CVE-2023-6974Same product: Lfprojects Mlflow
CVE-2023-1177Same product: Lfprojects Mlflow
CVE-2025-0453Same product: Lfprojects Mlflow
CVE-2026-64849Same product: Lfprojects Mlflow
CVE-2024-1560Same product: Lfprojects Mlflow
CVE-2024-1594Same product: Lfprojects Mlflow
CVE-2023-6568Same product: Lfprojects Mlflow

Affected Assets

lfprojects
mlflow
3.9.0 — 3.10.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.5.3
  • V10.6.2
  • V15.2.4

Mitigating Controls (NIST 800-53 r5) AI

IA-3 Device Identification and Authentication good match

IA-3 requires unique identification and authentication of devices before any communication channel is established, directly stopping acceptance of unverified origins.

AC-17 Remote Access good match

AC-17 mandates documented restrictions and authentication requirements for remote access, blocking channels whose origins are not properly verified.

AC-4 Information Flow Enforcement good match

Information flow enforcement directly requires validating the source of data before allowing transmission or receipt.

SC-23 Session Authenticity good match

Session authenticity mechanisms require validation that communications originate from the expected party.

SC-7 Boundary Protection partial match

Boundary protection at interfaces enforces checks on the origin of incoming communications.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-03 partial match
blocks

Authentication of users/services/hardware directly enforces source verification for communication channels.

PR.AA-04 partial match
blocks

Verifying identity assertions prevents spoofed channel origins but does not cover all channel-establishment scenarios.

PR.IR-01 partial match
blocks

Network protections reduce unauthorized channel usage but do not specifically require origin verification at channel setup.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.20 Networks security partial match
degrades

Network security controls enforce origin validation at network boundaries.

A.8.21 Security of network services partial match
degrades

Security of network services includes validating the authenticity of service endpoints.

A.8.24 Use of cryptography partial match
blocks

A.8.24 mandates proper use of cryptography (algorithms, key management, protection of data in transit/storage) but has no bearing on whether a product correctly verifies the origin of an incoming communication channel; the weakness can still be present and exploited regardless of cryptographic controls.

A.8.26 Application security requirements partial match
blocks

A.8.26 requires identifying and specifying requirements for resilience against malicious attacks including SQL injections and input validation (items d, j), plus related protections (authentication, segregation, cryptography per 8.24), which can address some but not most origin validation scenarios such as those involving untrusted cross-origin requests or implicit trust in sources.

A.8.27 Secure system architecture and engineering principles partial match
blocks

A.8.27 mandates security-by-design principles (defense-in-depth, least privilege, assume-breach, distrust-external-input, zero-trust verification) plus design reviews that can catch and block origin-validation gaps in many common cases, but leaves a bounded remainder (e.g. protocol-level or third-party component origin errors not surfaced by the organization's review process).

A.8.28 Secure coding partial match
prevents

Secure coding practices include implementing proper origin validation to prevent spoofing.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-346, a class-level weakness, and none of its children carries one either.

References