# MLflow vulnerable to arbitrary file read on unauthenticated servers via prompt model version source

Advisory record · `GHSA-m65p-9j7q-6w33`

- **Identifiers:** `GHSA-m65p-9j7q-6w33` · `CVE-2026-116690`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 27 Oct 2026, 21:26 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `mlflow` (PyPI): affected `>=3.10.0, <3.17.0`; fixed in `3.17.0`

## Machine-written summary

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

> GHSA-m65p-9j7q-6w33 affects the PyPI package mlflow from 3.10.0 before 3.17.0, where a prompt model version can be created with a schemeless local path as its source. A remote attacker who can reach a tracking server running without authentication, which is the default for mlflow server, can create such a model version and then read arbitrary files the server process can access. On servers using basic-auth, any authenticated user who can create registered models can exploit this in the same way. Upgrade to mlflow 3.17.0, which is listed as the fixed version.

Written 31 Oct 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

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from CNA (GitHub_M)

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

## Timeline

- 31 Oct 2026, 14:07 UTC: First seen by agentprime
- 31 Oct 2026, 14:07 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-m65p-9j7q-6w33)

## Sources

- [GitHub Advisory Database: GHSA-m65p-9j7q-6w33](https://github.com/advisories/GHSA-m65p-9j7q-6w33)
- [OSV: GHSA-m65p-9j7q-6w33](https://osv.dev/vulnerability/GHSA-m65p-9j7q-6w33)
- <https://github.com/mlflow/mlflow/security/advisories/GHSA-m65p-9j7q-6w33>
- <https://github.com/mlflow/mlflow/pull/25870>
- <https://github.com/mlflow/mlflow/commit/81730a2ce4ebcd60d5d18f68c96f422ad7e30772>
- <https://github.com/mlflow/mlflow>
- <https://github.com/mlflow/mlflow/releases/tag/v3.17.0>

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-m65p-9j7q-6w33>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-m65p-9j7q-6w33/>. Everything for agents: <https://agentprime.io/llms.txt>.