CVE-2026-116691

Versions, checked against NVD

NVD's record (status: Awaiting Analysis) lists no affected versions of MLflow for this CVE. The ranges above come from the GitHub-reviewed advisory GHSA-j7qq-vr8c-xvw3.

NVD 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.

What to do

• Upgrade MLflow to 3.17.0 or later.
• Do not expose the component's API or UI to the internet without authentication in front of it.

Sources

• NVD: CVE-2026-116691
• https://github.com/mlflow/mlflow/commit/20927930d27f0072fcfeb7f024f24ad8c5e77c47
• https://github.com/mlflow/mlflow/pull/25845
• https://github.com/mlflow/mlflow/releases/tag/v3.17.0
• https://github.com/mlflow/mlflow/security/advisories/GHSA-j7qq-vr8c-xvw3

Read more

• MLflow authorization CVEs 2026