# CVE-2025-1473: CSRF in mlflow/mlflow

> An attacker can exploit a CSRF vulnerability in the signup feature to create unauthorized accounts, potentially leading to account takeover.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 Mar 2025
- **Updated:** 20 Mar 2025
- **Also known as:** BIT-mlflow-2025-1473, GHSA-969w-gqqr-g6j3, PYSEC-2026-1646

## What is CVE-2025-1473?

CVE-2025-1473 is a medium-severity vulnerability in Lfprojects Mlflow, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A Cross-Site Request Forgery (CSRF) vulnerability exists in the Signup feature of mlflow/mlflow versions 2.17.0 to 2.20.1. This vulnerability allows an attacker to create a new account, which may be used to perform unauthorized actions on behalf of the malicious user.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2025-1473?

4 open source packages ship an affected version, including mlflow. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mlflow` | Bitnami | From 2.17.0 | 2.20.1 |
| `mlflow` | PyPI | From 2.17.0 | 2.20.3 |
| `mlflow` | PyPI | From 2.17.0 | 2.20.3 |
| `mlflow` | PyPI | From 2.17.0 | 2.20.3 |

Products: Lfprojects Mlflow.

## How do I fix CVE-2025-1473?

Upgrade mlflow to a fixed version for your release line: 2.20.1 or 2.20.3.

## Is CVE-2025-1473 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1473 exists.

## Other vulnerabilities in Lfprojects Mlflow

- [CVE-2026-64849](https://insights.sbomify.com/CVE-2026-64849/): MLflow Server-Side Request Forgery (critical 9.3, exploited in the wild)
- [CVE-2025-15379](https://insights.sbomify.com/CVE-2025-15379/): Command Injection in mlflow/mlflow (critical 10.0)
- [CVE-2024-0520](https://insights.sbomify.com/CVE-2024-0520/): Remote Code Execution due to Full Controlled File Write in mlflow/mlflow (critical 10.0)
- [CVE-2023-6977](https://insights.sbomify.com/CVE-2023-6977/): Path Traversal: '\..\filename' (critical 10.0)
- [CVE-2023-6709](https://insights.sbomify.com/CVE-2023-6709/): Improper Neutralization of Special Elements Used in a Template Engine in mlflow/mlflow (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1473 and fix it if it is affected.

What it is: CVE-2025-1473 is a medium-severity vulnerability in Lfprojects Mlflow, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1473 exists.

Affected packages and fixed versions:
- mlflow (Bitnami): affected from 2.17.0; fixed in 2.20.1
- mlflow (PyPI): affected from 2.17.0; fixed in 2.20.3
- mlflow (PyPI): affected from 2.17.0; fixed in 2.20.3
- mlflow (PyPI): affected from 2.17.0; fixed in 2.20.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-1473/ (Markdown: https://insights.sbomify.com/CVE-2025-1473/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-1473
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-1473
- OSV: https://osv.dev/vulnerability/CVE-2025-1473

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-1473/
Summaries are generated and may contain mistakes; the official description above is the record.