MLflow Flaw CVE-2026-116692: Update Now
Published November 6, 2026 · Last updated November 6, 2026
The short version: CVE-2026-116692 is a critical-severity security flaw in MLflow. The National Vulnerability Database (NVD) published it on October 27, 2026, and the score it lists is 9.8 out of 10. When FraudMeNot checked on November 6, 2026, CISA had not added CVE-2026-116692 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.
What the official record says about CVE-2026-116692
The record was filed by github.com. In its own words: "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."
Why MLflow admins should care
Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on github.com rated CVE-2026-116692 9.8 (Critical) under CVSS 3.1. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker does not need an account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping MLflow running is high. Scoring string: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
Affected MLflow releases
According to the record, these releases are vulnerable:
- version >= 3.12.0rc0, < 3.17.0
The type of bug behind CVE-2026-116692
NVD classifies it using MITRE's Common Weakness Enumeration:
- CWE-94, Improper Control of Generation of Code. MITRE describes this class of bug as follows: "The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. (Roles: Common-Name, Attack-Focused)"
- CWE-470, Use of Externally-Controlled Input to Select Classes or Code. MITRE describes this class of bug as follows: "The product uses external input with reflection to select which classes or code to use, but it does not sufficiently prevent the input from selecting improper classes or code. (Roles: Common-Name, Attack-Focused, Common-Name)"
Vendor remediation for CVE-2026-116692
The vendor advisory remediation for operators of MLflow, quoted for this page, is: "Update MLflow to version 3.17.0 or later (GitHub security advisory GHSA-26p8-2jq9-3vq9)."
What to do about it
- Update now: Update MLflow to version 3.17.0 or later (GitHub security advisory GHSA-26p8-2jq9-3vq9).
- Who should act: IT teams, managed service providers, and developers who run or ship MLflow. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
- Read the official advisory from MLflow (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
- After patching, confirm the new version is actually running and review logs from October 27, 2026 onward for anything unusual.
- Home users: you do not need to buy or download anything because of CVE-2026-116692. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.
CVE-2026-116692 record details from CISA and NVD
- Attack complexity for CVE-2026-116692: low
- CVE-2026-116692 CVSS scope: unchanged
- NVD sub-scores for CVE-2026-116692: exploitability 3.9, impact 5.9.
- Who mapped the weakness type: the address listed on github.com (Secondary)
- References in the NVD record: 4.
- CISA SSVC decision points for CVE-2026-116692 (from NVD): exploitation=poc; automatable=yes; technicalImpact=total (role: CISA Coordinator, SSVC 2.0.3).
Dates to know
- October 27, 2026: NVD publishes CVE-2026-116692.
- November 6, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-116692 is not listed.
- November 2, 2026: most recent NVD update (record status: Awaiting Analysis).
Official references
Links listed in the NVD record (labels in brackets come from NVD):
- github.com/mlflow/mlflow/commit/a732443e695c3c677680c54320efc394c81654ab
- github.com/mlflow/mlflow/pull/25906
- github.com/mlflow/mlflow/releases/tag/v3.17.0
- github.com/mlflow/mlflow/security/advisories/GHSA-26p8-2jq9-3vq9
Sources
- NVD: CVE-2026-116692
- CVE.org: CVE-2026-116692
- MLflow advisory
- MLflow advisory
- MLflow advisory
- MITRE CWE-94
- MITRE CWE-470
General education only, not security advice. Facts checked against the sources above on the date shown.