CVE-2026-2652

published 15 May 2026 · updated 11 Nov 2026

Authentication Bypass in mlflow/mlflow

10.0CriticalCVSS 8.6EPSS 21%2 public exploits

2 public exploits exists; no exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 21%. Fixed in MLflow 3.10.0 and 3.10.0.

A vulnerability in mlflow/mlflow versions 3.9.0 and earlier allows unauthenticated access to certain FastAPI routes when the server is started with authentication enabled (`--app-name basic-auth`) and served via uvicorn (ASGI). The FastAPI permission middleware only enforces authentication on `/gateway/` routes, leaving other routes such as the Job API (`/ajax-api/3.0/jobs/*`) and the OpenTelemetry trace ingestion API (`/v1/traces`) unprotected. This allows unauthenticated remote attackers to submit jobs, read job results, cancel running jobs, and inject arbitrary trace data into experiments. The issue arises from an architectural mismatch between Flask and FastAPI authentication mechanisms, where the `_find_fastapi_validator()` function fails to handle non-`/gateway/` paths, resulting in a complete authentication bypass. This vulnerability is fixed in version 3.10.0.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
MLflowMLflow<3.10.03.10.0
lfprojectsmlflow<3.10.03.10.0

Exploit evidence

2 public sources

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in MLflow, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-2652 severity on Zeptric[![CVE-2026-2652](https://zeptric.io/badge/cve/CVE-2026-2652.svg)](https://zeptric.io/cve/CVE-2026-2652)