# CVE-2025-14279: DNS Rebinding Vulnerability in mlflow/mlflow

> Attackers can bypass Same-Origin Policy via DNS rebinding to query, update, or delete MLflow experiments, leading to data exfiltration or manipulation.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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:** 12 Jan 2026
- **Updated:** 12 Jan 2026
- **Also known as:** BIT-mlflow-2025-14279, GHSA-pgqp-8h46-6x4j, PYSEC-2026-1656

## What is CVE-2025-14279?

CVE-2025-14279 is a high-severity vulnerability in Lfprojects Mlflow, published on 12 Jan 2026. 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

MLFlow versions up to and including 3.4.0 are vulnerable to DNS rebinding attacks due to a lack of Origin header validation in the MLFlow REST server. This vulnerability allows malicious websites to bypass Same-Origin Policy protections and execute unauthorized calls against REST endpoints. An attacker can query, update, and delete experiments via the affected endpoints, leading to potential data exfiltration, destruction, or manipulation. The issue is resolved in version 3.5.0.

Weakness: CWE-346 (Origin Validation Error)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mlflow` | Bitnami | All versions | 3.5.0 |
| `mlflow` | PyPI | All versions | 3.5.0 |
| `mlflow` | PyPI | All versions | 3.5.0 |
| `mlflow` | PyPI | All versions | 3.5.0 |

Products: Lfprojects Mlflow.

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

Upgrade mlflow to 3.5.0 or later.

## Is CVE-2025-14279 being exploited?

There is no known exploitation of CVE-2025-14279 in the wild and no public exploit code.

## 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-14279 and fix it if it is affected.

What it is: CVE-2025-14279 is a high-severity vulnerability in Lfprojects Mlflow, published on 12 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-14279 in the wild and no public exploit code.

Affected packages and fixed versions:
- mlflow (Bitnami): affected all versions; fixed in 3.5.0
- mlflow (PyPI): affected all versions; fixed in 3.5.0
- mlflow (PyPI): affected all versions; fixed in 3.5.0
- mlflow (PyPI): affected all versions; fixed in 3.5.0

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-14279/ (Markdown: https://insights.sbomify.com/CVE-2025-14279/index.md)
```

## Sources

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

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