CVE-2026-33866 | MLflow up to 3.10.1 AJAX Endpoint authorization (EUVD-2026-19609)
VulDBArchived Apr 07, 2026✓ Full text saved
A vulnerability, which was classified as problematic , has been found in MLflow up to 3.10.1 . Affected by this issue is some unknown functionality of the component AJAX Endpoint . This manipulation causes missing authorization. This vulnerability is handled as CVE-2026-33866 . The attack can be initiated remotely. There is not any exploit available.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-355742 · CVE-2026-33866 · EUVD-2026-19609
MLFLOW UP TO 3.10.1 AJAX ENDPOINT AUTHORIZATION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
4.3 $0-$5k 2.32+
Summaryinfo
A vulnerability, which was classified as problematic, was found in MLflow up to 3.10.1. This affects an unknown part of the component AJAX Endpoint. Such manipulation leads to authorization. This vulnerability is uniquely identified as CVE-2026-33866. The attack can be launched remotely. No exploit exists.
Detailsinfo
A vulnerability was found in MLflow up to 3.10.1. It has been rated as problematic. Affected by this issue is some unknown functionality of the component AJAX Endpoint. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. Impacted is confidentiality. CVE summarizes:
MLflow is vulnerable to an authorization bypass affecting the AJAX endpoint used to download saved model artifacts. Due to missing access‑control validation, a user without permissions to a given experiment can directly query this endpoint and retrieve model artifacts they are not authorized to access. This issue affects MLflow version through 3.10.1
The weakness was disclosed by Sławomir Zakrzewski. The advisory is available at github.com. This vulnerability is handled as CVE-2026-33866 since 03/24/2026. The exploitation is known to be easy. The attack may be launched remotely. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 04/07/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-19609).
Productinfo
Name
MLflow
Version
3.10.0
3.10.1
Website
Product: https://github.com/mlflow/mlflow/
CPE 2.3info
🔒
🔒
CPE 2.2info
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3info
VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Authorization
CWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: no mitigation known
Status: 🔍
0-Day Time: 🔒
Timelineinfo
03/24/2026 CVE reserved
04/07/2026 +13 days Advisory disclosed
04/07/2026 +0 days VulDB entry created
04/07/2026 +0 days VulDB entry last update
Sourcesinfo
Product: github.com
Advisory: github.com
Researcher: Sławomir Zakrzewski
Status: Confirmed
CVE: CVE-2026-33866 (🔒)
GCVE (CVE): GCVE-0-2026-33866
GCVE (VulDB): GCVE-100-355742
EUVD: 🔒
Entryinfo
Created: 04/07/2026 15:28
Updated: 04/07/2026 17:04
Changes: 04/07/2026 15:28 (64), 04/07/2026 17:04 (1)
Complete: 🔍
Cache ID: 99:169:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸