Skip to content
Fencer Vulns
high 8.1

CVE-2026-8147 json

Authorization Bypass in mlflow/mlflow

published 2026-07-02 4 mo ago modified 2026-10-25 14 d ago also BIT-mlflow-2026-8147 , EUVD-2026-41257 , GHSA-2cm6-r77w-6g96 , PYSEC-2026-3686

cvss
8.1
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 46%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi mlflow 3.13.0rc0
  • bitnami mlflow 3.14.0
  • mlflow mlflow/mlflow 3.14.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-8147 updated cvss 8.1

mlflow: MLflow: Unauthorized access to trace data due to missing authorization validation

  • Red Hat OpenShift AI (RHOAI) rhoai/odh-mlflow-rhel9, rhoai/odh-th06-cpu-torch210-py312-rhel9, rhoai/odh-th06-rocm64-torch291-py312-rhel9, rhoai/odh-th06-cuda130-torch210-py312-rhel9, rhoai/odh-training-cuda128-torch29-py312-rhel9, rhoai/odh-pipeline-runtime-pytorch-cuda-py312-rhel9, +13 more
    not affected: vulnerable code not in execute path

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
4 mo ago

Exploit prediction

0.55% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • huntr.com https://huntr.com/bounties/b00c3ddd-373e-492f-9bf0-41a28bb21ed5 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 8.1 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
GitHub 3.0 8.1 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OSV 3.0 8.1 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
pypi mlflow
>=2.14.0rc0, <3.13.0rc0
3.13.0rc0
bitnami mlflow
<3.14.0
3.14.0

Affected products

  • mlflow mlflow/mlflow

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.