CVE-2026-69129: KubePi: Insufficient per-cluster authorization checks in cluster management APIs
KubePi is a Kubernetes multi-cluster management panel. In versions up to and including 2.0.0, cluster-scoped APIs do not consistently validate per-cluster access, allowing an authenticated user with cluster management permissions to operate on clusters outside the scope they were granted. Because the affected endpoints act on cluster-specific data without confirming that the requesting user is authorized for that particular cluster, a user assigned management rights over one cluster can, under certain role and cluster configurations, read or modify data in clusters they should not manage. This issue is fixed in version 2.0.1.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
KubePito a version that resolves this vulnerability.Fixed in 2.0.1
Event History
Frequently Asked Questions
Who can exploit this issue?
An authenticated user who has cluster management permissions can exploit it. The user must have management rights over at least one cluster, and exposure depends on the configured roles and cluster assignments.
What could an unauthorized user do?
They may be able to read or modify cluster-specific data for clusters outside the scope they were granted. The affected APIs do not consistently verify authorization for the particular cluster being accessed.
Which versions are affected and what fixes the issue?
KubePi versions up to and including 2.0.0 are affected. Upgrade to version 2.0.1, which fixes the authorization checks.