Skip to main content
VulnerabilityPublished

CVE-2026-8147: mlflow/mlflow · Improper Access Control

Affects mlflow/mlflowSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High : upgrade to 3.14.0 soon.

Data as of 14 Nov 2026, 20:44 UTC

CVSS 3.0 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.14.0
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.

What to do

Upgrade mlflow to 3.14.0.

Affected software

ProductAffectedFixed in
mlflowmlflow/mlflowAffected
  • ≥ unspecified, < 3.14.0
Fixed in–
PyPImlflowpkg:pypi/mlflowOther threatsAffected
  • <3.14.0
Fixed in
  • 3.14.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, restrict authenticated user permissions to trusted users only and monitor for suspicious trace API activity. Avoid enabling authentication without additional compensating controls on trace endpoints.

Description

In MLflow versions prior to 3.14.0, when running with authentication enabled, the trace API endpoints lack proper authorization validators. This allows any authenticated user to bypass experiment-level authorization controls on all trace operations, including reading, deleting, and modifying traces on experiments they do not have permission to access. The issue arises from the `_before_request` handler, which does not register authorization validators for trace endpoints, resulting in requests proceeding without validation. This vulnerability can expose sensitive data, destroy audit logs, and allow unauthorized modifications.

References

Community reviews

Loading reviews…