CVE-2026-62246: clastix kamaji · Improper Access Control
Affects clastix kamajiSource CVE Database V5
Not known to be exploited · CVSS 8.5 High : upgrade to 26.7.4-edge soon.
Data as of 29 Oct 2026, 07:15 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 26.7.4-edge
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 30 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade clastix kamaji to 26.7.4-edge.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| clastixkamaji | Affected
| Fixed in
|
GitHubclastix/kamajipkg:github/clastix/kamajiOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
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.
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.