---
id: "CVE-2026-118758"
kind: "vulnerability"
aliases: ["CVE-2026-118758"]
title: "Kubeflow Pipelines: artifact route path traversal reads files outside volumes"
severity: "high"
cvss: 7.5
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["kubeflow", "kubernetes", "machine-learning", "package", "self-hosted"]
not_affected_if: ["auth-required", "namespace-authorization-enforced", "version-2.18.0-or-later"]
published_at: "2026-10-29T17:18:06+00:00"
first_seen_at: "2026-10-29T17:26:17+00:00"
updated_at: "2026-10-29T17:27:52+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-118758", "first_seen_at": "2026-10-29T17:26:17+00:00"}]
---

# Kubeflow Pipelines: artifact route path traversal reads files outside volumes

Kubeflow Pipelines before 2.18.0 does not confine file paths requested through the GET /artifacts/get volume handler. An attacker who can reach that route and name an existing mounted volume can read files outside that volume, as far as the artifact-serving process can read them.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Kubeflow Pipelines version; affected if it is below `2.18.0`.
- Check whether artifact proxying is enabled in the deployment; the frontend pod or the namespace's artifact-service pod serves the route depending on that setting.
- Check whether authentication is disabled or the route is reachable from untrusted callers.

## Fix

- Kubeflow Pipelines: move to `2.18.0` or later.

## Timeline

- 2026-10-29T17:26:17+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-118758

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_