← Back
CVE-2026-2651
critical
CVSS 9.0
Vulnerability in mlflow (CVE-2026-2651)
Summary
vulnerability in mlflow (CVE-2026-2651). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `3.11.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-2651** has been found in mlflow.
Successful exploitation can lead to full system takeover. CVSS score: 9.0/10.
What to do: upgrade mlflow to **3.11.1** or later.
If unsure, ask your IT team or search "mlflow CVE-2026-2651" on the vendor's site.
CVE-2026-2651 (mlflow) — CWE-862 / CVSS v3 9.0
Attack vector: remote (network-reachable)
Patched: `3.11.1` — 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.
❓ What is the problem
**A vulnerability** (CWE-862) exists in mlflow.
📍 Affected scope
mlflow — .
🔥 Severity
Severity: Critical (CVSS 9.0/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **3.11.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade mlflow to 3.11.1ステージング環境で 3.11.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Bitnami
mlflow
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.11.1"}]}]
pip
mlflow
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.11.0rc1"}]}]
References
- web https://nvd.nist.gov/vuln/detail/CVE-2026-2651
- web https://github.com/mlflow/mlflow/commit/d7290811d8f3c95366d80109424edc1fb1ad966f
- web https://huntr.com/bounties/65beb119-d3e0-4e03-af2f-fa98f78f83dc
- web https://github.com/advisories/GHSA-8c7q-86fq-vvmh
- web https://access.redhat.com/security/cve/CVE-2026-2651
- web https://bugzilla.redhat.com/show_bug.cgi?id=2481117
- web https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-2651.json