CVE-2026-116691: medium-severity vulnerability in mlflow
MLflow CrewAI autologging records LLM provider API keys in logged trace spans
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 6.5epss 0.2%
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Affected products
mlflow · mlflowRelated CVEs — mlflow
In the same product, most dangerous first.
CVE-2026-64849CRITICALMLflow: Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed via unvalidated HTTP redirects (and DNS rebinding)EPSS 10.0%KEVCVE-2026-116690HIGHMLflow: Arbitrary file read on unauthenticated MLflow servers via prompt model version sourceEPSS 1.8%CVE-2026-116692CRITICALMLflow: Remote code execution on unauthenticated MLflow servers via third-party scorer deserialization importing caller-placed artifact modulesEPSS 0.7%CVE-2026-115886MEDIUMMLflow: SSRF on unauthenticated MLflow servers via third-party scorer kwargs in the scorer invoke, register, and GenAI evaluate endpointsEPSS 0.7%CVE-2026-53995HIGHMLflow 3.17.1 and prior Path Traversal via Trace ID APIEPSS 0.6%CVE-2026-79721HIGHCVE-2026-79721EPSS 0.5%