Skip to content
Cloud

CVE-2026-62246

8.5
High
EPSS 0.27%Patch availableJul 31, 2026

Normalization collision in Kamaji allows cross-tenant control-plane access

common questions

Is CVE-2026-62246 being exploited?

Not confirmed. CVE-2026-62246 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.27% probability of exploitation in the next 30 days.

How severe is CVE-2026-62246?

CVE-2026-62246 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-62246?

Yes. A fix has been recorded for CVE-2026-62246. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-62246 affect?

CVE-2026-62246 affects Kamaji < 26.7.4-edge, Hosted Kubernetes control planes, TenantControlPlane datastore, etcd key prefixes. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-62246?

Upgrade to Kamaji 26.7.4-edge; audit tenant state, rotate credentials, restore compromised data if needed

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Kamaji < 26.7.4-edgeHosted Kubernetes control planesTenantControlPlane datastoreetcd key prefixes
impact

Normalization collisions let one tenant read, modify, or destroy another tenant's Kubernetes control-plane and etcd data.

action required

Immediate action required

affected versions
clastix kamaji
  • affected< 26.7.4-edge

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free