cve.bz

CVE-2026-116690 mlflow mlflow: Path traversal

7.5 highEPSS 1.8%Fix available

High (7.5) in mlflow mlflow. EPSS 1.8% estimated probability of exploitation activity in the next 30 days. Fixed in mlflow 3.17.0.

On this page
MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. From 3.10.0 until 3.17.0, the prompt branch in _create_model_version() accepts schemeless relative sources because path validation runs only when a source has a URL scheme, and mlflow.prompt.is_prompt is interpreted by tag presence rather than a true value. A remote caller can store a server-local path as the model version artifact location and use /api/2.0/mlflow/model-versions/get-artifact to read files accessible to the MLflow server process. Default unauthenticated servers require no privileges, while basic-auth deployments are exposed to authenticated users who can create registered models. This issue is fixed in version 3.17.0.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
1.8% (unchanged from 1.8% a week ago) estimated probability of exploitation activity in the next 30 days; 79th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • mlflow (PyPI): fixed in 3.17.0

Ask an AI about this CVE

Show the promptExplain CVE-2026-116690 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116690?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116690?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-116690 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
mlflow>= 3.10.0, < 3.17.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-m65p-9j7q-6w33PyPImlflow>=3.10.0 <3.17.03.17.0

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as an Important severity flaw because an attacker with network access to the MLflow tracking service can read arbitrary files from the server container without requiring administrative credentials. In Red Hat OpenShift AI (RHOAI), MLflow deployments that allow model registry interactions expose sensitive environment configuration, process memory files, or credential databases to any caller able to submit prompt-based model versions. The issue is confined to unauthorized information disclosure and does not provide an attacker with file modification capabilities or arbitrary code execution.

Red Hat's mitigation

--- CME Mitigation Guidance (2026-11-03) ---

Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to eliminate local filesystem path assignment in MLflow model registry creation by validating and restricting artifact sources to approved URI schemes: upgrade to MLflow 3.17.0 (or the corresponding fixed Red Hat builds), which reject schemeless sources for prompt model versions unless they match known internal placeholders, classify Windows drive paths using get_uri_scheme, and require the prompt tag value to explicitly equal 'true', closing all 4 injection vectors (schemeless relative paths, Windows drive-letter paths, directory traversal sequences, prompt tag manipulation). Until patched, this is a concern on MLflow tracking server deployments accessible over network, including unauthenticated servers and basic-auth environments allowing model version creation, so Restrict network access to the MLflow tracking server REST API, require authentication, restrict privileges to create registered model versions, and audit stored model versions for non-placeholder source paths. As a compensating measure, Restrict path characters and enforce an allowlist of permitted artifact URI schemes with default-deny to reject schemeless or local file references, Inspect inbound HTTP API requests using a web application firewall to detect and block directory traversal sequences and local path patterns sent to model version endpoints, Configure auditd to monitor and alert on unexpected system file read operations performed by the MLflow process, and Use Falco or eBPF runtime security to detect anomalous read access to sensitive filesystem locations initiated by the containerized MLflow server process. These controls limit blast radius and contain exploitation, but they do not fix the underlying improper path validation defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-1301 Path Traversal Prevention (Canonicalization) (high)

ProductPackageStateAdvisory
Red Hat OpenShift AI (RHOAI)rhoai/odh-mlflow-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-datascience-cpu-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-pytorch-cuda-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-pytorch-llmcompressor-cuda-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-pytorch-rocm-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-tensorflow-cuda-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-tensorflow-rocm-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-th06-cpu-torch210-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-th06-cuda130-torch210-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-th06-rocm64-torch291-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-th-torch-cpu-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-th-torch-cuda-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-th-torch-rocm-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-training-cuda128-torch29-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-datascience-cpu-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-pytorch-cuda-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-pytorch-llmcompressor-cuda-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-pytorch-rocm-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-tensorflow-cuda-py312-rhel9Affected
2 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-116690.

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON