← Back
CVE-2026-10803
low
CVSS 3.6
Vulnerability in mlflow (CVE-2026-10803)
Summary
vulnerability in mlflow (CVE-2026-10803). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `3.10.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-10803** has been found in mlflow.
Risk of unauthorized operations or information disclosure. CVSS score: 3.6/10.
What to do: upgrade mlflow to **3.10.1** or later.
If unsure, ask your IT team or search "mlflow CVE-2026-10803" on the vendor's site.
CVE-2026-10803 (mlflow) — CWE-327 / CVSS v3 3.6
Attack vector: local / no user interaction
Patched: `3.10.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-327) exists in mlflow.
📍 Affected scope
mlflow — .
🔥 Severity
Severity: Low (CVSS 3.6/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.10.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.10.1ステージング環境で 3.10.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.10.1"}]}]
PyPI
mlflow
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.1"}]}]
References
- advisory https://vuldb.com/cve/CVE-2026-10803
- advisory https://vuldb.com/submit/831462
- advisory https://vuldb.com/vuln/368252
- report https://github.com/mlflow/mlflow/issues/22419
- report https://github.com/mlflow/mlflow/pull/22420
- report https://vuldb.com/vuln/368252/cti
- web https://nvd.nist.gov/vuln/detail/CVE-2026-10803
- web https://github.com/mlflow/mlflow
- web https://github.com/advisories/GHSA-5qmp-p3c4-72qj
- web https://github.com/mlflow/mlflow/