CVE-2026-2652
HighSummary
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. Issues with the authentication mechanisms lead to a bypass of protections on routes such as the Job API and the OpenTelemetry trace ingestion API.
Risk Assessment
Unauthenticated remote attackers can submit jobs, read job results, cancel running jobs, and inject arbitrary trace data into experiments, posing a serious threat to the integrity of data and operations within the organization.
Recommendation
It is recommended to upgrade to version 3.10.0 or later to mitigate this vulnerability and to implement additional security measures, such as restricting access to unauthenticated routes.
Other vulnerabilities in mlflow/mlflow
See allOriginal NVD description (English source)
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.