Loading vulnerability…
CVE-2026-4035 affects MLflow versions before 3.11.0 with AI Gateway APIs enabled. AI Gateway secret handling resolved an api_key value prefixed with "$" as a reference to an environment variable in the MLflow server process. The resolved value was subsequently included in provider authentication headers for requests sent to the user-configured upstream API base. An attacker can create a gateway secret referencing a sensitive server-side environment variable, configure an attacker-controlled upstream endpoint, and invoke a gateway request to receive the resolved secret. MLflow 3.11.0 changes this behavior by making environment-based API-key resolution conditional on the MLFLOW_GATEWAY_RESOLVE_API_KEY_FROM_ENV setting, which defaults to disabled for API-driven gateway deployments.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A distinct MLflow AI Gateway gateway-secret vulnerability involving server-side $ENV_VAR resolution in the api_key field, which can leak credentials to the configured upstream. The content states that its fix does not address CVE-2026-71211's api_base SSRF issue.
An information disclosure vulnerability in MLflow AI Gateway secrets handling that allows environment variable references in the api_key field to be resolved on the server and sent to an attacker-controlled upstream endpoint, potentially exposing sensitive credentials.
A critical MLflow AI Gateway vulnerability that allows environment variable exfiltration via $-prefixed api_key resolution to attacker-controlled endpoints, enabling credential theft and potential downstream supply-chain compromise.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.