Skip to main content
Exploitation reportedNot in CISA KEV yetFix available

CVE-2026-4035

Exploitation reported by one source. First attested on 2026-11-03 by GCVE · previdian.

  • Published2026-06-03
  • Fixed in3.11.0
  • WeaknessCWE-201

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2026-06-0309:16CVE publishedNVD
  2. 2026-11-0309:11Exploitation first reportedGCVE
  3. 2026-11-0309:11Listed as exploited by GCVEGCVE

Versions per branch

NVD · OSV
Lfprojects mlflow
BranchAffectedFixed in
3.11< 3.11.03.11.0

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As @huntr_ai, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • mlflow/mlflow
    Affected
    • < 3.11.0fixed in 3.11.0custom

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-06-03

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • mlflowTuxCare:PyPIfrom 2.22.4 · fixed in 2.22.4.post6+tuxcare
  • mlflowTuxCare:PyPIfrom 2.9.1 · fixed in 2.9.1.post6+tuxcare
  • mlflowChainguardall versions · fixed in 3.16.0-r0

Full record on NVD

Fix

  1. Update Lfprojects mlflow to 3.11.0

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • GCVEexploitation2026-11-03
  • CISA-ADPSSVC decisionpoc2026-06-03
  • CNACVSS 3.17.7known since 2026-10-23
  • NVDCVSS 3.17.7read 2026-10-23
  • CNACVSS 3.09.1known since 2026-10-23
  • CNAweakness (CWE)CWE-201known since 2026-10-23
  • FIRST EPSSEPSS score0.5 %2026-11-08
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryCRITICAL2026-07-10

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Published
2026-06-03
Last Modified
2026-08-14
NVD status
Modified
GitHub Advisory
GHSA-g35p-px32-whv6

Frequently asked questions

What is CVE-2026-4035?

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.

Is CVE-2026-4035 actively exploited?

A proof-of-concept exploit exists for CVE-2026-4035, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2026-4035?

CVE-2026-4035 has a CVSS v3 base score of 7.7 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N.

Running mlflow? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record