CVE-2026-118626: MLflow Tracking Server Issues Missing Authorization Privilege Escalation Vulnerability
Source GCVE Database
Not known to be exploited · CVSS 5.4 Medium.
Data as of 4 Nov 2026, 02:00 UTC
Thin evidence
One scorer or none| CNA (zdi) | CVSS 3.0 | 5.4 |
|---|
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MLflowMLflow | Affected
| Fixed in– |
AI-suggested
Until a fix is released, restrict access to the MLflow Tracking Server to trusted users only and monitor for unusual privilege escalation attempts.
Description
A privilege escalation vulnerability exists in MLflow Tracking Server due to missing authorization checks in the BEFORE_REQUEST_HANDLERS configuration. Exploitation requires authentication and allows attackers to gain elevated privileges to access normally protected resources.