How severe is CVE-2026-2614?

CVE-2026-2614 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-2614?

CVE-2026-2614 affects the following packages: mlflow (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2026-2614?

Update mlflow to 3.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-2614 is resolved across your whole dependency graph.

How do I detect CVE-2026-2614 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mlflow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-2614 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2026-2614 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-2614 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-2614?

CVE-2026-2614 has an EPSS (Exploit Prediction Scoring System) score of 3.6%, placing it in the 90th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-2614?

CVE-2026-2614 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2026-2614?

A Nuclei detection template exists for CVE-2026-2614, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2026-2614 published, and has it been updated?

CVE-2026-2614 was published on May 11, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

HIGH severity

CVE-2026-2614 — mlflow

HIGHFix: mlflow/mlflow@6e801f4

CVE-2026-2614 is a high-severity (CVSS 7.5) Path Traversal vulnerability in mlflow. A fix is available for mlflow — see the affected versions and patch details below.

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

Also known asBIT-mlflow-2026-2614GHSA-42h5-h8qh-vv9vPYSEC-2026-2654

Published

May 11, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-2614.

EPSS Exploitation Probability

via FIRST.org ↗

3.6%probability of exploitation in next 30 days

Lower Risk-0.06%

Lower risk than most CVEs90th percentile — riskier than 90% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐍mlflow

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`mlflow`	all versions	3.10.0`pip install --upgrade 'mlflow==3.10.0'`

Affected Products

1 product · 1 configurations

Application

mlflowlfprojects

< 3.10.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mlflow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mlflow to 3.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-2614 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

How to detect CVE-2026-2614

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2026-2614 -u https://target

Template: MLflow <= 3.9.0 - Arbitrary File Read
Severity: high
Impact: Unauthenticated attackers can read arbitrary files on the server, leading to complete confidentiality compromise.
Remediation: Upgrade to version 3.10.0 or later.

Template by ProjectDiscovery nuclei-templates (str4k3r), MIT licensed. View the full template. Scan only systems you are authorised to test.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This Important vulnerability in mlflow allows an unauthenticated remote attacker to read arbitrary files from the server's filesystem. The flaw exists in the `_create_model_version()` handler, where a specially crafted request with the `mlflow.prompt.is_prompt` tag bypasses source path validation. This enables an…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for CVE-2026-2614 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat OpenShift AI 3.3	`rhoai/odh-training-cuda128-torch29-py312-rhel9:1782991170`	RHSA-2026:37275
Red Hat OpenShift AI 3.4	`rhoai/odh-th06-cpu-torch210-py312-rhel9:1782135464`	RHSA-2026:34456
Red Hat OpenShift AI 3.4	`rhoai/odh-pipeline-runtime-datascience-cpu-py312-rhel9:1787073866`	RHSA-2026:60520

Frequently Asked Questions

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 sta

O3 Security · Impact-Aware SCA

Is CVE-2026-2614 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works