Live › vulnerability › CVE-2026-118760
Kubeflow Pipelines versions from 0.5.1 through 2.16.x do not check namespace authorization on frontend artifact routes. A signed-in user who knows an artifact location can read datasets, models or pipeline outputs belonging to another tenant.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 17:26 UTC. All times on this page are UTC.
Teams running multi-user Kubeflow Pipelines that depend on its authorization to separate tenants. Single-tenant deployments, and deployments where ingress authentication is the only isolation, are the exposed case. The sources do not say which exact deployment modes are unaffected beyond that.
No product ranges from the sources yet.
unknown for the exact command, the sources do not say2.17.0Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-118760")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.