Authentication bypass via unvalidated account passwords
Published Oct 29, 2025 · Updated Oct 29, 2025
Weak password requirements in MLflow 2.21.0 allow remote attackers to bypass basic authentication through user registration. SqlAlchemyStore.create_user hashes passwords without validating their length, while the signup form accepts values as short as four characters. Exposure requires the basic-auth tracking server, and a newly registered account receives default READ access to tracked resources.
Summary
What happened
Weak password requirements in MLflow 2.21.0 allow remote attackers to bypass basic authentication through user registration. SqlAlchemyStore.create_user hashes passwords without validating their length, while the signup form accepts values as short as four characters. Exposure requires the basic-auth tracking server, and a newly registered account receives default READ access to tracked resources.
The record
- CVE
- CVE-2025-11200
- Published
- Oct 29, 2025
- Updated
- Oct 29, 2025
- Vendor
- MLflow Project
- Product
- MLflow
- Classifications
- CWE-521, T1136
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 29, 2025CVE publishedPublication date reported by the CVE source.
- Oct 29, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.21.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo