Quick answers
- Is CVE-2026-118628 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118628 being exploited in the wild.
- How severe is CVE-2026-118628?
- High severity, with a CVSS score of 8.2, published 4 November 2026.
- Which products and versions are affected?
- Mlflow prior to 3.17.0.
- Is there a fix for CVE-2026-118628?
- 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-118628 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-118628?
- Check whether you run Mlflow at an affected version. 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 get-artifacts function in MLflow fails to properly validate URIs before accessing resources, enabling a server-side request forgery (SSRF) attack. An unauthenticated attacker can exploit this over the network without user interaction to read arbitrary files or data accessible to the MLflow server process, resulting in information disclosure with partial integrity impact.
Affected products
- MLflow MLflow prior to 3.17.0
Timeline
- 2026-02-05: disclosed: Vulnerability reported to vendor
- 2026-10-29: advisory: Coordinated public release of advisory