CVE-2026-116692

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-27. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-111383 (ENISA EUVD) · GHSA-26p8-2jq9-3vq9 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
53rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 27, 2026

Last Modified

November 2, 2026

Advisory Details (4)

Auto-updated Nov 2, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, github_commit, github_pr.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Remote code execution on unauthenticated MLflow servers via third-party scorer deserialization importing caller-placed artifact modules · Advisory · mlflow/mlflow · GitHub

https://github.com/mlflow/mlflow/security/advisories/GHSA-26p8-2jq9-3vq9
GitHub release Patch Available

MLflow 3.17.0

Patch available: mlflow/mlflow v3.17.0

https://github.com/mlflow/mlflow/releases/tag/v3.17.0
GitHub pull request

Match third-party scorer modules exactly instead of by package prefix (GHSA-26p8-2jq9-3vq9)

Fix merged in mlflow/mlflow PR #25906 on 2026-09-16 — awaiting tagged release

https://github.com/mlflow/mlflow/pull/25906
GitHub commit

commit a732443e695c (mlflow/mlflow)

Fix landed in mlflow/mlflow commit a732443e695c — awaiting tagged release

https://github.com/mlflow/mlflow/commit/a732443e695c3c677680c54320efc394c81654ab

Vendor Advisories for CVE-2026-116692(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipmlflow @ 3.17.0 (fixes >= 3.12.0rc0, < 3.17.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
mlflow3.12.0 ... 3.16.1 (10 versions)
  • 3.12.0rc0 up to 3.17.0: fixed in 3.17.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 34× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 23:42 UTCEchelonGraph re-scored
  2. 2026-11-12 23:42 UTCGHSA enrichmentGHSA-26p8-2jq9-3vq9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  4. 2026-11-11 23:23 UTCEchelonGraph re-scored
  5. 2026-11-11 23:23 UTCGHSA enrichmentGHSA-26p8-2jq9-3vq9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  7. 2026-11-10 23:04 UTCEchelonGraph re-scored
  8. 2026-11-10 23:04 UTCGHSA enrichmentGHSA-26p8-2jq9-3vq9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  10. 2026-11-09 22:41 UTCEchelonGraph re-scored
  11. 2026-11-09 22:41 UTCGHSA enrichmentGHSA-26p8-2jq9-3vq9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  13. 2026-11-08 22:22 UTCEchelonGraph re-scored
  14. 2026-11-08 22:22 UTCGHSA enrichmentGHSA-26p8-2jq9-3vq9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  16. 2026-11-07 22:03 UTCEchelonGraph re-scored
  17. 2026-11-07 22:03 UTCGHSA enrichmentGHSA-26p8-2jq9-3vq9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  19. 2026-11-06 21:43 UTCEchelonGraph re-scored
  20. 2026-11-06 21:43 UTCGHSA enrichmentGHSA-26p8-2jq9-3vq9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  22. 2026-11-05 23:55 UTCOSV refresh
  23. 2026-11-05 21:24 UTCEchelonGraph re-scored
  24. 2026-11-05 21:24 UTCGHSA enrichmentGHSA-26p8-2jq9-3vq9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
Show 29 more
  1. 2026-11-04 21:05 UTCEchelonGraph re-scored
  2. 2026-11-04 21:05 UTCGHSA enrichmentGHSA-26p8-2jq9-3vq9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  4. 2026-11-03 20:45 UTCEchelonGraph re-scored
  5. 2026-11-03 20:45 UTCGHSA enrichmentGHSA-26p8-2jq9-3vq9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  7. 2026-11-02 20:26 UTCEchelonGraph re-scored
  8. 2026-11-02 20:26 UTCGHSA enrichmentGHSA-26p8-2jq9-3vq9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-11-02 19:47 UTCEchelonGraph re-scored
  10. 2026-11-02 19:47 UTCGHSA enrichmentGHSA-26p8-2jq9-3vq9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-11-02 17:28 UTCEchelonGraph re-scored
  12. 2026-11-02 17:28 UTCGHSA enrichmentGHSA-26p8-2jq9-3vq9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  14. 2026-11-01 17:08 UTCEchelonGraph re-scored
  15. 2026-11-01 17:08 UTCGHSA enrichmentGHSA-26p8-2jq9-3vq9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  17. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-26p8-2jq9-3vq9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-11-01 07:59 UTCEchelonGraph re-scored
  19. 2026-10-31 16:49 UTCEchelonGraph re-scored
  20. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  21. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  22. 2026-10-30 16:07 UTCEchelonGraph re-scored
  23. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  24. 2026-10-29 15:47 UTCEchelonGraph re-scored
  25. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  26. 2026-10-27 21:26 UTCEchelonGraph re-scored
  27. 2026-10-27 21:01 UTCENISA EUVD ID recordedEUVD-2026-111383 · Source: ENISA EUVD
  28. 2026-10-27 20:20 UTCEchelonGraph re-scoredFirst assessed: 9.8 CRITICAL
  29. 2026-10-27 20:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-116692?
CVE-2026-116692 is a critical-severity vulnerability; its CVE record was published on October 27, 2026. 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…
When was the CVE record for CVE-2026-116692 published?
The CVE record for CVE-2026-116692 was published on October 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 2, 2026; the record at its source may have been updated since.
Is CVE-2026-116692 actively exploited?
CVE-2026-116692 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-116692?
CVE-2026-116692 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-116692?
A fix for CVE-2026-116692 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-116692 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-116692

Explore →

Is Your Infrastructure Affected by CVE-2026-116692?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.