Skip to main content
VulnerabilityPublished

CVE-2026-115886: mlflow · Unsafe Reflection

Affects mlflowSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium : upgrade to 3.17.0 when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.17.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade mlflow to 3.17.0.

Affected software

ProductAffectedFixed in
mlflowmlflowAffected
  • >=3.12.0rc0 <3.17.0
Fixed in
  • 3.17.0

AI-suggested

Upgrade MLflow to version 3.17.0 or later, where this vulnerability is fixed. No other mitigations are indicated or required according to the vendor advisory.

Description

MLflow versions from 3.12.0rc0 up to but not including 3.17.0 contain a vulnerability involving unsafe reflection in certain endpoints that accept serialized third-party scorer data. This flaw allows attackers to manipulate class selection and constructor arguments, potentially causing the server to make outbound requests to attacker-controlled or internal hosts. The issue is resolved in version 3.17.0.

References

Community reviews

Loading reviews…