CVE-2026-3198: mlflow/mlflow · Improper Access Control
Affects mlflow/mlflowSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| mlflowmlflow/mlflow | Affected
| Fixed in– |
AI-suggested
Until an official fix is available, restrict access to MLflow instances with basic-auth enabled to trusted users only and monitor for unauthorized access attempts. Avoid exposing MLflow Gateway API endpoints publicly and consider additional access controls or network segmentation to limit exposure.
Description
MLflow version 3.9.0 with basic authentication enabled has an improper access control vulnerability in several Gateway API list endpoints. Authenticated users can enumerate sensitive gateway secrets, endpoints, and model definitions without proper authorization. This exposure includes API keys and proprietary model details, potentially compromising confidentiality.