SA-26-261 High

MLflow: A vulnerability has been found in MLflow up to 4666cffc7912ea606d592fc38d6a75e2935f65e7

MLflow

Severity
High, CVSS 8.8
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Record
CVE-2026-13484
Affects
MLflow
Known exploited
Not listed in the CISA Known Exploited Vulnerabilities catalog
Published
Record first published by the source
June 28, 2026
Source last modified
July 1, 2026

Description

A vulnerability has been found in MLflow up to 4666cffc7912ea606d592fc38d6a75e2935f65e7. The impacted element is an unknown function of the component Experiment-scoped Label Schema CRUD API. Such manipulation leads to missing authorization. It is possible to launch the attack remotely. A high complexity level is associated with this attack. The exploitability is regarded as difficult. The exploit has been disclosed to the public and may be used. A reply to the GitHub issue explains, that "[t]he labeling schema PR has not been merged yet. The auth handlers will be added before the release."

Description quoted from the NVD record.

Who is affected

MLflow, made by LF Projects, is a platform that teams use to track and manage their machine learning work, from experiments to finished models. This flaw affects MLflow code up to the code change labeled 4666cffc7912ea606d592fc38d6a75e2935f65e7, in the part that lets users create, view, change and delete labeling schemes for experiments. That part does not properly check whether a person is allowed to use it, and an attacker could misuse it over a network, although the attack is considered difficult. The feature had not yet been added to a released version, and access checks were planned before release. This flaw is rated High.

What to do

  1. Find out who installed or runs MLflow for your organization. This is the person who should act on this flaw.
  2. No fixed version is named for this flaw yet, so ask that person to check the vendor advisory linked on this page for a fixed release and install it once it is available.
  3. If an IT provider or vendor runs MLflow for your organization, send them this advisory and ask when the update will be done.
  4. If your organization does not use MLflow, you do not need to do anything about this flaw.

Analysis written from the source record as of July 1, 2026 and reviewed before publishing.

Sources

MORE ADVISORIES

See all