# CVE-2026-118760: Kubeflow Pipelines: Missing namespace authorization permits cross-tenant artifact reads


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/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-vjhf-6c8f-qhwj

## What is CVE-2026-118760?

CVE-2026-118760 is a medium-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. From 0.5.1 until 2.17.0, the frontend artifact routes did not check whether an authenticated user was authorized to access the requested namespace. A user who can reach the frontend and knows an artifact location can select another tenant's namespace, or omit the namespace and reach an unguarded direct handler, to read artifact contents such as datasets, models, or pipeline outputs. The issue applies to multi-user deployments that rely on Kubeflow Pipelines authorization for tenant isolation. Authentication at ingress identifies the caller but does not authorize access to the selected artifact namespace. The issue does not establish arbitrary Kubernetes Secret disclosure, storage modification, or server-side code execution. This issue is fixed in version 2.17.0.

Weakness: CWE-862 (Missing Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-118760 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-118760 is a medium-severity vulnerability in kubeflow pipelines, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118760 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-118760/ (Markdown: https://insights.sbomify.com/CVE-2026-118760/index.md)
```

## Sources

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

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