CVE-2026-8147: In MLflow versions prior to 3.14.0, when running with authentication enabled, the trace API endpoints lack pro

Q: How do I fix CVE-2026-8147?

mlflow: upgrade to 3.14.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-8147 being exploited?

CVE-2026-8147 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-8147 affect?

CVE-2026-8147 affects mlflow. Severity is high (CVSS 8.1). 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 op

Q: How urgent is CVE-2026-8147?

Priority 45/100. High severity; Public exploit reference

This month

HIGH 8.1UPGRADE

CVE-2026-8147 is a high-severity flaw (CVSS 8.1) affecting mlflow. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 valid

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.5% (top 54%)
CISA exploited list	No
Weakness	CWE-284
Published	2026-07-02
Last modified	2026-10-25

Publisher (CNA): huntr.dev · Vendor: lfprojects

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-07-02 09:16 UTCPublished CVE record published
2026-10-25 21:10 UTCUpdated Record last modified

lfprojects mlflow UPGRADE

Affected: < 3.14.0

Fixed in: 3.14.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy mlflow || rpm -q mlflow || mlflow --version

2. UPGRADE to 3.14.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade mlflow

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade mlflow

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-8147?

mlflow: upgrade to 3.14.0. Exact commands for each OS are on this page.

Is CVE-2026-8147 being exploited?

CVE-2026-8147 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-8147 affect?

CVE-2026-8147 affects mlflow. Severity is high (CVSS 8.1). 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 op

How urgent is CVE-2026-8147?

Priority 45/100. High severity; Public exploit reference

References

← Back to latest CVEs