Vulnerability in mlflow (CVE-2026-3198)
Summary
Vulnerability in mlflow (CVE-2026-3198). Confidential information can be exposed externally. Exploitable via BEFORE_REQUEST_HANDLERS. Mitigation: upgrade to 3.10.0 or later.
Original description
The description as published by the source.
MLflow 3.9.0 with basic-auth (--app-name basic-auth) fails to enforce authorization checks for multiple Gateway API 'list' endpoints. Specifically, the BEFORE_REQUEST_HANDLERS dictionary in mlflow/server/auth/__init__.py does not include entries for ListGatewaySecretInfos, ListGatewayEndpoints, and ListGatewayModelDefinitions. This allows any authenticated user, regardless of their assigned permissions, to enumerate all gateway secrets, endpoints, and model definitions. This vulnerability exposes sensitive information, such as API keys, endpoint configurations, and proprietary model definitions, to unauthorized users.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-3198 has been found in mlflow.
Attackers can target a specific entry point like BEFORE_REQUEST_HANDLERS over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade mlflow to 3.10.0 or later.
If unsure, ask your IT team or search "mlflow CVE-2026-3198" on the vendor's site.
CVE-2026-3198 (mlflow) — CWE-284 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: BEFORE_REQUEST_HANDLERS / ListGatewaySecretInfos / ListGatewayEndpoints / ListGatewayModelDefinitions
Patched: 3.10.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-284) exists in mlflow. Attackers reach the vulnerable code path via BEFORE_REQUEST_HANDLERS.
Check the vendor advisory for the affected versions of mlflow. Attack surface: BEFORE_REQUEST_HANDLERS / ListGatewaySecretInfos / ListGatewayEndpoints / ListGatewayModelDefinitions.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 3.10.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mlflow' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mlflow' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mlflowを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade mlflow to 3.10.0ステージング環境で 3.10.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web huntr.com
- web github.com
- web github.com