MLflow CrewAI autologging records LLM provider API keys in logged trace spans
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
Reports 1
1 outlet mention it. Reports are not confirmation; each links to its source.
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.
Text from CVE List
Affected versions 1
- mlflowaffected: >= 2.19.0, < 3.17.0CVE List