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.
CVE-2026-69129
MEDIUMPre-NVD 5.85.8—
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 5.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 85% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.8Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.8
- EG Score
- 5.8(medium)
- EG Risk
- 26(Track)EG Risk 26/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity58% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 15%
- KEV
- Not listed
Published
August 26, 2026
Last Modified
August 27, 2026
Advisory Details (3)
Auto-updated Aug 26, 2026Patch available. Sources: github_release, github, github_commit.
github Patch Available
KubePi: insufficient per-cluster authorization checks in cluster management APIs · Advisory · 1Panel-dev/KubePi · GitHub
https://github.com/1Panel-dev/KubePi/security/advisories/GHSA-cwg7-34p9-9hxhgithub_release Patch Available
v2.0.1
Patch available: 1Panel-dev/KubePi v2.0.1
https://github.com/1Panel-dev/KubePi/releases/tag/v2.0.1github_commit Patch Available
commit 8e6ceefc68f3 (1Panel-dev/KubePi)
Patch available: 1Panel-dev/KubePi v2.0.1 (contains commit 8e6ceefc68f3)
https://github.com/1Panel-dev/KubePi/commit/8e6ceefc68f374225aba2e6bc1905bb4210e6045Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-27 17:30 UTCEG score recompute
- 2026-08-27 17:06 UTCEG score recompute
- 2026-08-26 23:21 UTCEG score recompute
- 2026-08-26 23:10 UTCEG score recompute
- 2026-08-26 23:09 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS p94CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS p94CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS p97CRITICAL
- CVE-2019-13360EG 9.8EPSS p98CRITICAL
- CVE-2019-12866EG 9.8CRITICAL
- CVE-2019-9756EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-69129?
CVE-2026-69129 is a medium vulnerability published on August 26, 2026. 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…
When was CVE-2026-69129 disclosed?
CVE-2026-69129 was first published in the National Vulnerability Database on August 26, 2026, with the most recent update on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-69129 actively exploited?
CVE-2026-69129 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.4% of all scored CVEs.
What is the CVSS score of CVE-2026-69129?
CVE-2026-69129 has a CVSS v3 base score of 5.8 (NVD).
How do I remediate CVE-2026-69129?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69129, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-69129
Is Your Infrastructure Affected by CVE-2026-69129?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.