CVE-2026-2651: CWE-862 Missing Authorization in mlflow mlflow/mlflow
A vulnerability in MLflow versions <=3.10.1.dev0 allows unauthorized access to multipart upload (MPU) endpoints when the `--serve-artifacts` mode is enabled. The authorization logic does not enforce resource-level permission checks for `/mlflow-artifacts/mpu/*` endpoints, enabling attackers to overwrite artifacts belonging to other users. This can lead to unauthorized cross-user writes, model supply chain poisoning, and arbitrary code execution when compromised models are loaded. The issue is resolved in version 3.10.0.
AI Analysis
Technical Summary
This vulnerability in MLflow affects versions up to 3.10.1.dev0 and involves missing authorization checks on multipart upload endpoints under the --serve-artifacts mode. Specifically, the /mlflow-artifacts/mpu/* endpoints lack proper resource-level permission enforcement, allowing unauthorized users with limited privileges to overwrite artifacts owned by others. Such unauthorized cross-user writes can result in supply chain attacks by poisoning models and may lead to arbitrary code execution upon loading the compromised models. The vulnerability is tracked as CWE-862 (Missing Authorization) and has a CVSS 3.0 base score of 9.0, indicating critical severity. The fix is included starting from MLflow version 3.10.0.
Potential Impact
Exploitation of this vulnerability allows attackers to overwrite artifacts of other users, which can lead to model supply chain poisoning and potentially arbitrary code execution when the compromised models are loaded. This impacts confidentiality, integrity, and availability of the MLflow artifact storage and model deployment processes. The CVSS score of 9.0 reflects high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
Upgrade MLflow to version 3.10.0 or later, where this vulnerability is resolved. Since no official patch link or vendor advisory is provided, users should verify the upgrade path from the MLflow project releases. Until upgraded, restrict access to the --serve-artifacts mode and carefully control user privileges to limit exposure. Patch status is not explicitly confirmed beyond the statement that the issue is resolved in version 3.10.0; check the official MLflow release notes for confirmation.
CVE-2026-2651: CWE-862 Missing Authorization in mlflow mlflow/mlflow
Description
A vulnerability in MLflow versions <=3.10.1.dev0 allows unauthorized access to multipart upload (MPU) endpoints when the `--serve-artifacts` mode is enabled. The authorization logic does not enforce resource-level permission checks for `/mlflow-artifacts/mpu/*` endpoints, enabling attackers to overwrite artifacts belonging to other users. This can lead to unauthorized cross-user writes, model supply chain poisoning, and arbitrary code execution when compromised models are loaded. The issue is resolved in version 3.10.0.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability in MLflow affects versions up to 3.10.1.dev0 and involves missing authorization checks on multipart upload endpoints under the --serve-artifacts mode. Specifically, the /mlflow-artifacts/mpu/* endpoints lack proper resource-level permission enforcement, allowing unauthorized users with limited privileges to overwrite artifacts owned by others. Such unauthorized cross-user writes can result in supply chain attacks by poisoning models and may lead to arbitrary code execution upon loading the compromised models. The vulnerability is tracked as CWE-862 (Missing Authorization) and has a CVSS 3.0 base score of 9.0, indicating critical severity. The fix is included starting from MLflow version 3.10.0.
Potential Impact
Exploitation of this vulnerability allows attackers to overwrite artifacts of other users, which can lead to model supply chain poisoning and potentially arbitrary code execution when the compromised models are loaded. This impacts confidentiality, integrity, and availability of the MLflow artifact storage and model deployment processes. The CVSS score of 9.0 reflects high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
Upgrade MLflow to version 3.10.0 or later, where this vulnerability is resolved. Since no official patch link or vendor advisory is provided, users should verify the upgrade path from the MLflow project releases. Until upgraded, restrict access to the --serve-artifacts mode and carefully control user privileges to limit exposure. Patch status is not explicitly confirmed beyond the statement that the issue is resolved in version 3.10.0; check the official MLflow release notes for confirmation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- @huntr_ai
- Date Reserved
- 2026-02-18T01:33:23.276Z
- Cvss Version
- 3.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a13eec0a5ae1af1aa6777ad
Added to database: 5/25/2026, 6:40:00 AM
Last enriched: 5/25/2026, 6:55:49 AM
Last updated: 5/26/2026, 7:54:26 AM
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.