CVE-2026-118625
Exploitation: none CVSS 6.3 MEDIUMCVSS base score: 6.3 (Medium) vendor CNA · v3.0
Score assigned by the vendor's own CVE Numbering Authority (CNA); CISA's Vulnrichment program adds a score only when the CNA omits one. Vulnrichment source record → (opens in a new tab)
Vendor: MLflow Product: MLflow
Description
MLflow Tracking Server Missing Authorization Privilege Escalation Vulnerability. This vulnerability allows remote attackers to escalate privileges on affected installations of MLflow. Authentication is required to exploit this vulnerability. The specific flaw exists within the get_endpoints function. The issue results from the lack of authorization prior to allowing access to functionality. An attacker can leverage this vulnerability to escalate privileges to resources normally protected from the user. Was ZDI-CAN-32107.
Research & News Coverage
| Date | Source | Article |
|---|---|---|
| 2026-10-29 | Trend Micro ZDI | ZDI-26-841: MLflow Tracking Server Missing Authorization Privilege Escalation Vulnerability (opens in a new tab) |
Articles from monitored vendor research blogs and security news feeds that specifically mention this CVE. Coverage begins when feed monitoring started; earlier articles are not indexed.
Lifecycle Timeline
-
2026-11-03
-
not recordedPublic exploit codeNo dated exploit found in Metasploit, Exploit-DB or public GitHub repositories.
-
not recordedEPSS flags exploitation riskTracked, and has never reached 10% (peak 0.3%).
-
not recordedFirst national advisoryNo tracked government advisory analyses this CVE. Routine KEV catalog-addition alerts do not count here.
-
not recordedAdded to CISA KEVNot in the CISA KEV catalog.
-
not recordedFederal remediation dueNo remediation deadline set.
-
not recordedVendor fix publishedNo dated vendor fix. Only Microsoft publishes a machine-readable release date; other vendors state a fixed version without one.
Each milestone comes from a different source, so gaps between them are gaps in what those sources publish, not evidence that nothing happened. EPSS history for this CVE holds 10 points from 2026-11-04, tracked daily from 2026-11-04; earlier points are weekly, which dates a spike to within a week. Peak probability 0.3% on 2026-11-04.
Published Applicability
Check whether a specific version is affected →
What each source publishes about which product versions carry this vulnerability, kept as written rather than merged. Absence here means no source has published applicability data, not that nothing is affected.
Detection & Exploitation
Blind spot. No public detection — verify by version/patch. Nothing in the monitored scanner, IDS, SIEM or offensive-tool collections references this CVE, so exposure has to be established from asset inventory and patch level rather than from a signature.
Coverage across public collections only: Nuclei and OpenVAS NVT (scan);
Snort and Suricata ET Open (network); Sigma and YARA (host/SIEM);
Metasploit, Exploit-DB, public GitHub repositories and NVD exploit references (exploit). Absence
here means nothing public was found, not that detection is impossible.
GitHub PoC repositories are collected automatically by
PoC-in-GitHub (opens in a new tab) (CC0) and filtered to repositories that are
still online, contain code, and are starred or at least two weeks old. They are
still not vetted: some are fakes and some are malware. Treat
them as evidence that code was published, not as code to run.
NVD exploit references are links NVD's analysts tag as exploits; they confirm
an exploit was referenced but carry no date. This product uses data from the
NVD but is not endorsed or certified by the NVD.
OpenVAS coverage derives from the Greenbone Community Feed, made available
under the Open Database License (ODbL) v1.0 (opens in a new tab);
its individual Vulnerability Tests are licensed
GNU GPL v2 (opens in a new tab).
No exploit-tool sightings recorded for this CVE.
Metasploit is dated by the first commit of the module file, Exploit-DB by its publication date, and GitHub repositories by their creation date. GitHub PoC repositories are filtered (still online, contain code, starred or at least two weeks old) but not vetted: some are fakes and some are malware, so they show that code was published, not that it works or is safe to run. Evidence tiers are explained on the About page.
CISA Assessment (Vulnrichment / SSVC)
Federal Remediation Window (BOD 26-04)
| If the asset is | Remediate within | Table 1 row |
|---|---|---|
| Publicly exposed | 14 days | 7 of 16 |
| Not publicly exposed | Fix on system upgrade | 15 of 16 |
BOD 26-04 (opens in a new tab) replaced the single KEV deadline of BOD 22-01 with four inputs: whether the asset is publicly exposed, KEV status, whether exploitation is automatable, and technical impact. Exposure belongs to each agency's asset, not to the CVE, so both outcomes are shown. Automatable and technical impact come from the CISA assessment above. Days are calendar days; for KEV entries the clock starts on the date it was added, and otherwise when the agency identifies the vulnerability on an asset. Agencies make the final exposure call asset by asset, and may set shorter timelines.