Vulnerability · Published Jul 30, 2026 · Assigned by GitHub_M

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

High 8.5

In plain English

A high-severity improper access control in kamaji from clastix. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 30% of all known vulnerabilities).

Severity (CVSS 3.1)8.5High

Exploit odds (30 days)0.4%top 69.7% of all CVEs

Exploited in the wildNo reportsCISA SSVC: poc

Attack toolingNoneno public tooling known

Official 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.

Affected products (as reported)

Vendor	Product	Versions
clastix	kamaji	< 26.7.4-edge

Weakness: CWE-284, CWE-653 · Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

References

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