CVE-2026-116692MLflow: Remote code execution on unauthenticated MLflow servers via third-party scorer deserialization importing caller-placed artifact modules
- 9.8CriticalCVSS base score
- 2.4%Exploitation in 30 daysEPSS · top 16% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- 1Public exploitsMetasploit, Nuclei and Exploit-DB
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.
Public exploit
An exploit or proof of concept is public: anyone can try it against an unpatched system. The public collections list a Nuclei template for it. CISA's SSVC rates its exploitation: a proof of concept is public.
Show the exploits1
Nuclei templates1 template
- MLflow < 3.17.0 - Third-Party Scorer Deserialization Remote Code Execution (Nuclei template) (opens in a new tab)
http/cves/2026/CVE-2026-116692.yamlSeverity critical
Modules, templates and exploits as listed by the Metasploit Framework (BSD-3-Clause), ProjectDiscovery's Nuclei templates (MIT) and the Exploit Database (GPLv2), read once a day. Where the data comes from
Timeline
ID reserved
By GitHub_M
- 1 day later
· 1 day later
Published
- 6 days later
· 6 days later
Record updated
- 17 days later
· 17 days later
EPSS rose above 1%
0.70% → 2.4%
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| GitHub_MCNA (assigner) | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Awaiting Analysis | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 2.4% · top 16% of all CVEs (19 Nov 2026)
- CISA SSVC
- Exploitation: poc · Automatable: yes · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.
Affected products
Affected packages
From reviewed advisories of the GitHub Advisory Database.
- PyPImlflowGHSA-26p8-2jq9-3vq9 (opens in a new tab)
References
References4
- https://github.com/mlflow/mlflow/security/advisories/GHSA-26p8-2jq9-3vq9 (opens in a new tab)x_refsource_CONFIRM
- https://github.com/mlflow/mlflow/pull/25906 (opens in a new tab)x_refsource_MISC
- https://github.com/mlflow/mlflow/commit/a732443e695c3c677680c54320efc394c81654ab (opens in a new tab)x_refsource_MISC
- https://github.com/mlflow/mlflow/releases/tag/v3.17.0 (opens in a new tab)x_refsource_MISC
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-111383 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisory GHSA-26p8-2jq9-3vq9 (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-116692)Record last updated .