Artifact disclosure via omitted route validators
Published Apr 7, 2026 · Updated Apr 7, 2026
Missing authorization in MLflow 3.10.1 and earlier allows remote authenticated users to read restricted logged-model artifacts. The request hook treats a missing match in LOGGED_MODEL_BEFORE_REQUEST_VALIDATORS as allowed, leaving the artifact file and directory routes unchecked. Basic-auth mode must be enabled, and any account lacking read permission on the parent experiment can retrieve model files and metadata.
Summary
What happened
Missing authorization in MLflow 3.10.1 and earlier allows remote authenticated users to read restricted logged-model artifacts. The request hook treats a missing match in LOGGED_MODEL_BEFORE_REQUEST_VALIDATORS as allowed, leaving the artifact file and directory routes unchecked. Basic-auth mode must be enabled, and any account lacking read permission on the parent experiment can retrieve model files and metadata.
The record
- CVE
- CVE-2026-33866
- Published
- Apr 7, 2026
- Updated
- Apr 7, 2026
- Vendor
- MLflow Project
- Product
- MLflow
- Classifications
- CWE-862, CAPEC-115, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 7, 2026CVE publishedPublication date reported by the CVE source.
- Apr 7, 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=0 <=3.10.1
What conditions does exploitation require?
What is affected?
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
- AFINE logged-model artifact authorization-bypass proof of conceptfunctional · demonstrated
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