← Back
CVE-2026-33866
Vulnerability in mlflow (CVE-2026-33866)
Summary
vulnerability in mlflow (CVE-2026-33866). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `3.11.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-33866** has been found in mlflow.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade mlflow to **3.11.1** or later.
If unsure, ask your IT team or search "mlflow CVE-2026-33866" on the vendor's site.
CVE-2026-33866 (mlflow) — CWE-862 /
Attack vector: remote (network-reachable) / no user interaction
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: ?. Risk of unauthorized operations or information disclosure
🔧 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"}]}]
PyPI
mlflow
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.11.0rc0"}]}]
pip
mlflow
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.11.0rc0"}]}]
References
- advisory https://cert.pl/en/posts/2026/04/CVE-2026-33865/
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-33866
- advisory https://github.com/advisories/GHSA-46r5-x6jq-v8g6
- package https://github.com/mlflow/mlflow
- patch https://github.com/mlflow/mlflow/pull/21708
- report https://afine.com/blogs/attacking-mlflow-how-ml-artifacts-become-attack-vectors
- web https://github.com/mlflow/mlflow/commit/005b959cacda05d1423356cfcbd9ebeda8ff96a7
- web https://cert.pl/en/posts/2026/04/CVE-2026-33865
- web https://github.com/pypa/advisory-database/tree/main/vulns/mlflow/PYSEC-2026-94.yaml