Advisory record · GHSA-2cm6-r77w-6g96

MLflow: trace API endpoints lack proper authorization validators

CVSS 8.1 HighEPSS 0.0055 · 46th percentile

Published by the GitHub Advisory Database at 2 Jul 2026, 09:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
mlflowPyPI>=2.14.0rc0, <3.13.0rc03.13.0rc0
Identifiers
GHSA-2cm6-r77w-6g96 · BIT-mlflow-2026-8147 · CVE-2026-8147 · PYSEC-2026-3686
Weakness (CWE)
CWE-284
Published
2 Jul 2026
Updated
19 Aug 2026

Machine-written summary

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

MLflow versions from 2.14.0rc0 before 3.13.0rc0 are affected when authentication is enabled. Any authenticated user can bypass experiment-level authorization and read, delete, or modify traces on experiments they cannot access, which may expose sensitive data and allow audit logs to be destroyed. Upgrade mlflow to 3.13.0rc0 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

ScoreRatingCVSSVectorSource
8.1 High 3.0 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N CNA (@huntr_ai)
  • CISA KEV Not listed.
  • EPSS 0.0055, the 46th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:39 UTC First seen by agentprime
  2. 31 Oct 2026, 14:39 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.