EM-20261103-UZ0V
VulnerabilityMedium severity
mlflow Vulnerability (CVE-2026-118626)
CVE-2026-118626
Status
Developing
Since : signals keep joining.
- First Signal
- Oct 29 05:00 UTCC37 Zero Day Initiative (published)
- Page Born
- Nov 03 23:45 UTCsecond source joined
- Last Signal
- Nov 03 23:45 UTC14 hours before snapshot
- Sources
- 21 official · 1 research, news or crowd
- Open For
- 6 daysso far
Life Of This Page
- 1BornA second, independent source names it.
- 2Developing · NowNew signals join; severity can move.
- 3ConfirmedNot yetCISA KEV lists it, or exploitation in the wild is reported.
- 4ResolvedNot yetPast the fix deadline and 14 days with no new signal.
- 5ArchivedNot yet30 days after resolved. Read only; the link keeps working. Reopens if it comes back.
The address and ID never change. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.
Vulnerability Lifecycle
- Disclosed: reachedOct 29 05:00 UTCC37 first to name it
- Scored: not yetNot yetNo CVSS yet
- Exploited: not yetNot yetNo exploitation reported
- Advisories: not yetNot yetNone yet
- Vendor Response: reachedNov 03 23:45 UTCC41 published
- Resolved: not yetNot yetAfter 14 quiet days
Timeline
Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.
Signals
- Red Hat: CVE-2026-118626 (moderate) (opens source in a new tab) mlflow: mlflow: Privilege escalation via missing authorization in request handlers Med severityVendorC41 Red Hat Security Data
- ZDI-26-842: MLflow Tracking Server I ue Mi ing Authorization Privilege E calation Vulnerability (opens source in a new tab) This vulnerability allows remote attackers to escalate privileges on affected installations of MLflow. Authentication is required to exploit this vulnerability. The ZDI has assigned a CVSS rating of 5.4. The following CV… Med severityResearch & NewsC37 Zero Day Initiative (published)