CVE-2026-8147
MLflow <3.14.0: Auth bypass on trace API endpoints.
Is CVE-2026-8147 being exploited?
Not confirmed. CVE-2026-8147 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.55% probability of exploitation in the next 30 days.
How severe is CVE-2026-8147?
CVE-2026-8147 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-8147?
Yes. A fix has been recorded for CVE-2026-8147. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-8147 affect?
CVE-2026-8147 affects MLflow <3.14.0, Trace API endpoints. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-8147?
Upgrade to MLflow 3.14.0+; enforce trace endpoint auth validators.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated users can bypass trace-level authorization for all trace ops, exposing data, destroying logs, and modifying traces.
Patch when possible
- affected< 3.14.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.