Quick answers
- Is CVE-2026-118625 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118625 being exploited in the wild.
- How severe is CVE-2026-118625?
- Medium severity, with a CVSS score of 6.3, published 4 November 2026.
- Which products and versions are affected?
- MLflow MLflow.
- Is there a fix for CVE-2026-118625?
- 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-118625 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-118625?
- Check whether you run Mlflow. 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 MLflow's get_endpoints function, which fails to perform authorization checks before exposing functionality to authenticated users. An attacker with valid authentication credentials can exploit this missing authorization to escalate privileges and access protected resources. The issue requires authentication but no user interaction, and can be exploited remotely over the network.
Affected products
- MLflow MLflow
Timeline
- 2026-06-30: disclosed: Vulnerability reported to vendor
- 2026-10-29: patched: Fixed in MLflow 3.16.0
- 2026-10-29: advisory: Coordinated public release of advisory