CVE-2026-4035: Environment Variable Resolution Vulnerability in mlflow/mlflow
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 apikey field in gateway secrets can accept $ENVVAR 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 apibase. 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 (AWSACCESSKEYID, AWSSECRETACCESSKEY), which could lead to artifact poisoning and cross-boundary code execution in downstream environments. The issue is fixed in version 3.11.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
mlflow/mlflowto a version that resolves this vulnerability.Fixed in 3.11.0
Event History
Frequently Asked Questions
What is the severity of CVE-2026-4035?
The severity of CVE-2026-4035 is critical with a rating of 9.1.
How do I fix CVE-2026-4035?
To fix CVE-2026-4035, you should upgrade to mlflow/mlflow version 3.11.0 or later.
What is the impact of CVE-2026-4035?
CVE-2026-4035 allows attackers to exfiltrate sensitive server-side environment credentials via exploited AI Gateway secrets.
In which versions is CVE-2026-4035 present?
CVE-2026-4035 is present in mlflow/mlflow versions prior to 3.11.0.
What is exploited in CVE-2026-4035?
CVE-2026-4035 exploits the resolution of environment variables in AI Gateway secrets, specifically targeting the 'api_key' field.