CVE-2025-1474 json
Weak Password Requirements in mlflow/mlflow
published last yr. modified 2mo ago also BIT-mlflow-2025-1474 , EUVD-2025-6810 , GHSA-4rj2-9gcx-5qhx , PYSEC-2025-17
- cvss
- 3.8
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
In mlflow/mlflow version 2.18, an admin is able to create a new user account without setting a password. This vulnerability could lead to security risks, as accounts without passwords may be susceptible to unauthorized access. Additionally, this issue violates best practices for secure user account management. The issue is fixed in version 2.19.0.
Patch / fix
- pypi mlflow 2.19.0
- bitnami mlflow 2.19.0
- mlflow mlflow/mlflow 2.19.0
Is CVE-2025-1474 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- huntr.com https://huntr.com/bounties/e79f7774-10fe-46b2-b522-e73b748e3b2d referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 3.8 | CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N |
| GitHub | 3.0 | 3.8 | CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:N |
| OSV | 3.1 | 5.5 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | mlflow | <2.19.0 |
2.19.0 |
| bitnami | mlflow | <2.19.0 |
2.19.0 |
Affected products
- mlflow mlflow/mlflow
Classification
- Weakness
-
- CWE-521 Weak Password Requirements
References
-
github.com
/mlflow/mlflow/commit/149c9e18aa219bc47e86b432e130e467a36f4a17
web, patch
-
huntr.com
/bounties/e79f7774-10fe-46b2-b522-e73b748e3b2d
web, exploit, third-party-advisory, advisory, evidence
-
nvd.nist.gov
/vuln/detail/CVE-2025-1474
advisory, web
-
github.com
/mlflow/mlflow
package
-
github.com
/pypa/advisory-database/tree/main/vulns/mlflow/PYSEC-2025-17.yaml
web
-
github.com
/advisories/GHSA-4rj2-9gcx-5qhx
advisory
Sources
- CVE List CVE-2025-1474
- GitHub Advisory GHSA-4rj2-9gcx-5qhx
- NVD CVE-2025-1474
- OSV BIT-mlflow-2025-1474
- OSV PYSEC-2025-17
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.