MLflow CrewAI autologging records LLM provider API keys in logged trace spans

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

• CISA KEV Not listed.
• EPSS 0.0021, the 10th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

1. 27 Oct 2026, 19:56 UTC Confirmed by the CVE List
2. 27 Oct 2026, 20:17 UTC Confirmed by NVD
3. 31 Oct 2026, 14:07 UTC First seen by agentprime
4. 31 Oct 2026, 14:07 UTC Confirmed by OSV

Sources

• GitHub Advisory Database: GHSA-j7qq-vr8c-xvw3
• OSV: GHSA-j7qq-vr8c-xvw3
• github.com/mlflow/mlflow/security/advisories/GHSA-j7qq-vr8c-xvw3
• github.com/mlflow/mlflow/pull/25845
• github.com/mlflow/mlflow/commit/20927930d27f0072fcfeb7f024f24ad8c5e77c47
• github.com/mlflow/mlflow
• github.com/mlflow/mlflow/releases/tag/v3.17.0

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.