LiveActive security incident?Get immediate response
CVE Record

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.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-2614 lets an unauthenticated remote attacker read files from an affected MLflow server. If the server holds credentials, datasets, tokens, or configuration files, confidentiality impact can be serious. The provided sources say MLflow fixed the issue in version 3.10.0.

Executive priority

Treat this as a high-priority confidentiality risk for MLflow environments. Prioritize internet-exposed or shared MLflow servers first, because the described issue requires no authentication and can expose server-side files.

Technical view

In MLflow 3.9.0 and earlier, `_create_model_version()` can accept a prompt-related tag that bypasses source path validation. A local filesystem path can then be stored as a model version source. Later, `get_model_version_artifact_handler()` serves files from that source without rechecking prompt status, causing arbitrary file read.

Likely exposure

Organizations running MLflow servers at version 3.9.0 or earlier are potentially exposed, especially where model registry or artifact endpoints are reachable by unauthenticated or untrusted users. Exposure depends on endpoint accessibility and deployment controls.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. The vulnerability is remotely reachable, unauthenticated, low-complexity, and confidentiality-only under the supplied CVSS vector.

Researcher notes

Focus validation on the model version creation flow and artifact retrieval path described in the sources. Do not assume integrity or availability impact beyond the supplied CVSS vector. Evidence is sufficient for the core flaw and fix, but exploitation-in-the-wild evidence is not provided.

Mitigation direction

  • Upgrade MLflow to version 3.10.0 or later.
  • Restrict MLflow server access to trusted networks and authenticated users.
  • Review Red Hat advisories for packaged MLflow fixes if using Red Hat distributions.
  • Rotate secrets if sensitive local files may have been exposed.
  • Monitor model registry and artifact access logs for suspicious file-source behavior.

Validation and detection

  • Inventory MLflow deployments and confirm versions are above 3.9.0.
  • Verify model registry and artifact endpoints are not publicly exposed.
  • Review model version metadata for unexpected local filesystem source paths.
  • Check access logs for unusual artifact retrieval patterns.
  • Confirm vendor packages include the fix referenced by applicable advisories.
Prepared
Confidence
high
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-2614 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.0)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.0HighCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6@huntr_ai
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-2614Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPmlflow: mlflow: Arbitrary file read via bypassed source path validation
other:Red Hat severity ratingcvssV3_1
  • 2026-05-11T20:05:23.444Z: Reported to Red Hat.
  • 2026-05-11T19:02:46.025Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
mlflowmlflow/mlflowunspecifiedListed
Weakness

CWE details

CWE-22

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs