Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-2635 high CVSS 7.3

Vulnerability in mlflow (CVE-2026-2635)

Summary

Vulnerability in mlflow (CVE-2026-2635). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 3.8.0rc0 or later.

Original description

The description as published by the source.

MLflow Use of Default Password Authentication Bypass Vulnerability. This vulnerability allows remote attackers to bypass authentication on affected installations of MLflow. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the basic_auth.ini file. The file contains hard-coded default credentials. An attacker can leverage this vulnerability to bypass authentication and execute arbitrary code in the context of the administrator. Was ZDI-CAN-28256.

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-2635 has been found in mlflow.
Successful exploitation can lead to full system takeover. CVSS score: 7.3/10.
What to do: upgrade mlflow to 3.8.0rc0 or later.
If unsure, ask your IT team or search "mlflow CVE-2026-2635" on the vendor's site.

CVE-2026-2635 (mlflow) — CWE-1393 / CVSS v3 7.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.8.0rc0 — 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-1393) exists in mlflow.

📍 Affected scope

Check the vendor advisory for the affected versions of mlflow.

🔥 Severity

Severity: High (CVSS 7.3/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 3.8.0rc0.

🛡️ 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'mlflow' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で mlflow を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade mlflow to 3.8.0rc0

    ステージング環境で 3.8.0rc0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

PyPI mlflow
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.8.0rc0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details