CVE-2026-116691: MLflow CrewAI autologging records LLM provider API keys in logged trace spans
mlflow.crewai.autolog() leaks CrewAI LLM provider API keys into MLflow trace telemetry.
When a CrewAI Agent is instrumented with MLflow autologging, MLflow serializes the agent’s __dict__ and converts its fields to strings. The llm field contains the CrewAI LLM object, whose string representation includes its api_key in plaintext.
As a result, an application that calls mlflow.crewai.autolog() can unintentionally send its LLM provider API key to the MLflow trace backend or configured OTLP destination.
The application does not need to explicitly log the credential or place it in a span attribute. The credential is extracted automatically by MLflow’s instrumentation.
This was verified on MLflow 3.16.0 with CrewAI 1.15.18 using MLflow’s own OTLP exporter. The fake credential appeared in 5 attribute locations across 2 spans.
References
Code Behaviors & Features
Detect and mitigate CVE-2026-116691 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →