Skip to main content
VulnerabilityPublished

CVE-2026-118626: MLflow Tracking Server Issues Missing Authorization Privilege Escalation Vulnerability

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-118626· Medium 5.4

Not known to be exploited · CVSS 5.4 Medium.

Data as of 4 Nov 2026, 02:00 UTC

CVSS 3.0 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (zdi)CVSS 3.05.4
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
MLflowMLflowAffected
  • =3.14.0
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.

References

Community reviews

Loading reviews…