CVE Intelligence
Medium Info disclosure

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

MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. From 2.19.0 until 3.17.0, mlflow.crewai.autolog() records CrewAI Agent objects without consistently sanitizing nested credential-bearing values. mlflow/crewai/autolog.py::_get_agent_attributes() converts the Agent llm field to a string that includes the provider API key, while mlflow/crewai/autolog.py::_construct_full_inputs() expands the Agent object into mlflow.spanInputs. Applications can therefore send plaintext provider credentials to the MLflow trace backend or a configured OTLP destination, where trace readers can obtain them. This issue is fixed in version 3.17.0.

Published Oct 27, 2026 · Updated Oct 28, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+2
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.21%
ahead of 11% of scored CVEs · Oct 29, 2026
Affects
Mlflow
Mlflow
CVSS base
6.5
Medium · 3 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Pip Mlflow: fixed in version 3.17.0 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Mlflow Mlflow, Pip Mlflow).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes matching the vulnerability class (info disclosure), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Mlflow Mlflow version >= 2.19.0, < 3.17.0 Vulnerable CVE Program (cve.org) e CISA ADP
Pip Mlflow ≥ 2.19.0 and < 3.17.0 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.5 CVSS 3.1 Medium 2.8 3.6 security-advisories@github.com via NIST National Vulnerability Database
6.5 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
6.5 CVSS 3.1 Medium — — GitHub_M via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N (score shown at the top: security-advisories@github.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-200 · Exposure of Sensitive Information

Other CVEs with this weakness →

EPSS over time FIRST

Oct 28, 2026 → Oct 29, 2026 · 2 reading(s) · max 0.21%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Look for anomalous data read/export volumes and access to sensitive records.
web/proxy/WAF logsnetwork IDS/IPSapplication logsauthentication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 28, 2026 · GitHub Security Advisories
  • Affected products added · pip/mlflow
    Oct 28, 2026 · GitHub Security Advisories
  • Source status changed · Received → Awaiting Analysis
    Oct 28, 2026 · NIST National Vulnerability Database
  • Affected products added · mlflow/mlflow
    Oct 27, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 27, 2026
  • CVSS changed · 6.5
    Oct 27, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 27, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 27, 2026 · Alertas do Telegram
  • CVE published
    Oct 27, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 27, 2026 – Oct 28, 2026
  • 1× Official description updated · Oct 27, 2026 – Oct 27, 2026

References

5 on the record

Elsewhere on this site

Mlflow
every CVE for this vendor
Info disclosure
same class
CWE-200
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-116692 MLflow: Remote code execution on unauthenticated MLflow servers via third-party scorer deserialization importing caller-placed artifact modules 2d
  • CVE-2026-116690 MLflow: Arbitrary file read on unauthenticated MLflow servers via prompt model version source 2d
  • CVE-2026-115886 MLflow: SSRF on unauthenticated MLflow servers via third-party scorer kwargs in the scorer invoke, register, and GenAI evaluate endpoints 6d
  • CVE-2026-53995 MLflow 3.17.1 Path Traversal via Trace ID API 10d
  • CVE-2026-96804 CVE-2026-96804 Sep 23, 2026
  • CVE-2026-96775 MLflow dspy bypasses pickle deserialization control Sep 23, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-116691 is "MLflow CrewAI autologging records LLM provider API keys in logged trace spans", rated Medium. It affects Mlflow (Mlflow); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.5 describes technical severity. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.