CVE-2026-2614 — Arbitrary File Read via Prompt Tag Source Validation Bypass in mlflow/mlflow
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Public exploit/PoC (nuclei)+4
- EPSS 3.2% (30-day exploitation probability)+13
- Technical severity (high)+6
- CISA SSVC: exploitation "poc"+5
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — github.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Lfprojects Mlflow, Mlflow Mlflow).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Lfprojects | Mlflow | < 3.10.0 | Vulnerable | NIST National Vulnerability Database |
| Mlflow | Mlflow | < 3.10.0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.5 | CVSS 3.1 | High | 3.9 | 3.6 | 0b0ca135-0b70-47e7-9f44-1890c2a1c46c via NIST National Vulnerability Database |
| 7.5 | CVSS 3.0 | High | 3.9 | 3.6 | security@huntr.dev via NIST National Vulnerability Database |
| 7.5 | CVSS 3.0 | High | — | — | @huntr_ai via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (score shown at the top: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Public exploits, PoCs and detection templates
Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.
Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 3.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Monitor file creation in web directories and paths with traversal sequences (../).
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · mlflow/mlflow/mlflow
- SSVC assessment updated
- Record published
- Fix documented
- CVSS changed · 7.5
- Source status changed · → Modified
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
8 on the record
- github.com/mlflow/mlflow/commit/6e801f4259d96804c73107315b24cef0f6aa115a
- access.redhat.com/errata/RHSA-2026:37275
- bugzilla.redhat.com/show_bug.cgi
- access.redhat.com/errata/RHSA-2026:60520
- access.redhat.com/errata/RHSA-2026:34456
- access.redhat.com/security/cve/CVE-2026-2614
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-2614.json
- huntr.com/bounties/19380271-3fbf-4beb-987e-6fd7069c55e6
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-79721 Code execution can occur in versions of the MLflow platform running version 0.0.1 or… Sep 8, 2026
- High CVE-2026-69148 MLflow: CreateModelVersion source validation does not check READ permission on referenced run_id Aug 17, 2026
- Medium CVE-2026-69146 MLflow: LogInputs endpoint bypasses per-run UPDATE authorization in basic-auth Aug 17, 2026
- Critical CVE-2026-64849 MLflow Server-Side Request Forgery Vulnerability KEV Aug 17, 2026
- High CVE-2026-71211 mlflow - Unvalidated Gateway Secret api_base Enables SSRF via Gateway Proxy Endpoint Aug 5, 2026
- High CVE-2026-8147 Authorization Bypass in mlflow/mlflow Jul 2, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-2614 is "Arbitrary File Read via Prompt Tag Source Validation Bypass in mlflow/mlflow", rated High. It affects Mlflow (Lfprojects); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. EPSS 3.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.