Skip to main content
VulnerabilityPublished

CVE-2026-116691: mlflow · Information Exposure

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 27 Oct 2026, 20:27 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 3.17.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 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
  • >=2.19.0 <3.17.0
Fixed in
  • 3.17.0
PyPImlflowpkg:pypi/mlflowOther threatsAffected
  • >=2.19.0 <=3.16.999
Fixed in–

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 issue is fixed. No other mitigations are specified or required.

Description

MLflow versions from 2.19.0 up to but not including 3.17.0 contain a vulnerability where the mlflow.crewai.autolog() function records CrewAI Agent objects without properly sanitizing nested credential values. This causes provider API keys to be included in plaintext within trace data sent to MLflow's trace backend or OTLP destinations. The issue is resolved in version 3.17.0.

References

Community reviews

Loading reviews…