Quick answers
- Is CVE-2026-2614 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-2614 being exploited in the wild.
- How severe is CVE-2026-2614?
- High severity, with a CVSS score of 7.5, published 11 May 2026.
- Which products and versions are affected?
- mlflow (PyPI) < 3.10.0, ECOSYSTEM:introduced=0,fixed=3.10.0.
- Is there a fix for CVE-2026-2614?
- Yes. mlflow (PyPI): upgrade to 3.10.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-2614 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-2614?
- Check whether you run mlflow (PyPI) 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
- mlflow (PyPI): upgrade to 3.10.0 or later
pip install "mlflow>=3.10.0"
Technical details
A path traversal vulnerability exists in the `_create_model_version()` handler within `mlflow/server/handlers.py`. The vulnerability is triggered when a `CreateModelVersion` request includes the specific tag `mlflow.prompt.is_prompt`, which causes the server to bypass standard source path validation. An attacker can provide an arbitrary local filesystem path as the model version source. Subsequently, the `get_model_version_artifact_handler()` function serves files from this path without re-verifying the prompt status or path legitimacy. This allows unauthenticated remote attackers to retrieve any file accessible to the MLflow server process. The issue is resolved in version 3.10.0.
Affected products
- mlflow mlflow <= 3.9.0
Identifiers
- CVE-2026-2614
- GHSA-42h5-h8qh-vv9v
- PYSEC-2026-2654
Timeline
- 2026-05-11: advisory: NVD publication date
- 2026-05-11: disclosed: Initial disclosure via huntr.dev
- 2026-05-11: patched: Fix committed to MLflow repository