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


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-2fg9-fx2f-439r

## What is CVE-2026-118758?

CVE-2026-118758 is a high-severity vulnerability in kubeflow pipelines, published on 29 Oct 2026. 

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

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-118758?


## How do I fix CVE-2026-118758?

No fix has been published for CVE-2026-118758 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-118758 being exploited?

There is no known exploitation of CVE-2026-118758 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-118758 and fix it if it is affected.

What it is: CVE-2026-118758 is a high-severity vulnerability in kubeflow pipelines, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118758 in the wild and no public exploit code.

Affected product: kubeflow pipelines. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-118758/ (Markdown: https://insights.sbomify.com/CVE-2026-118758/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-118758
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-118758
- OSV: https://osv.dev/vulnerability/CVE-2026-118758

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-118758/
Summaries are generated and may contain mistakes; the official description above is the record.