Information Exposure Affecting mlflow package, versions <3.16.0-r0


Severity

Recommended
0.0
high
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.66% (50th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-WOLFILATEST-MLFLOW-19827926
  • published15 Sept 2026
  • disclosed3 Jun 2026

Introduced: 3 Jun 2026

CVE-2026-4035  (opens in a new tab)
CWE-201  (opens in a new tab)

How to fix?

Upgrade Wolfi mlflow to version 3.16.0-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream mlflow package and not the mlflow package as distributed by Wolfi. See How to fix? for Wolfi relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1