A HIGH-severity vulnerability identified as CVE-2026-8147 has been published on July 2, 2026 with a CVSS base score of 8.1. This security advisory provides a detailed breakdown of the vulnerability, its potential impact, weakness classification, and actionable steps to protect your systems.
Table of Contents
ToggleVulnerability Details
CVE ID: CVE-2026-8147
Severity: HIGH
CVSS Score: 8.1
Published: July 2, 2026
Weakness (CWE): CWE-284
| Attack Vector | Network |
| Attack Complexity | Low |
| Privileges Required | Low |
| User Interaction | None |
| Confidentiality Impact | High |
| Integrity Impact | High |
| Availability Impact | None |
Technical 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.
Potential Impact
If exploited, this high-severity vulnerability could allow an attacker to compromise sensitive data confidentiality, tamper with system integrity. Organizations running affected software should treat this as a priority remediation item.
Recommended Action
No official patch is available yet. Until one is released:
- Monitor the official NVD page and vendor channels for patch announcements.
- Restrict access to the affected system or service where possible.
- Apply network-level mitigations such as firewall rules or WAF policies.
- Enable logging and alerting for anomalous activity related to this vulnerability.
- Review your incident response plan in case of active exploitation.
References
Related Security Advisories
- [HIGH] CVE-2026-13547 — CVSS 7.3 (June 29, 2026) — HIGH / CVSS 7.3
- [CRITICAL] CVE-2026-48907 — CVSS 10.0 (June 5, 2026) — CRITICAL / CVSS 10.0
- [HIGH] CVE-2026-9563 — CVSS 7.5 (July 2, 2026) — HIGH / CVSS 7.5

![[HIGH] CVE-2026-13126 — CVSS 7.8 (July 8, 2026)](https://atlas-cybersecurity.com/wp-content/plugins/elementor/assets/images/placeholder.png)



