CVE-2026-116691

MLflow CrewAI autologging records LLM provider API keys in logged trace spans

Published Oct 27, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

MLflow versions 2.19.0 through 3.17.0 allow the CrewAI autologging feature to capture agent objects without sanitizing nested credential information. The internal conversion of the llm field to a string includes the provider API key, and the expansion of the agent object into span inputs can send the key to the trace backend or OTLP exporter. As a result, plaintext provider credentials become visible in trace logs, presenting a clear confidentiality breach that could expose sensitive API keys. The vulnerability does not grant code execution but can compromise any secrets that the application stores for language‑model providers.

Affected Systems

The affected product is MLflow. The vulnerability exists in all releases from 2.19.0 up to and including 3.17.0, with the fix applied in the 3.17.0 release and later. Users on earlier or later versions are not impacted.

Risk and Exploitability

The CVSS score of 6.5 indicates a medium severity level. Exposure is possible through any application that invokes CrewAI autologging, and the likely attack vector, inferred from the description, is local to the code execution environment. While official exploitation evidence is not reported and the EPSS score of 0.00207 (approximately 0.21%) indicates a very low exploitation probability, the absence of this vulnerability from CISA’s KEV catalog suggests it is not currently widely exploited. Nonetheless, the potential for leaking sensitive API keys makes this a significant risk to confidentiality, especially when trace data is forwarded to external OTLP services or stored in accessible locations.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade MLflow to version 3.17.0 or later to apply the vendor patch that removes API keys from trace logs.
  • If an immediate upgrade is not possible, disable CrewAI autologging or remove calls to mlflow.crewai.autolog() so that agent objects are no longer logged.
  • Configure the MLflow trace backend or OTLP exporter to filter or redact sensitive input data, and purge any traces that may already contain exposed credentials.

Generated by OpenCVE AI on November 4, 2026 at 10:59 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-j7qq-vr8c-xvw3 MLflow CrewAI autologging records LLM provider API keys in logged trace spans
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Mlflow
Mlflow mlflow
Vendors & Products Mlflow
Mlflow mlflow
Type Values Removed Values Added
Description 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.
Title MLflow CrewAI autologging records LLM provider API keys in logged trace spans
Weaknesses CWE-200
CWE-312
CWE-532
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

  • CWE-201

    Insertion of Sensitive Information Into Sent Data

  • CWE-312

    Cleartext Storage of Sensitive Information

  • CWE-532

    Insertion of Sensitive Information into Log File

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 3, 2026, 12:09 PM
Reserved
Oct 26, 2026, 8:00 PM
Status
Awaiting Analysis
Published
Oct 27, 2026, 8:17 PM
Modified
Nov 3, 2026, 1:17 PM
Severity
Moderate
Public date
Oct 27, 2026, 7:56 PM