INCIDENT MAP

Browse / AI Framework and Platform Flaws / CVE-2026-2652

MLflow: unauthenticated access to certain FastAPI routes

CVE-2026-2652 ยท 2026-05-15 high

Class
AI Framework and Platform Flaws (filed by a model that read the advisory)
Technique
Authentication and access control
Affected
mlflow (PyPI)
Gets past
Authentication check
CVSS
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L
EPSS
20.8% chance of exploitation in 30 days

How it works, in short

Authentication is enforced only on gateway paths, so unauthenticated requests reach job and trace ingestion FastAPI routes under uvicorn. (Our summary, written by a model. The source text is below.)

Details

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.

References

Source: GitHub Advisory Database, used under CC BY 4.0.