
MLflowの認証なしRCE(CVE-2026-116692、CVSS 9.8)。許可リストの前方一致がなぜ攻撃者のモジュールを通したのか。3.16.0と3.17.0のwheel差分から、完全一致化・コード実行の分離・認可チェックの変更を読み解きます。 https://x.com/i/article/2115293334272983041
Signal is active with 8 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD description
MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. From 3.12.0rc0 until 3.17.0, third-party scorer deserialization in mlflow/genai/scorers/base.py accepts request-selected descendants of THIRD_PARTY_SCORER_ALLOWED_MODULES rather than requiring an exact allowed module. A caller can use MLflow artifact endpoints to place a Python module beneath a writable allowed package and submit its module and class through /ajax-api/3.0/mlflow/scorer/invoke. Scorer.model_validate_json() imports the module and constructs the class before trace processing. Authentication-disabled deployments permit this code execution without credentials, while basic-auth deployments require a principal capable of creating an experiment and run and uploading artifacts. In either configuration, the allowed scorer package must be writable by the server process. This issue is fixed in version 3.17.0.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
NONE
Momentum
STABLE

MLflowの認証なしRCE(CVE-2026-116692、CVSS 9.8)。許可リストの前方一致がなぜ攻撃者のモジュールを通したのか。3.16.0と3.17.0のwheel差分から、完全一致化・コード実行の分離・認可チェックの変更を読み解きます。 https://x.com/i/article/2115293334272983041

⚠️ CVE-2026-116692 (9.8) ⚠️ MLflow, the open source AI engineering platform, lets an attacker run their own code on the server. 3.12.0rc0 up to (but not including) 3.17.0 is affected. Upgrade to 3.17.0. https://t.co/zfxHcfSFr5

🚨 MLflow unauthenticated RCE (CVE-2026-116692), CVSS 3.1 9.8 (CNA) 🧠 Scorer deserialization imports a caller-uploaded module ⚠️ No-auth servers: no credentials needed ✅ Affected 3.12.0rc0 to <3.17.0; fixed in 3.17.0. Not in KEV 🔗 https://github.com/mlflow/mlflow/security/advisories/GHSA-26p8-2jq9-3vq9 #AppSec #MLOps https://t.co/lgOxMQWTl4

🚨 CRITICAL - RCE & Arbitrary File Read Vulnerabilities Patched in MLflow Two security vulnerabilities in MLflow allow unauthenticated attackers to compromise tracking servers: • CVE-2026-116692 (CVSS 9.8 Critical): Remote code execution via third-party scorer deserialization importing caller-placed artifact modules. • CVE-2026-116690 (CVSS 7.5 High): Path traversal in prompt model version source handling enabling arbitrary local file read. 👉 Affected: MLflow >= 3.10.0 / 3.12.0rc0 prior to 3.17.0 | Upgrade to v3.17.0 or later immediately

MLflow has a critical RCE flaw, CVE-2026-116692 (CVSS 9.8). On a server with no auth, anyone who can reach it can run Python code via scorer deserialization. Affects 3.12.0 up to 3.17.0. Fixed in 3.17.0. Update, and put auth in front of tracking servers. https://t.co/jRxrchLyA3

🚨 CVE-2026-116692 (CVSS 9.8 Critical) Deserialization flaw in MLflow allows unauthenticated remote attackers to execute arbitrary code via third-party scorer module loading. ⚡ Action: Upgrade MLflow to >= v3.17.0. 🔗 https://www.thehackerwire.com/vulnerability/CVE-2026-116692/ https://t.co/fzp5NkVerO

CVE-2026-116692 (CRITICAL / 9.8) — MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. From 3.... https://nvd.nist.gov/vuln/detail/CVE-2026-116692 #Python

Three MLflow flaws at once — worst is unauthenticated RCE to root. CVE-2026-116692: scorer deserialization lets attackers upload a malicious module and trigger server-side import. Official v3.14.0 image runs as uid 0. Fix: 3.17.0. Is your MLflow unauthenticated?

🔴 MLflow, Insecure Deserialization Vulnerability, #CVE-2026-116692 (Critical) -DC-Oct2026-3860 https://dailycve.com/mlflow-insecure-deserialization-vulnerability-cve-2026-116692-critical-dc-oct2026-3860/

An unconfirmed report flags CVE-2026-116692, a critical MLflow scorer flaw letting attackers run server code, affecting 3.12.0rc0 up to but not including 3.17.0. Upgrade to 3.17.0. https://t.co/TAbh7Y1YnW