CVE-2026-8147Patch(lfprojects / mlflow)

LOWCVSS 8.1 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch lfprojects mlflow systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD 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.

0.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-284

Priority

LOW

Exploitation

NONE

PoC

YES

Patch

AVAILABLE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • mlflow

Threat summary

  • Patch or workaround signal is available
  • 1 mentions across 1 observed day

What's happening

  • Patch or workaround mentioned in 1 signal
  • Technical details provided in 1 signal
  • 1 total mentions across 1 day

Affected systems

Vendors
Products
mlflow

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-07-02: 1Patch / Workaround · 2026-07-02: 1Technical Details · 2026-07-02: 107-02
Signal classification1 categories
Patch
1100.0%
Full discourse1 post
  • Upwind Security MDR@UpwindMDR
    Patch

    🚨 HIGH - MLflow Trace API authorization bypass (CVE-2026-8147) MLflow with authentication enabled is vulnerable due to missing authorization checks on trace API endpoints, impacting the tracing component used to store and retrieve experiment traces. The root cause is improper authorization validation (access control failure) that fails to enforce experiment-level permissions on trace operations. An attacker only needs a valid authenticated MLflow account to call the trace endpoints directly and bypass experiment access controls to read, delete, or modify traces belonging to other experiments. Exploitation can lead to sensitive data exposure in traces, tampering with experiment telemetry, and deletion of trace/audit artifacts that undermines incident response and compliance. 👉 Affected: mlflow < 3.14.0 (auth enabled) | Upgrade to 3.14.0

    Post summary

    MLflow’s trace API allows authenticated users to bypass experiment-level access controls, exposing or allowing modification of traces; upgrading to version 3.14.0 resolves the vulnerability.

    0000072
    232 followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Applfprojectsmlflow---

Explore more