Read the docs
TI-2026-82674 Aliases CVE-2026-118760

Kubeflow Pipelines lets users read other tenants' artifacts

Priority LOW 29CWE-639Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-639.

Summary

Kubeflow Pipelines from 0.5.1 before 2.17.0 has frontend artifact routes that do not check whether an authenticated user is authorized for the requested namespace. A user with low privileges who can reach the frontend and knows an artifact location can select another tenant's namespace to read artifacts such as datasets, models, or pipeline outputs, which is a missing authorization flaw (CWE-862). The flaw affects multi-user deployments that rely on Kubeflow Pipelines authorization for tenant isolation, because ingress authentication identifies the caller but does not authorize the artifact namespace.

Written with Claude Haiku 5.5 from the sources below · 2026-11-03

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00352 29th percentileScored 2026-11-07
Fix Fixed pipelines (kubeflow): 2.17.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
kubeflowpipelinesbefore 2.17.02.17.0Patch availableCNA
  • pipelines Vendorkubeflow Affected before 2.17.0 Fixed in 2.17.0 Patch available CNA

Remediation

Kubeflow Pipelines version 2.17.0 fixes this issue, so upgrade to 2.17.0 or later.

Written with Claude Haiku 5.5 from the sources below · 2026-11-03

  • Fix · CNA pipelines (kubeflow) Fixed in 2.17.0

Timeline

  1. 2026-10-29 Threatist record created from CVE-2026-118760
  2. 2026-10-31 Priority changed: MEDIUM → LOW
  3. 2026-11-03 CISA SSVC decision points changed

References

Other 5

  • TI-2026-39556 Improper access control in kubeflow pipelines CVSS 3.1CRITICAL 10.0
  • TI-2024-05160 ReDoS in kubeflow/kubeflow CVSS 3.1HIGH 7.5
  • TI-2026-34822 Kubeflow Community Distribution: Overly Permissive Istio Permissions Allows Kubeflow Authorization Token Stealing CVSS 3.1HIGH 8.0
  • TI-2026-85696 Server-side request forgery in Kubeflow Pipelines TensorBoard proxy CVSS 3.1MEDIUM 5.8
  • TI-2026-73437 Server-side request forgery in Kubeflow Model Registry leaks tokens CVSS 4.0HIGH 7.1
  • TI-2026-85698 Server-side request forgery in Kubeflow Pipelines artifact endpoints CVSS 3.1HIGH 8.6
See all 19 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences