CVE-2026-116691
MLflow is an open source AI engineering platform for agents, large …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
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
- github.com/advisories/GHSA-j7qq-vr8c-xvw3
- nvd.nist.gov/vuln/detail/CVE-2026-116691
- cve.org/CVERecord?id=CVE-2026-116691
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.