CVE-2026-62246: CWE-284: Improper Access Control in clastix kamaji
Kamaji, a Hosted Control Plane Manager for Kubernetes, has an improper access control vulnerability prior to version 26.7.4-edge. The issue arises from a lossy normalization process that causes distinct tenants with colliding normalized identifiers to share control-plane state. This allows unauthorized tenants to read, modify, or destroy another tenant's Kubernetes data. The vulnerability is identified as CVE-2026-62246 and has a high severity score of 8.5. The problem is fixed in version 26.7.4-edge.
AI Analysis
Technical Summary
Kamaji versions before 26.7.4-edge use a lossy namespace-and-name normalization in the functions GetDefaultDatastoreSchema() and GetDefaultDatastoreUsername() to derive TenantControlPlane datastore schema, database user, and etcd key prefix. This flawed normalization can cause distinct tenants with colliding normalized identifiers to share control-plane state, enabling unauthorized access to another tenant's Kubernetes data, including reading, modification, or destruction. The vulnerability is classified under CWE-284 (Improper Access Control) and CWE-653. The issue is resolved in Kamaji version 26.7.4-edge.
Potential Impact
Exploitation of this vulnerability allows a tenant to access, modify, or destroy Kubernetes data belonging to another tenant due to improper access control caused by identifier collisions. This compromises confidentiality, integrity, and availability of tenant data within the Kamaji control plane.
Mitigation Recommendations
A fix is available in Kamaji version 26.7.4-edge. Users should upgrade to this version or later to remediate the vulnerability. Patch status beyond this is not explicitly stated; verify with the vendor for the latest remediation guidance.
CVE-2026-62246: CWE-284: Improper Access Control in clastix kamaji
Description
Kamaji, a Hosted Control Plane Manager for Kubernetes, has an improper access control vulnerability prior to version 26.7.4-edge. The issue arises from a lossy normalization process that causes distinct tenants with colliding normalized identifiers to share control-plane state. This allows unauthorized tenants to read, modify, or destroy another tenant's Kubernetes data. The vulnerability is identified as CVE-2026-62246 and has a high severity score of 8.5. The problem is fixed in version 26.7.4-edge.
CVSS v3.1
Score 8.5high
Affected software
clastix
kamaji
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Kamaji versions before 26.7.4-edge use a lossy namespace-and-name normalization in the functions GetDefaultDatastoreSchema() and GetDefaultDatastoreUsername() to derive TenantControlPlane datastore schema, database user, and etcd key prefix. This flawed normalization can cause distinct tenants with colliding normalized identifiers to share control-plane state, enabling unauthorized access to another tenant's Kubernetes data, including reading, modification, or destruction. The vulnerability is classified under CWE-284 (Improper Access Control) and CWE-653. The issue is resolved in Kamaji version 26.7.4-edge.
Potential Impact
Exploitation of this vulnerability allows a tenant to access, modify, or destroy Kubernetes data belonging to another tenant due to improper access control caused by identifier collisions. This compromises confidentiality, integrity, and availability of tenant data within the Kamaji control plane.
Mitigation Recommendations
A fix is available in Kamaji version 26.7.4-edge. Users should upgrade to this version or later to remediate the vulnerability. Patch status beyond this is not explicitly stated; verify with the vendor for the latest remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-13T17:09:57.573Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a6bc4339c2644c7f8b99af3
Added to database: 07/30/2026, 21:37:55 UTC
Last enriched: 08/07/2026, 14:30:51 UTC
Last updated: 09/13/2026, 22:01:35 UTC
Views: 64
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.