CVE-2026-118758

Kubeflow: Unauthenticated path traversal to arbitrary file read on ml-pipeline-ui via the volume artifact source

Published Oct 29, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.18.0, the volume artifact handler for GET /artifacts/get?source=volume did not confine a caller-supplied file path to the selected volume. A caller who can reach the route and identify an existing mounted volume can use path traversal to read files outside that volume when the artifact-serving process can read them. The frontend pod serves the request when artifact proxying is disabled, while the selected namespace's artifact-service pod serves it when proxying is enabled. A deployment with authentication disabled requires no application credentials; in multi-user deployments, the caller ordinarily must be authorized for the supplied namespace. This issue is fixed in version 2.18.0.

Analysis

AI-generated

Technical impact

Kubeflow Pipelines prior to version 2.18.0 exposed a path traversal flaw in the volume artifact request handler. An attacker who can reach the GET /artifacts/get?source=volume endpoint can supply a crafted file path that is not confined to the intended volume, causing the artifact service to read and return the contents of any file visible to the process. This flaw (CWE‑22) lets an unauthenticated or minimally privileged user read arbitrary files on the hosting node or pod, potentially exposing sensitive configuration or credential data.

Affected Systems

The vulnerability affects the Kubeflow Pipelines product across all releases preceding 2.18.0. Deployments running an older version, especially those with authentication disabled or default ingress settings that expose the artifact endpoint to external traffic, are susceptible.

Risk and Exploitability

The CVSS score of 7.5 indicates a high risk when authentication and authorization are bypassed. Because the exploit requires only a simple HTTP request to the exposed endpoint, and authentication can be absent in some deployments, the attack surface is broad. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog, suggesting no widespread active exploitation yet; however, attackers with network access to the cluster can trigger the path traversal and retrieve arbitrary files, making this a significant threat in multi‑user or poorly secured environments.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Kubeflow Pipelines to at least version 2.18.0, which fixes the path traversal in the volume artifact handler.
  • If an immediate upgrade is not possible, restrict or disable external access to the /artifacts/get?source=volume endpoint by applying network policies or adjusting the Ingress configuration to prevent unauthenticated requests.
  • Enable authentication and enforce namespace‑level authorization for the artifact service so that only authorized users can reach the vulnerable endpoint and read files.

Generated by OpenCVE AI on October 29, 2026 at 17:28 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Kubeflow
Kubeflow pipelines
Vendors & Products Kubeflow
Kubeflow pipelines
Type Values Removed Values Added
Description Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.18.0, the volume artifact handler for GET /artifacts/get?source=volume did not confine a caller-supplied file path to the selected volume. A caller who can reach the route and identify an existing mounted volume can use path traversal to read files outside that volume when the artifact-serving process can read them. The frontend pod serves the request when artifact proxying is disabled, while the selected namespace's artifact-service pod serves it when proxying is enabled. A deployment with authentication disabled requires no application credentials; in multi-user deployments, the caller ordinarily must be authorized for the supplied namespace. This issue is fixed in version 2.18.0.
Title Kubeflow: Unauthenticated path traversal to arbitrary file read on ml-pipeline-ui via the volume artifact source
Weaknesses CWE-22
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}

Weaknesses
  • CWE-22

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

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 29, 2026, 8:18 PM
Reserved
Oct 28, 2026, 7:20 PM
Status
Awaiting Analysis
Published
Oct 29, 2026, 5:18 PM
Modified
Oct 30, 2026, 5:18 PM