MLflow: Environment variable injection in AI Gateway secrets enables server-side credential exfiltration
CVE-2026-4035 · GHSA-g35p-px32-whv6 · published 2026-06-03 · updated 2026-07-10
- Severity
- Critical
- CVSS score
- 9.1
- Chance of exploitation (EPSS)
- 0.52%
- Fixed in
- 3.11.0
- Exploitation Public proof of concept
- Automatable No
- Technical impact Partial
- CISA SSVC
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.
Upgrade mlflow to 3.11.0 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| mlflow | PyPI | < 3.11.0 | 3.11.0 |
- CriticalPhoenix: Format String Injection in applyChatTemplatearize-phoenix
- CriticalFlowise: Unauthenticated OAuth2 token refresh endpoint returns access tokens — enables token theft for any connected serviceflowise
- CriticalvLLM has RCE In Video Processingvllm
- HighConfig revision hashes could expose password verifiersopenclaw
- Highn8n: Shared Credential Header Leak via HTTP Request Pagination Expressionn8n, n8n, n8n
- HighWorkspace dotenv files could override provider credentialsopenclaw
- CriticalMLflow: Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed via unvalidated HTTP redirects (and DNS rebindingmlflowExploited
- CriticalMLflow vulnerable to remote code execution on unauthenticated servers via third-party scorer deserialization importing caller-placed artifacmlflow
- CriticalMLflow allows unauthorized access to multipart upload endpoints when the `--serve-artifacts` mode is enabledmlflow
- CriticalMLflow: Improper Origin Validation in MLflow Assistant /ajax-api Endpoints Enables Browser-Mediated Local Command Executionmlflow
- Criticalmlflow: FastAPI job endpoints under `/ajax-api/3.0/jobs/*` are not protected by authentication or authorizationmlflow
- CriticalMlflow: Command Injection when serving models with enable_mlserver=Truemlflow
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.