CVE-2026-8147

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM 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
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.1HIGHmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation1% × 40%
Automatability30% × 15%
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

Published

July 2, 2026

Last Modified

July 6, 2026

Advisory Details (2)

Auto-updated Jul 2, 2026
Patch available. 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.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
mlflow2.14.0 ... 3.9.0rc0 (79 versions)
  • 2.14.0rc0 up to 3.13.0rc0: fixed in 3.13.0rc0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 30× 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.

Showing the most recent 100 of 208 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:13 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:44 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-01 19:51 UTCEPSS rescore
  8. 2026-09-30 15:04 UTCEPSS rescore
  9. 2026-09-28 13:52 UTCEPSS rescore
  10. 2026-09-28 13:52 UTCEPSS rescore
  11. 2026-09-27 13:49 UTCEPSS rescore
  12. 2026-09-26 15:59 UTCEPSS rescore
  13. 2026-09-24 14:04 UTCEPSS rescore
  14. 2026-09-23 17:54 UTCEPSS rescore
  15. 2026-09-23 06:43 UTCEG score recompute
  16. 2026-09-22 16:01 UTCEPSS rescore
  17. 2026-09-21 21:09 UTCEPSS rescore
  18. 2026-09-20 20:16 UTCEPSS rescore
  19. 2026-09-18 19:28 UTCEPSS rescore
  20. 2026-09-18 06:22 UTCEG score recompute
  21. 2026-09-17 19:32 UTCEPSS rescore
  22. 2026-09-16 14:09 UTCEPSS rescore
  23. 2026-09-16 05:15 UTCEPSS rescore
  24. 2026-09-15 03:12 UTCEPSS rescore
  25. 2026-09-14 00:18 UTCEG score recompute
Show 75 more
  1. 2026-09-13 16:48 UTCEPSS rescore
  2. 2026-09-13 09:03 UTCEG score recompute
  3. 2026-09-12 15:02 UTCEPSS rescore
  4. 2026-09-12 14:32 UTCEG score recompute
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-08 22:01 UTCEPSS rescore
  7. 2026-09-06 14:23 UTCEG score recompute
  8. 2026-09-06 13:48 UTCEPSS rescore
  9. 2026-09-06 00:33 UTCEG score recompute
  10. 2026-09-05 15:31 UTCEPSS rescore
  11. 2026-09-04 05:07 UTCEPSS rescore
  12. 2026-09-02 14:12 UTCEPSS rescore
  13. 2026-09-01 13:54 UTCEPSS rescore
  14. 2026-09-01 04:40 UTCEPSS rescore
  15. 2026-08-30 23:47 UTCEG score recompute
  16. 2026-08-30 19:18 UTCEPSS rescore
  17. 2026-08-30 19:17 UTCEPSS rescore
  18. 2026-08-30 11:26 UTCEG score recompute
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:42 UTCEPSS rescore
  21. 2026-08-27 22:20 UTCEG score recompute
  22. 2026-08-27 14:25 UTCEPSS rescore
  23. 2026-08-26 14:47 UTCEPSS rescore
  24. 2026-08-25 16:04 UTCEG score recompute
  25. 2026-08-25 13:49 UTCEPSS rescore
  26. 2026-08-24 22:54 UTCEG score recompute
  27. 2026-08-24 14:18 UTCEPSS rescore
  28. 2026-08-24 10:26 UTCEG score recompute
  29. 2026-08-23 08:19 UTCEG score recompute
  30. 2026-08-23 00:19 UTCEPSS rescore
  31. 2026-08-22 06:45 UTCEG score recompute
  32. 2026-08-21 23:49 UTCEPSS rescore
  33. 2026-08-21 05:16 UTCEG score recompute
  34. 2026-08-20 22:56 UTCEPSS rescore
  35. 2026-08-20 04:24 UTCEG score recompute
  36. 2026-08-19 17:04 UTCEPSS rescore
  37. 2026-08-18 20:56 UTCEG score recompute
  38. 2026-08-18 13:49 UTCEPSS rescore
  39. 2026-08-18 13:49 UTCEPSS rescore
  40. 2026-08-18 04:44 UTCEG score recompute
  41. 2026-08-17 13:47 UTCEPSS rescore
  42. 2026-08-17 00:04 UTCEG score recompute
  43. 2026-08-16 14:56 UTCEPSS rescore
  44. 2026-08-16 14:56 UTCEPSS rescore
  45. 2026-08-16 11:42 UTCEG score recompute
  46. 2026-08-16 02:15 UTCEPSS rescore
  47. 2026-08-15 11:01 UTCEG score recompute
  48. 2026-08-15 01:31 UTCEPSS rescore
  49. 2026-08-14 10:18 UTCEG score recompute
  50. 2026-08-13 22:00 UTCEPSS rescore
  51. 2026-08-13 09:36 UTCGHSA enrichment
  52. 2026-08-12 21:15 UTCEG score recompute
  53. 2026-08-12 21:15 UTCGHSA enrichment
  54. 2026-08-12 13:51 UTCEPSS rescore
  55. 2026-08-12 08:54 UTCGHSA enrichment
  56. 2026-08-11 20:32 UTCEG score recompute
  57. 2026-08-11 20:32 UTCGHSA enrichment
  58. 2026-08-11 13:43 UTCEPSS rescore
  59. 2026-08-11 08:12 UTCEG score recompute
  60. 2026-08-11 08:12 UTCGHSA enrichment
  61. 2026-08-11 00:00 UTCEPSS rescore
  62. 2026-08-10 19:50 UTCGHSA enrichment
  63. 2026-08-10 07:28 UTCGHSA enrichment
  64. 2026-08-09 19:08 UTCEG score recompute
  65. 2026-08-09 19:08 UTCGHSA enrichment
  66. 2026-08-09 13:47 UTCEPSS rescore
  67. 2026-08-09 06:47 UTCGHSA enrichment
  68. 2026-08-08 18:26 UTCEG score recompute
  69. 2026-08-08 18:26 UTCGHSA enrichment
  70. 2026-08-08 16:37 UTCEPSS rescore
  71. 2026-08-08 06:04 UTCGHSA enrichment
  72. 2026-08-07 17:43 UTCEG score recompute
  73. 2026-08-07 17:43 UTCGHSA enrichment
  74. 2026-08-07 05:22 UTCGHSA enrichment
  75. 2026-08-06 16:59 UTCEG score recompute

Related CVEs(same product + 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 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 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-8147?
CVE-2026-8147 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-8147?
A fix for CVE-2026-8147 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-8147 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs