---
title: "CVE-2026-2611: MLflow: Improper Origin Validation in MLflow Assistant /ajax-api Endpoints Enables Browser-Mediated Local Command Execution"
url: https://erroneo.us/security/cve/CVE-2026-2611/
description: "CVE-2026-2611 (mlflow (PyPI)): In MLflow version 3.9.0, the MLflow Assistant feature introduced improper origin validation in its /ajax-api endpoints. This…"
type: vulnerability-record
section: "Security Digest"
date_published: 2026-05-19
date_modified: 2026-10-05
publisher: erroneo.us
author: erroneo.us Security Desk
cve: "CVE-2026-2611"
kev: false
cvss: 9.6
epss: 0.00414
license: All rights reserved. Quote with attribution and a link.
---

# CVE-2026-2611: MLflow: Improper Origin Validation in MLflow Assistant /ajax-api Endpoints Enables Browser-Mediated Local Command Execution

**Signal:** Critical and remotely reachable. No known exploitation yet, but it is network-reachable without credentials. (Computed from CISA KEV, EPSS and CVSS; not an editorial verdict.)

## Should you act?

- Not in CISA KEV , but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 0.4% , percentile 35: FIRST’s model estimates a 0.4% chance of exploitation activity in the next 30 days, higher than 35% of all scored CVEs (low). EPSS is a probability, not a verdict.
- Needs a user to click or open something. Phishing makes that realistic, but it is not wormable.
- Only applies if your dependency tree includes mlflow (PyPI) = 3.9.0, fixed in 3.10.0 . Check your lockfile, including transitive dependencies.

## What it is

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.

## Affected packages

- PyPI `mlflow` = 3.9.0 → fixed: 3.10.0

## Affected products (CVE record)

- mlflow mlflow/mlflow: unspecified < 3.10.0

## Severity

- @huntr_ai CVSS 3.0: 9.6 `CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`
- redhat-SADP CVSS 3.1: 9.6 `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`
- GitHub CVSS 3.1: 9.6 `CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`

## Exploitation

- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation poc , automatable no , technical impact total .
- FIRST EPSS (model of 2026-10-21): 0.41% probability of exploitation activity in the next 30 days; percentile 35.

## Sources

- [GitHub Advisory GHSA-67c5-x5mf-rppq](https://github.com/advisories/GHSA-67c5-x5mf-rppq)
- [CVE.org record CVE-2026-2611](https://www.cve.org/CVERecord?id=CVE-2026-2611)
- [NVD entry CVE-2026-2611](https://nvd.nist.gov/vuln/detail/CVE-2026-2611)
- [huntr.com](https://huntr.com/bounties/8462addd-b464-4a84-b6a2-5529604e6e5a)
- [github.com](https://github.com/mlflow/mlflow/commit/8f9c8a53af90842944101eb8b7d60706822c81bc)
- [access.redhat.com](https://access.redhat.com/security/cve/CVE-2026-2611)
- [RHBZ#2479797](https://bugzilla.redhat.com/show_bug.cgi?id=2479797)
- [security.access.redhat.com](https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-2611.json)
- [github.com](https://github.com/mlflow/mlflow)
- [github.com](https://github.com/pypa/advisory-database/tree/main/vulns/mlflow/PYSEC-2026-418.yaml)
- [pypi.org](https://pypi.org/project/mlflow)

---
Source page: https://erroneo.us/security/cve/CVE-2026-2611/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt