Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-j7qq-vr8c-xvw3 | MLflow CrewAI autologging records LLM provider API keys in logged trace spans |
Tue, 27 Oct 2026 22:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mlflow
Mlflow mlflow |
|
| Vendors & Products |
Mlflow
Mlflow mlflow |
Tue, 27 Oct 2026 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | MLflow CrewAI autologging records LLM provider API keys in logged trace spans | |
| Weaknesses | CWE-200 CWE-312 CWE-532 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-27T19:56:22.083Z
Reserved: 2026-10-26T20:00:59.830Z
Link: CVE-2026-116691
No data.
Status : Received
Published: 2026-10-27T20:17:14.497
Modified: 2026-10-27T20:17:14.497
Link: CVE-2026-116691
No data.
OpenCVE Enrichment
Updated: 2026-10-27T22:15:10Z

Github GHSA