Quick answers
- Is CVE-2026-118624 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118624 being exploited in the wild.
- How severe is CVE-2026-118624?
- Medium severity, with a CVSS score of 5.4, published 4 November 2026.
- Which products and versions are affected?
- MLflow MLflow.
- Is there a fix for CVE-2026-118624?
- 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-118624 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-118624?
- 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 _find_validator function in MLflow Tracking Server lacks proper authorization checks, allowing authenticated attackers to access restricted functionality. The vulnerability requires prior authentication but permits disclosure of information in the context of the service account. An attacker can leverage this to read sensitive data they are not authorized to access.
Affected products
- MLflow MLflow
Timeline
- 2026-06-18: disclosed: Vulnerability reported to vendor
- 2026-10-29: advisory: Coordinated public release of advisory
- 2026-10-29: patched: Fix available in MLflow 3.16.0