CVE-2026-3198

Analyzed Analyzed - Analysis Complete

Authentication Bypass in MLflow 3.9.0 Gateway API

Publication date: 2026-06-02

Last updated on: 2026-06-03

Assigner: huntr.dev

Description

MLflow 3.9.0 with basic-auth (`--app-name basic-auth`) fails to enforce authorization checks for multiple Gateway API 'list' endpoints. Specifically, the `BEFORE_REQUEST_HANDLERS` dictionary in `mlflow/server/auth/__init__.py` does not include entries for `ListGatewaySecretInfos`, `ListGatewayEndpoints`, and `ListGatewayModelDefinitions`. This allows any authenticated user, regardless of their assigned permissions, to enumerate all gateway secrets, endpoints, and model definitions. This vulnerability exposes sensitive information, such as API keys, endpoint configurations, and proprietary model definitions, to unauthorized users.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-06-02

Last Modified

2026-06-03

Generated

2026-07-12

AI Q&A

2026-06-02

EPSS Evaluated

2026-07-11

NVD

CVE-2026-3198

EUVD

EUVD-2026-33880

Affected Vendors & Products

Vendor	Product	Version / Range
lfprojects	mlflow	3.9.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-284	The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Attack-Flow Graph

Executive Summary

This vulnerability exists in MLflow version 3.9.0 when using basic-auth mode. The software fails to enforce proper authorization checks on several Gateway API 'list' endpoints. Specifically, certain endpoints like ListGatewaySecretInfos, ListGatewayEndpoints, and ListGatewayModelDefinitions are not included in the authorization check handlers. As a result, any authenticated user, regardless of their permissions, can access and enumerate sensitive information such as gateway secrets, API keys, endpoint configurations, and proprietary model definitions.

Impact Analysis

The impact of this vulnerability is that unauthorized users who have basic authentication credentials can access sensitive information that should be restricted. This includes API keys, endpoint configurations, and proprietary model definitions. Exposure of such information can lead to further security breaches, unauthorized access to systems, and potential misuse of confidential data.

Compliance Impact

This vulnerability allows any authenticated user to enumerate sensitive information such as API keys, endpoint configurations, and proprietary model definitions without proper authorization checks.

Exposure of such sensitive information could lead to non-compliance with data protection regulations like GDPR and HIPAA, which require strict access controls and protection of sensitive data.

Therefore, organizations using affected versions of MLflow may face compliance risks due to unauthorized disclosure of sensitive information.

Hi! I’m here to help you understand CVE-2026-3198. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70