Authenticated trace disclosure and tampering via missing validators
Published Jul 2, 2026 · Updated Jul 2, 2026
Improper access control in MLflow before 3.14.0 allows remote authenticated users to read, modify, or delete unauthorized traces. The _before_request handler omits trace routes from its validator map, so requests bypass experiment-level read, update, and delete permission checks. Authentication must be enabled and any valid account is sufficient; the bypass exposes trace contents and permits tampering with or deleting trace and audit data.
Summary
What happened
Improper access control in MLflow before 3.14.0 allows remote authenticated users to read, modify, or delete unauthorized traces. The _before_request handler omits trace routes from its validator map, so requests bypass experiment-level read, update, and delete permission checks. Authentication must be enabled and any valid account is sufficient; the bypass exposes trace contents and permits tampering with or deleting trace and audit data.
The record
- CVE
- CVE-2026-8147
- Published
- Jul 2, 2026
- Updated
- Jul 2, 2026
- Vendor
- MLflow Project
- Product
- MLflow
- Classifications
- CWE-284, T1565, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 2, 2026CVE publishedPublication date reported by the CVE source.
- Jul 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <3.14.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- huntr trace authorization-bypass proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo