CVE-2026-8147

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-02. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.1
EG Score
8.1(high)
EPSS
25.7%
KEV
Not listed

Published

July 2, 2026

Last Modified

July 6, 2026

Advisory Details (2)

Auto-updated Jul 2, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

huntr - The world's first bug bounty platform for AI/ML

https://huntr.com/bounties/b00c3ddd-373e-492f-9bf0-41a28bb21ed5
github_commit

commit f9b1eb510478 (mlflow/mlflow)

Fix landed in mlflow/mlflow commit f9b1eb510478 — awaiting tagged release

https://github.com/mlflow/mlflow/commit/f9b1eb510478570609ef451984a255775aa4b937

Vendor Advisories for CVE-2026-8147(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 28× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 00:44 UTCEG score recompute
  2. 2026-07-07 00:44 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 12:23 UTCEG score recompute
  6. 2026-07-06 12:23 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 23:59 UTCEG score recompute
  10. 2026-07-05 23:59 UTCGHSA enrichment
  11. 2026-07-05 11:38 UTCEG score recompute
  12. 2026-07-05 11:38 UTCGHSA enrichment
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 23:16 UTCEG score recompute
  16. 2026-07-04 23:15 UTCGHSA enrichment
  17. 2026-07-04 10:54 UTCEG score recompute
  18. 2026-07-04 10:54 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-03 22:33 UTCEG score recompute
  22. 2026-07-03 22:33 UTCGHSA enrichment
  23. 2026-07-03 10:08 UTCEG score recompute
  24. 2026-07-03 10:07 UTCGHSA enrichment
  25. 2026-07-02 21:44 UTCEG score recompute
Show 3 more
  1. 2026-07-02 21:44 UTCGHSA enrichment
  2. 2026-07-02 09:23 UTCEG score recompute
  3. 2026-07-02 09:23 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-8147?
CVE-2026-8147 is a high vulnerability published on July 2, 2026. 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…
When was CVE-2026-8147 disclosed?
CVE-2026-8147 was first published in the National Vulnerability Database on July 2, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-8147 actively exploited?
CVE-2026-8147 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 25.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-8147?
CVE-2026-8147 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-8147?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8147, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-8147

Explore →

Is Your Infrastructure Affected by CVE-2026-8147?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs