mlflow
Affected
- introduced
0, fixed3.11.0(ecosystem)
Fixed versions
3.11.0
Fix
- Fixed version
3.11.0pip install --upgrade mlflow==3.11.0
Advisory
Also known as: BIT-mlflow-2026-4035, CVE-2026-4035, GHSA-g35p-px32-whv6
The record has no summary.
A vulnerability in mlflow/mlflow versions prior to 3.11.0 allows for the resolution of environment variables in AI Gateway secrets, which can be exploited to exfiltrate sensitive server-side environment credentials to an attacker-controlled endpoint. This issue arises because the api_key field in gateway secrets can accept $ENV_VAR references, which are resolved against the MLflow server's environment during runtime. The resolved secrets are then sent in provider authentication headers to the configured upstream api_base. This vulnerability can be exploited by low-privileged authenticated users in basic-auth deployments or by unauthenticated users in default deployments without basic-auth. The impact includes potential leakage of sensitive credentials such as cloud artifact credentials (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY), which could lead to artifact poisoning and cross-boundary code execution in downstream environments. The issue is fixed in version 3.11.0.
High Basis: CVSS v3 score 7.7, vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
0, fixed 3.11.0 (ecosystem)3.11.0
3.11.0pip install --upgrade mlflow==3.11.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: PyPA Advisory Database · CC BY 4.0