Skip to main content
CVE-2026-116692VulnerabilityPublished

MLflow: Remote code execution on unauthenticated MLflow servers via third-party scorer deserialization importing

Affects mlflowSource GCVE Database

0
Compare
Authoritative record:CVE-2026-116692· Critical 9.8

Not known to be exploited · CVSS 9.8 Critical : upgrade to 3.17.0 as a priority.

Data as of 17 Nov 2026, 16:33 UTC

CVSS 3.1 base score
9.8Critical
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.19.8
Patch
Available – fixed in 3.17.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

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

    Not in CISA KEV and no source reports exploitation

  5. 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.12.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. Deployments should ensure that the allowed scorer packages are not writable by the server process if upgrading is not immediately possible. For basic-auth deployments, restrict permissions to minimize the ability to create experiments and upload artifacts. No other specific mitigations are indicated by the vendor advisory.

Description

MLflow versions from 3.12.0 up to but not including 3.17.0 contain a critical vulnerability that allows remote code execution via third-party scorer deserialization. This occurs because the system accepts request-selected descendants of allowed modules rather than enforcing exact module restrictions. Unauthenticated deployments are vulnerable to code execution without credentials, while basic-auth deployments require elevated permissions. The vulnerability is fixed in version 3.17.0.

References

Community reviews

Loading reviews…