Live › vulnerability › CVE-2026-118624
ZDI-26-840: the MLflow tracking server's job routes (GET /mlflow/jobs/<id>, PATCH /mlflow/jobs/cancel/<id>) had no authorization validator and jobs recorded no owner (_find_validator). Under the built-in basic-auth, any authenticated user could read another user's job parameters and results, and cancel it. ZDI states it is fixed in MLflow 3.16.0; the linked PR adds a per-job creator check.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-04 00:46 UTC. All times on this page are UTC.
Self-hosted MLflow tracking servers before 3.16.0 that run with multiple authenticated users and use the server's jobs feature. An attacker needs a valid login, then can read other users' job parameters and results, and cancel their jobs. Single-user setups, servers without the jobs feature, and managed MLflow hosting where the vendor patches it can likely skip it.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| mlflow | pypi | < 3.16.0 | 3.16.0 |
mlflow --version (or pip show mlflow); versions before 3.16.0 are affected per ZDI3.13.0, unconfirmed)3.16.0 (per ZDI-26-840)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
MLflow Tracking Server Jobs Missing Authorization Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of MLflow. Authentication is required to exploit this vulnerability.
The specific flaw exists within the _find_validator function. The issue results from the lack of authorization prior to allowing access to functionality. An attacker can leverage this vulnerability to disclose information in the context of the service account. Was ZDI-CAN-31894.
This page as .md · .json · in your agent: get_signal("CVE-2026-118624")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.