I found an API key leak in MLflow, and why your AI agent may have one too

The author reports that MLflow's CrewAI autologging (mlflow.crewai.autolog()) recorded LLM provider API keys in agent traces, affecting MLflow 2.19.0 through 3.16.x; the issue is tracked as CVE-2026-116691 and fixed in MLflow 3.17.0 (PR #25845). The advisory recommends upgrading to mlflow>=3.17.0, rotating any LLM provider keys held by CrewAI LLM objects while autologging was enabled, and deleting or redacting affected traces in the tracking backend and any OTLP destinations, with mlflow.crewai.autolog(disable=True) as a workaround. The author also describes Weir, an open-source Apache-2.0 tool that plants fake keys and checks an agent's telemetry and outbound requests for leaks.