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

[ Why it matters ]Priority signals

• Public proof-of-concept exploit exists (CISA SSVC)

[ Description ]Official 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.

[ Fixes ]Fixes and patches

• mlflow 3.17.0Fixed version · GitHub Advisories · pip package mlflow: upgrade to 3.17.0 or later (affected >= 2.19.0, < 3.17.0)

[ Advisories ]Government CERT advisories

• BSI CERT-Bund12 Oct 2026WID-SEC-2026-3875

  MLflow: Multiple vulnerabilities allow information disclosure Translated from German

  CVE-2026-116691CVE-2026-116690

[ Packages ]Affected open-source packages

• mlflow pipAffected >= 2.19.0, < 3.17.0 · fixed in 3.17.0 · GHSA-j7qq-vr8c-xvw3

[ References ]References

• github.com/mlflow/mlflow/commit/20927930d27f0072fcfeb7f024f24ad8c5e77c47
• github.com/mlflow/mlflow/pull/25845
• github.com/mlflow/mlflow/releases/tag/v3.17.0
• github.com/mlflow/mlflow/security/advisories/GHSA-j7qq-vr8c-xvw3