Skip to main content
VulnerabilityPublished

CVE-2026-116690: Arbitrary file read on unauthenticated MLflow servers via prompt model version source

Affects mlflowSource GCVE Database

0
Compare
Authoritative record:CVE-2026-116690· High 7.5

Not known to be exploited · public detection template (Nuclei) · CVSS 7.5 High : upgrade to 3.17.0 soon.

Data as of 17 Nov 2026, 16:34 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.17.5
Patch
Available – fixed in 3.17.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Oct 2026

  2. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade mlflow to 3.17.0.

Affected software

ProductAffectedFixed in
Bitnamimlflowpkg:bitnami/mlflowOther threatsAffected
  • >=3.10.0 <3.17.0
Fixed in
  • 3.17.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade MLflow to version 3.17.0 or later, where this vulnerability is fixed. Since a patch is available and the issue is resolved in 3.17.0, applying this official fix is the recommended remediation.

Description

MLflow versions from 3.10.0 up to but not including 3.17.0 contain a vulnerability that allows unauthenticated remote attackers to read arbitrary files on the server. This occurs because the prompt branch in the _create_model_version() function accepts schemeless relative sources without proper path validation. The flaw enables attackers to specify server-local paths as model version artifact locations and retrieve files via the /api/2.0/mlflow/model-versions/get-artifact endpoint. Default unauthenticated servers are fully exposed, while basic-auth deployments are vulnerable to authenticated users with model creation privileges. The issue is fixed in version 3.17.0.

References

Community reviews

Loading reviews…