Quick answers
- Is CVE-2026-118623 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118623 being exploited in the wild.
- How severe is CVE-2026-118623?
- 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-118623?
- Yes: fixed in MLflow 3.13.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118623 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-118623?
- 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.13.0
Technical details
The vulnerability exists in MLflow's PickleEvaluationArtifact parser, which deserializes pickle files without validating the data source. An attacker can craft a malicious pickle file that executes arbitrary Python code during deserialization. User interaction is required (opening a malicious file or visiting a malicious page), but exploitation results in arbitrary code execution in the process context.
Affected products
- MLflow MLflow
Timeline
- 2026-03-25: disclosed: Vulnerability reported to vendor
- 2026-10-29: advisory: Coordinated public release of advisory