Quick answers
- Is CVE-2026-118626 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118626 being exploited in the wild.
- How severe is CVE-2026-118626?
- Medium severity, with a CVSS score of 5.4, published 4 November 2026.
- Which products and versions are affected?
- MLflow MLflow Tracking Server.
- Is there a fix for CVE-2026-118626?
- Yes: fixed in MLflow 3.16.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118626 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-118626?
- Check whether you run MLflow Tracking Server. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: MLflow 3.16.0
Technical details
The vulnerability exists in the configuration of BEFORE_REQUEST_HANDLERS, where lack of authorization checks allows authenticated attackers to bypass access controls and escalate privileges. An attacker with valid credentials can leverage this flaw to access resources normally protected from their user role. The issue has been fixed in MLflow 3.16.0.
Affected products
- MLflow MLflow Tracking Server
Timeline
- 2026-06-30: disclosed: Vulnerability reported to vendor
- 2026-10-29: advisory: Coordinated public release of advisory