GPU VulnDB

Database/Control plane, storage & DevOps

OpsTree BuildPiper: unrestricted Additional Manifests let project users gain Kubernetes cluster-admin

CVSS 9.4CVE-2026-127073Control plane, storage & DevOpscurated

Impact

BuildPiper applies manifests submitted through its Additional Manifest feature with the pipeline's cluster-wide credentials and does not restrict which kinds of object they contain. A project-level user can submit a ClusterRoleBinding that binds a service account they control to cluster-admin. That gives them every workload and every Secret in the cluster, including other teams' namespaces. On a shared GPU cluster that means one project user can read or take over every tenant's jobs, model weights and credentials.

Who can reach it

An authenticated BuildPiper project user who can use the Additional Manifest feature. Login is required, but no cluster RBAC rights are needed beyond what BuildPiper's own credentials carry.

What to do

Upgrade BuildPiper to 2.7.0 or later. The record does not describe a workaround. Until you upgrade, reduce the RBAC held by the credentials BuildPiper deploys with, or block cluster-scoped RBAC objects with admission policy. After upgrading, check for ClusterRoleBindings or RoleBindings to cluster-admin created through the pipeline, and rotate the cluster Secrets if any exist.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.