MLflow vulnerable to arbitrary file read on unauthenticated servers via prompt model version source
CVE-2026-116690GHSA-m65p-9j7q-6w33
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (mlflow 3.17.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI mlflow
- Affected
- >= 3.10.0, < 3.17.0
- Fixed in
- 3.17.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-m65p-9j7q-6w33 lists affected ranges: PyPI mlflow >=3.10.0 <3.17.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-m65p-9j7q-6w33 lists affected ranges: PyPI mlflow >=3.10.0 <3.17.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- EPSS
- CVE-2026-116690: 1.80% estimated exploitation activity in the next 30 days; percentile 78.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary On MLflow tracking servers running without authentication, which is the default for mlflow server, a remote attacker can read arbitrary files from the server’s filesystem by creating a model version tagged as a prompt whose source is a schemeless local path. The fix for CVE-2026-2614 in 3.10.0 added a prompt-specific branch to the `CreateModelVersion` handler that rejects `file://` URIs and absolute paths but runs path validation only when the source carries a URL scheme. A schemeless value such as `../../etc`, a plain relative name, `.`, a percent-encoded path, or a Windows drive-letter path is therefore stored unchanged as the model version’s artifact location, and the `model-versions/get-artifact endpoint` later serves files from it with the privileges of the server process. The tag check also keyed on the presence of the `mlflow.prompt.is_prompt` tag rather than its value, so a false value still selected the weaker branch. Servers using `--app-name basic-auth` are…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from osv record GHSA-m65p-9j7q-6w33
- Revision 1 · created ·
Published from ghsa record GHSA-m65p-9j7q-6w33
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-116690 Advisory: MLflow vulnerable to arbitrary file read on unauthenticated servers via prompt model version source IDs: CVE-2026-116690, GHSA-m65p-9j7q-6w33 Record: https://patchnext.com/advisories/cve-2026-116690 (revision 2, source checked 28 Oct 2026, 06:05 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: mlflow 3.17.0. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI mlflow: affected >= 3.10.0, < 3.17.0; fixed in 3.17.0 ## Suggested inspection (read-only) - `python -m pip show mlflow`: prints the installed version. Run with the environment that serves production active. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on mlflow. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-m65p-9j7q-6w33 (OSV record GHSA-m65p-9j7q-6w33 lists affected ranges: PyPI mlflow >=3.10.0 <3.17.0 (fixed)) - Verified: https://github.com/advisories/GHSA-m65p-9j7q-6w33 (GitHub-reviewed advisory GHSA-m65p-9j7q-6w33 lists affected ranges: PyPI mlflow >=3.10.0 <3.17.0) Commands are suggestions: review each one before running it.
Loading voting…