GHSA-75cm-x2w3-8mgf: mlflow (CVE-2026-2652)

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`) ...

CVSS 8.6 HighCriticalEPSS 0.21 · 97th percentile

Critical, because:

CVSS score 8.6 (7.0 or more) and EPSS 0.21 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by the GitHub Advisory Database at 15 May 2026, 03:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

Package	Ecosystem	Affected	Fixed in
mlflow	PyPI	<3.10.0	3.10.0

Identifiers

GHSA-75cm-x2w3-8mgf · BIT-mlflow-2026-2652 · CVE-2026-2652 · PYSEC-2026-2221

Weakness (CWE)

CWE-305

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Mlflow versions before 3.10.0 are affected when the server runs with basic authentication enabled under uvicorn (ASGI). The FastAPI permission middleware only checks authentication on /gateway/ routes, so routes such as the Job API and trace ingestion API accept requests without credentials. A remote unauthenticated attacker could submit, read, and cancel jobs and inject trace data into experiments. Upgrade to mlflow 3.10.0 or later.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

Score	Rating	CVSS	Vector	Source
8.6	High	3.0	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L	CNA (@huntr_ai)

CISA KEV Not listed.
EPSS 0.21, the 97th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

31 Oct 2026, 14:43 UTC First seen by agentprime
31 Oct 2026, 14:43 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.