Skip to main content
VulnerabilityPublished

CVE-2026-116691: MLflow CrewAI autologging records LLM provider API keys in logged trace spans

Affects mlflowSource GCVE Database

0
Compare
Authoritative record:CVE-2026-116691· Medium 6.5

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

Data as of 17 Nov 2026, 16:34 UTC

CVSS 3.1 base score
6.5Medium
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.16.5
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. 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
  • >=2.19.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 issue is fixed. Until upgrading, avoid sending sensitive credential-bearing Agent objects to the trace backend or OTLP destinations, or sanitize credentials before logging. Since a patch is available, applying the official fix is the recommended mitigation.

Description

MLflow versions from 2.19.0 up to but not including 3.17.0 have a vulnerability in the CrewAI autologging feature where API keys for large language model providers are recorded in plaintext within logged trace spans. This occurs because the autolog function converts Agent objects to strings including sensitive credentials and expands these into trace inputs, potentially exposing provider API keys to anyone with access to the trace backend or OTLP destination. The issue is fixed in version 3.17.0.

References

Community reviews

Loading reviews…