cve.bz

CVE-2026-8147 lfprojects mlflow: Improper Access Control

8.1 highExploit referenceEPSS 0.5%Fix available

High (8.1) in lfprojects mlflow. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in mlflow 3.13.0rc0.

On this page
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.

Severity

CVSS 3.0

8.1 high
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 46th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-07-02. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-284 Improper Access Control
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-8147 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-8147?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-8147?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-8147 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
mlflow/mlflowbefore 3.14.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-2cm6-r77w-6g96PyPImlflow>=2.14.0rc0 <3.13.0rc03.13.0rc0
PYSEC-2026-3686PyPImlflow>=2.14.0rc0 <3.13.0rc03.13.0rc0

Red Hat

Red Hat rates this Important.

Red Hat's statement

This Important flaw in MLflow, as deployed in Red Hat OpenShift AI, allows an authenticated user to bypass experiment-level authorization controls on trace API endpoints. This enables unauthorized access, modification, and deletion of sensitive trace data, impacting the confidentiality and integrity of machine learning experiment results within the platform. The vulnerability specifically affects the `rhoai/odh-mlflow-rhel9` component.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat OpenShift AI (RHOAI)rhoai/odh-mlflow-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-datascience-cpu-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-pytorch-cuda-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-pytorch-llmcompressor-cuda-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-pytorch-rocm-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-tensorflow-cuda-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-tensorflow-rocm-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-th06-cpu-torch210-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-th06-cuda130-torch210-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-th06-rocm64-torch291-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-training-cuda128-torch29-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-datascience-cpu-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-pytorch-cuda-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-pytorch-llmcompressor-cuda-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-pytorch-rocm-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-tensorflow-cuda-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-tensorflow-rocm-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-8147.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-284 (17).

References

Check your stackJSON