CVE-2026-69129

MEDIUMPre-NVD 5.85.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (33rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
5.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
5.8
EG Score
5.8MEDIUMmedium confidence
EG Risk
26
EG Risk 26/100

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 computed (value × EchelonGraph’s weight)
Severity58% × 45%
The EG Score, 5.8 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 26, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Aug 26, 2026
Patch available. Sources: github_release, github, github_commit.
GitHub advisoryMentions a patch (unverified)

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-9hxh
GitHub release Patch Available

v2.0.1

Patch available: 1Panel-dev/KubePi v2.0.1

https://github.com/1Panel-dev/KubePi/releases/tag/v2.0.1
GitHub 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/8e6ceefc68f374225aba2e6bc1905bb4210e6045

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 48× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-11 19:29 UTCEG score recompute
  2. 2026-10-11 16:45 UTCEG score recompute
  3. 2026-10-11 14:05 UTCEG score recompute
  4. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-10-10 09:53 UTCEG score recompute
  7. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-10-09 07:18 UTCEG score recompute
  9. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-10-08 05:31 UTCEG score recompute
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  12. 2026-10-07 03:46 UTCEG score recompute
  13. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  14. 2026-10-06 01:41 UTCEG score recompute
  15. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  17. 2026-10-03 16:05 UTCEG score recompute
  18. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  19. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  20. 2026-10-02 09:28 UTCEG score recompute
  21. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  22. 2026-10-01 07:43 UTCEG score recompute
  23. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  24. 2026-09-30 05:59 UTCEG score recompute
  25. 2026-09-28 23:59 UTCEG score recompute
Show 53 more
  1. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-09-27 22:15 UTCEG score recompute
  3. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-09-26 20:30 UTCEG score recompute
  5. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-09-25 00:14 UTCEG score recompute
  7. 2026-09-23 20:51 UTCEG score recompute
  8. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  9. 2026-09-22 19:06 UTCEG score recompute
  10. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  11. 2026-09-21 17:21 UTCEG score recompute
  12. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  13. 2026-09-20 14:43 UTCEG score recompute
  14. 2026-09-19 12:59 UTCEG score recompute
  15. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  16. 2026-09-18 11:14 UTCEG score recompute
  17. 2026-09-17 09:30 UTCEG score recompute
  18. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  19. 2026-09-16 07:44 UTCEG score recompute
  20. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  21. 2026-09-15 05:57 UTCEG score recompute
  22. 2026-09-14 04:11 UTCEG score recompute
  23. 2026-09-13 02:27 UTCEG score recompute
  24. 2026-09-12 00:42 UTCEG score recompute
  25. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  26. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  27. 2026-09-10 22:57 UTCEG score recompute
  28. 2026-09-09 15:06 UTCEG score recompute
  29. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  30. 2026-09-08 13:21 UTCEG score recompute
  31. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  32. 2026-09-07 11:23 UTCEG score recompute
  33. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  34. 2026-09-06 09:32 UTCEG score recompute
  35. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  36. 2026-09-05 07:48 UTCEG score recompute
  37. 2026-09-04 06:03 UTCEG score recompute
  38. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  39. 2026-09-03 04:13 UTCEG score recompute
  40. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  41. 2026-09-02 02:25 UTCEG score recompute
  42. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  43. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  44. 2026-08-30 22:52 UTCEG score recompute
  45. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  46. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  47. 2026-08-29 21:08 UTCEG score recompute
  48. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  49. 2026-08-27 17:30 UTCEG score recompute
  50. 2026-08-27 17:06 UTCEG score recompute
  51. 2026-08-26 23:21 UTCEG score recompute
  52. 2026-08-26 23:10 UTCEG score recomputeFirst assessed: 5.8 MEDIUM
  53. 2026-08-26 23:09 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-69129?
CVE-2026-69129 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-69129 published?
The CVE record for CVE-2026-69129 was published on August 26, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-69129 actively exploited?
CVE-2026-69129 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-69129?
CVE-2026-69129 has a CVSS base score of 5.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-69129?
A fix for CVE-2026-69129 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-69129

Explore →

Is Your Infrastructure Affected by CVE-2026-69129?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs