CVE Tools

CVE-2026-2614

Arbitrary File Read via Prompt Tag Source Validation Bypass in mlflow/mlflow

CVE-2026-2614 is a path traversal in Mlflow Mlflow/mlflow (CVSS 7.5, High).

No known exploitation. EPSS puts it in the 90th percentile. Fixed in 3.10.0.

Check it yourself

Nuclei · 1 templateOpenVAS · 1 check

e.g. MLflow <= 3.9.0 - Arbitrary File Read · OID 1.3.6.1.4.1.25623.1.0.180059

Run the check

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • Mlflow/mlflowAffected: ≥ unspecified, < 3.10.0Upgrade to: 3.10.0Stated by: CVE record
  • Lfprojects MlflowAffected: < 3.10.0Upgrade to: 3.10.0Stated by: NVD

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

A vulnerability in the `_create_model_version()` handler of `mlflow/server/handlers.py` in mlflow/mlflow versions 3.9.0 and earlier allows an unauthenticated remote attacker to read arbitrary files from the server's filesystem. The issue arises when a `CreateModelVersion` request includes the tag `mlflow.prompt.is_prompt`, which bypasses source path validation. This enables an attacker to store an arbitrary local filesystem path as the model version source. The `get_model_version_artifact_handler()` function later uses this source to serve files without verifying the model version's prompt status, leading to a complete confidentiality compromise. This issue is fixed in version 3.10.0.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS90th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

3.6% chance of exploitation activity in the next 30 days, which ranks it in the 90th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

15 events over 184 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Patch availablerecord updated
  3. Nuclei check added
  4. Patch availablerecord updated
  5. Patch availablerecord updated
  6. Patch availablerecord updated

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Scored 7.5 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity NoneNo integrity impact
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Questions about CVE-2026-2614

Is CVE-2026-2614 being exploited?
No exploitation is confirmed and no public exploit is known. EPSS puts the chance of exploitation in the next 30 days at 3.6%.
Which versions are affected by CVE-2026-2614?
Mlflow/mlflow: ≥ unspecified, < 3.10.0. Mlflow: < 3.10.0.
How do I fix or mitigate CVE-2026-2614?
Upgrade to 3.10.0 or later. The advisory is on access.redhat.com.

Last updated

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Mlflow/mlflow, not every advisory.