Kamaji is the Hosted Control Plane Manager for Kubernetes. Prior to 26.7.4-edge, Kamaji derives a TenantControlPlane datastore schema, database user, and etcd key prefix from a lossy namespace-and-name normalization in GetDefaultDatastoreSchema() and GetDefaultDatastoreUsername(), allowing distinct tenants with colliding normalized identifiers to share control-plane state and read, modify, or destroy another tenant's Kubernetes data. This issue is fixed in version 26.7.4-edge.
CVE-2026-62246
This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.5
- EG Score
- 8.5(low)
- EG Risk
- 43(Track)EG Risk 43/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 computedSeverity85% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
July 30, 2026
Last Modified
July 30, 2026
Advisory Details (2)
Auto-updated Jul 30, 2026commit 4232a9df7ccd (clastix/kamaji)
Patch available: clastix/kamaji 26.7.4-edge (contains commit 4232a9df7ccd)
https://github.com/clastix/kamaji/commit/4232a9df7ccd08075c26191f59566202042543a9TenantControlPlane namespace/name collision binds two tenants to the same etcd key prefix, or SQL datastore schema + DB user, breaking per-tenant isolation · Advisory · clastix/kamaji · GitHub
https://github.com/clastix/kamaji/security/advisories/GHSA-4f3f-65vx-r34fWeakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× 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-07-30 22:20 UTCEG score recompute
- 2026-07-30 21:26 UTCEG score recompute
- 2026-07-30 21:25 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-284
Frequently asked(4)
What is CVE-2026-62246?
When was CVE-2026-62246 disclosed?
What is the CVSS score of CVE-2026-62246?
How do I remediate CVE-2026-62246?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-62246
Is Your Infrastructure Affected by CVE-2026-62246?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.