CVE-2026-2635: MLflow Use of Default Password Authentication Bypass Vulnerability
MLflow Use of Default Password Authentication Bypass Vulnerability. This vulnerability allows remote attackers to bypass authentication on affected installations of MLflow. Authentication is not required to exploit this vulnerability.
The specific flaw exists within the basic_auth.ini file. The file contains hard-coded default credentials. An attacker can leverage this vulnerability to bypass authentication and execute arbitrary code in the context of the administrator. Was ZDI-CAN-28256.
Security readout for executives and security teams
Plain-English summary
MLflow 3.4.0 is reported to ship with hard-coded default credentials in basic_auth.ini. A remote attacker may bypass authentication and run code as the administrator. The source bundle does not show active exploitation, but the impact is severe for exposed MLflow servers.
Executive priority
Prioritize exposed MLflow 3.4.0 systems immediately. This is a critical unauthenticated path to administrator-level code execution, but current evidence does not prove exploitation in the wild.
Technical view
CVE-2026-2635 is an MLflow authentication bypass tied to default credentials in basic_auth.ini. ZDI reports unauthenticated remote exploitation can lead to arbitrary code execution in the administrator context. CVSS is 9.8, with network attack vector, low complexity, no privileges, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely in MLflow 3.4.0 deployments using the affected basic_auth.ini and reachable from untrusted networks. The bundle does not establish other affected versions or product variants.
Exploitation context
The CVE record says authentication is not required. KEV status is false, and the supplied sources do not claim active exploitation. Treat internet-facing systems as urgent because compromise could grant administrative code execution.
Researcher notes
Evidence is strong for the core flaw and severity, but incomplete for fixed versions, broader affected ranges, and exploitation activity. Avoid expanding scope beyond MLflow 3.4.0 unless vendor or distribution advisories add confirmation.
Mitigation direction
Inventory MLflow deployments and identify any running version 3.4.0.
Restrict MLflow access to trusted networks until vendor guidance is applied.
Review MLflow vendor guidance and PR 19260 for the official fix path.
Do not rely on shipped default authentication configuration.
Rotate credentials that may have matched defaults or been exposed.
Validation and detection
Confirm MLflow version and whether basic authentication is enabled.
Inspect basic_auth.ini for shipped default or hard-coded credentials.
Check whether the MLflow service is reachable from untrusted networks.
Review logs for unexpected administrator access or code execution activity.
Track Red Hat and MLflow advisories for affected-version clarification.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-1393: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-1393 · source CWE mapping
Use of Default Password
Use of Default Password represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.