CVE-2026-67567
HelmRelease template processing lets tenants deploy arbitrary cluster resources via elevated controller SA.
Is CVE-2026-67567 being exploited?
Not confirmed. CVE-2026-67567 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.43% probability of exploitation in the next 30 days.
How severe is CVE-2026-67567?
CVE-2026-67567 is rated Critical with a CVSS score of 9.9. 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-67567?
Yes. A fix has been recorded for CVE-2026-67567. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67567 affect?
CVE-2026-67567 affects multicloud-operators-subscription HelmRelease controller, Kubernetes clusters using multicloud-operators-subscription. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67567?
Patch from vendor if available; otherwise revoke HelmRelease create rights, tighten RBAC, or disable controller.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
A tenant who can create HelmRelease CRs can deploy arbitrary resources cluster-wide using the controller's elevated ServiceAccount, enabling full cluster compromise and arbitrary code execution.
Immediate action required