CVE-2026-69129

KubePi: Insufficient per-cluster authorization checks in cluster management APIs

Published Aug 26, 2026 CVSS 4.0 · 5.8 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

In KubePi versions up to and including 2.0.0, the cluster‑scoped APIs fail to validate per‑cluster access, allowing an authenticated user with cluster‑management permissions to read or modify data in clusters outside the set of clusters they are authorized to manage. This privilege escalation flaw enables unauthorized access to cluster data, which can lead to data leakage or unauthorized configuration changes.

Affected Systems

Affected product: KubePi by 1Panel‑dev. Vulnerable versions are 2.0.0 and earlier; the issue was resolved in version 2.0.1.

Risk and Exploitability

The CVSS base score is 5.8, indicating moderate severity, and EPSS is not available, but the flaw requires authenticated access and is not listed in the CISA KEV catalog. An attacker with valid cluster management credentials could exploit the missing per‑cluster checks to manipulate or read data in other clusters, especially if role assignments overlap. Upgrading to a fixed version mitigates the risk, but the absence of a high‑probability EPSS score suggests exploitation is possible but not likely in widespread attacks at this time.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade KubePi to version 2.0.1 or later to apply the fix.
  • Review and tighten cluster‑management roles so users have permissions only for the clusters they should manage.
  • Re‑validate the RBAC policy and monitor logs for unintended cross‑cluster actions.

Generated by OpenCVE AI on August 27, 2026 at 00:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared 1panel Dev
1panel Dev kubepi
Vendors & Products 1panel Dev
1panel Dev kubepi
Type Values Removed Values Added
Description 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.
Title KubePi: Insufficient per-cluster authorization checks in cluster management APIs
Weaknesses CWE-639
References
Metrics cvssV4_0

{'score': 5.8, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:H/SI:H/SA:H'}

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 27, 2026, 2:32 PM
Reserved
Aug 3, 2026, 3:20 PM
Status
Deferred
Published
Aug 26, 2026, 11:17 PM
Modified
Sep 9, 2026, 9:09 PM