# 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 suscep...

Advisory record · `GHSA-4rj2-9gcx-5qhx`

- **Identifiers:** `GHSA-4rj2-9gcx-5qhx` · `BIT-mlflow-2025-1474` · `CVE-2025-1474` · `PYSEC-2025-17`
- **State:** Confirmed
- **Severity:** CVSS 3.8 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-521](https://cwe.mitre.org/data/definitions/521.html)
- **Tags:** [Hard-coded credentials](https://agentprime.io/advisories/tag/hard-coded-credentials.md)
- **Published:** 20 Mar 2025
- **Updated:** 10 Jun 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 20 Mar 2025, 10:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `mlflow` (PyPI): affected `<149c9e18aa219bc47e86b432e130e467a36f4a17 || <2.19.0`; fixed in `149c9e18aa219bc47e86b432e130e467a36f4a17`, `2.19.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The mlflow package, versions before 2.19.0, lets an administrator create a user account without setting a password. An attacker would need admin access to exploit this, and accounts created this way may be reachable without authentication. Upgrade mlflow to version 2.19.0 or later.

Written 10 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 3.8 Low, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N`, from CNA (@huntr_ai)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0036, the 30th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 20 Mar 2025. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-4rj2-9gcx-5qhx](https://github.com/advisories/GHSA-4rj2-9gcx-5qhx)
- [OSV: GHSA-4rj2-9gcx-5qhx](https://osv.dev/vulnerability/GHSA-4rj2-9gcx-5qhx)
- <https://github.com/mlflow/mlflow/commit/149c9e18aa219bc47e86b432e130e467a36f4a17>
- <https://huntr.com/bounties/e79f7774-10fe-46b2-b522-e73b748e3b2d>
- <https://github.com/advisories/GHSA-4rj2-9gcx-5qhx>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-4rj2-9gcx-5qhx>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-4rj2-9gcx-5qhx/>. Everything for agents: <https://agentprime.io/llms.txt>.