# MLFlow is vulnerable to DNS rebinding attacks due to a lack of Origin header validation

Advisory record · `GHSA-pgqp-8h46-6x4j`

- **Identifiers:** `GHSA-pgqp-8h46-6x4j` · `BIT-mlflow-2025-14279` · `CVE-2025-14279` · `PYSEC-2026-1656`
- **State:** Confirmed
- **Severity:** CVSS 8.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-346](https://cwe.mitre.org/data/definitions/346.html)
- **Tags:** [CWE-346](https://agentprime.io/advisories/tag/cwe-346.md)
- **Published:** 12 Jan 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 12 Jan 2026, 09:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `mlflow` (PyPI): affected `<3.5.0`; fixed in `3.5.0`

## Machine-written summary

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

> MLflow versions before 3.5.0 are vulnerable to DNS rebinding attacks because the REST server does not validate the Origin header. An attacker who lures a user to a malicious website can make unauthorized calls to REST endpoints to query, update, or delete experiments. Upgrade mlflow to version 3.5.0 or later.

Written 5 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

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

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

## Timeline

- 31 Oct 2026, 14:34 UTC: First seen by agentprime
- 31 Oct 2026, 14:34 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-pgqp-8h46-6x4j)

## Sources

- [GitHub Advisory Database: GHSA-pgqp-8h46-6x4j](https://github.com/advisories/GHSA-pgqp-8h46-6x4j)
- [OSV: GHSA-pgqp-8h46-6x4j](https://osv.dev/vulnerability/GHSA-pgqp-8h46-6x4j)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-14279>
- <https://github.com/mlflow/mlflow/pull/17910>
- <https://github.com/mlflow/mlflow/commit/b0ffd289e9b0d0cc32c9e3a9b9f3843ae83dbec3>
- <https://github.com/mlflow/mlflow>
- <https://huntr.com/bounties/ef478f72-2e4f-44dc-8055-fc06bef03108>

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-pgqp-8h46-6x4j>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-pgqp-8h46-6x4j/>. Everything for agents: <https://agentprime.io/llms.txt>.