Quick answers
- Is CVE-2026-118627 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118627 being exploited in the wild.
- How severe is CVE-2026-118627?
- High severity, with a CVSS score of 7.8, published 4 November 2026.
- Which products and versions are affected?
- MLflow MLflow.
- Is there a fix for CVE-2026-118627?
- Yes: fixed in MLflow 3.17.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118627 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-118627?
- 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.17.0
Technical details
The vulnerability exists in MLflow's SHAP load_explainer functionality, where insufficient validation of user-supplied data permits deserialization of untrusted objects. An attacker can craft a malicious SHAP explainer model file that executes arbitrary code when deserialized. User interaction is required: the victim must visit a crafted page or open a malicious file.
Affected products
- MLflow MLflow
Timeline
- 2026-04-15: disclosed: Vulnerability reported to vendor
- 2026-10-29: advisory: Coordinated public release of advisory
- 2026-10-29: patched: Fixed in MLflow 3.17.0