Mlflow mlflow/mlflow
Authentication Bypass in mlflow/mlflow
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- >= unspecified, < 3.10.0
Fixed in 3.10.0
Mitigation
Upgrade mlflow/mlflow to 3.10.0 or later.
References
Timeline
Days relative to CVE publicationFirst public PoC 20 days after publication; not in CISA KEV. First PoC: nuclei template: MLflow < 3.10.0 - Authentication Bypass on FastAPI Routes (nuclei template, 4 Jun 2026).
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| nuclei template | nuclei template: MLflow < 3.10.0 - Authentication Bypass on FastAPI Routes | 4 Jun 2026 | 14 Nov 2026 |