CVE-2026-118760

Kubeflow Pipelines: Missing namespace authorization permits cross-tenant artifact reads

Published Oct 29, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Kubeflow Pipelines suffers from a missing namespace authorization check in its frontend artifact routes. From version 0.5.1 up to 2.17.0, any authenticated user who can reach the frontend and knows the artifact location can specify an arbitrary namespace or omit the namespace entirely. This allows the user to read artifact contents—including datasets, trained models, or pipeline outputs—belonging to other tenants. The vulnerability does not grant access to Kubernetes Secrets, write capabilities, or server‑side code execution; it is strictly a data disclosure flaw.

Affected Systems

The affected product is Kubeflow Pipelines, with all releases from 0.5.1 through 2.17.0 installed in a multi‑user configuration. Deployments that rely on Kubeflow’s built‑in tenant isolation are susceptible. Version 2.17.0 contains the fix and is the earliest patched release.

Risk and Exploitability

The CVSS score of 6.5 reflects moderate complexity; the EPSS score is not provided, and the issue is not listed in CISA KEV. The attack requires only that the attacker be an authenticated user who can reach the frontend and possess knowledge of an artifact URI. The attacker can then craft a request with a different namespace or no namespace to retrieve the artifact, thereby compromising confidentiality across tenants.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Kubeflow Pipelines to version 2.17.0 or later, which implements proper namespace authorization checks.
  • Configure RBAC in Kubeflow to strictly limit which namespaces each user or service account may access, ensuring that namespace visibility is enforced beyond the frontend.
  • Apply network policies or ingress controls that restrict access to the Kubeflow Pipelines frontend to only trusted sources, reducing the attack surface for unauthenticated or unintended users.

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

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', '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. 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.
Title Kubeflow Pipelines: Missing namespace authorization permits cross-tenant artifact reads
Weaknesses CWE-639
CWE-862
References
Metrics cvssV3_1

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

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

  • CWE-862

    Missing Authorization

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 3, 2026, 4:03 PM
Reserved
Oct 28, 2026, 7:20 PM
Status
Awaiting Analysis
Published
Oct 29, 2026, 5:18 PM
Modified
Nov 3, 2026, 5:17 PM