GPU VulnDB

Database/AI/ML frameworks & serving

Kubeflow Pipelines: any authenticated user can modify or delete shared pipelines without RBAC

CVSS 7.2CVE-2026-88984AI/ML frameworks & servingcurated

Impact

In a multi-user Kubeflow install, the API server treats the empty namespace that marks shared or global pipelines as an authorization exception on write paths. Any authenticated user - a data scientist with a single namespace, not a cluster admin - can edit or delete the shared pipeline definitions and versions that other teams run, which breaks integrity and availability of the fleet's training and inference workflows. Because a modified pipeline is later executed by whoever runs it, a tampered definition becomes code running on GPU nodes under someone else's service account. Read access to shared pipelines is intentional and single-user deployments intentionally skip the multi-user checks, so only multi-user clusters are exposed.

Who can reach it

Any authenticated Kubeflow user with access to the multi-user API server. No cluster-level RBAC permission on the shared namespace is needed - that is the bug.

What to do

Upgrade Kubeflow Pipelines to 2.16.1 and restart the API server deployment; no node drain or GPU downtime is involved. Note that the advisory explicitly leaves the shared-pipeline multipart upload authorization path unfixed in 2.16.1, so continue to restrict who can reach that endpoint.

References

Related entries

All AI/ML frameworks & serving 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.