The vulnerability CVE-2026-73267 in Multicluster Engine concerns the clusterclaims-controller and allows a tenant with basic privileges to delete ManagedClusters owned by other tenants or even the hub. Red Hat rates the vulnerability as important, with an initial CVSS of 7.7.
The vulnerability was discovered in Multicluster Engine for Kubernetes, the platform used to manage multiple clusters from a central environment. According to Red Hat's official analysis, the issue is due to a missing ownership check in the ClusterClaim resource management flow.
See also: Red Hat ACM Application resources: Critical vulnerability CVE-2026-72
CVE-2026-73267 Multicluster Engine: How the attack works
To exploit CVE-2026-73267 Multicluster Engine, an attacker needs a tenant account and permissions to create and delete ClusterClaim. No user interaction is required, and the attack is performed over the network and is characterized by low complexity.
The critical point is in the spec.namespace. The controller uses the value of the field to determine which ManagedCluster to handle, without verifying that the tenant actually owns the cluster. Thus, a user with limited access can report a resource from another tenant and cause it to be deleted.
This technique does not directly lead to data disclosure or change of cluster content. However, it creates a serious denial of service, because it can take down the local-cluster hub or infrastructure serving other clusters. In multi-tenant environments, such an action can disrupt services and require time-consuming recovery.
What we know about the affected versions
Red Hat's page does not yet list a complete list of affected versions or a separate workaround that meets the criteria of ease and widespread implementation. The entry links the vulnerability to Bugzilla 2514218 and CWE-602, which is insufficient enforcement of server-side security checks.
The CVSS score of 7.7 primarily reflects the impact on availability rather than a breach of confidentiality. However, the controller's position at the central management level increases the significance of the incident: deleting a ManagedCluster can impact applications, policies, and deployment processes that depend on it.
Red Hat notes that the assessment is preliminary and subject to revision. The NVD page for CVE-2026-73267 does not yet have a rich description or metrics, so organizations should not wait for the final listing to review their report.
In deployments where tenants create ClusterClaim resources through automation, control should extend to deployment pipelines. Service accounts, CI/CD credentials, and roles used temporarily need the same strict treatment as human accounts because they can perform the same dangerous actions.
In parallel, Red Hat has released a security update for Multicluster Engine 2.17.1, with new clusterclaims-controller images for amd64, arm64, ppc64le, and s390x. Administrators should check the exact version they are using and follow the documentation in the related security update RHSA-2026:48284.
See also: CVE-2026-56163: Critical vulnerability in Azure Kubernetes Service
Immediate protection measures for administrators
Until the upgrade is complete, security teams should restrict ClusterClaim creation and deletion permissions to only highly trusted accounts and service accounts. RBAC rules should also be reviewed to ensure that a tenant cannot refer to namespaces or clusters outside of its own boundary.
Log audits should look for unusual changes to spec.namespace, ManagedCluster deletions, and actions originating from accounts without a corresponding business reason. Comparing audit logs before and after the update helps detect exploitation attempts.
🔒 Protect your privacy with Proton VPN
Swiss VPN from the creators of Proton Mail — strict no-logs policy, strong encryption, and built-in NetShield that blocks ads, trackers, & malware.
- ✔ No-logs, based in Switzerland (except 14-Eyes)
- ✔ NetShield: blocks ads, trackers & malicious domains
- ✔ Covers all devices — free version available
The link is an affiliate link — SecNews may receive a commission at no additional cost to you. It does not affect the independence of our article writing.
After installing the update, it is advisable to verify the version of the container image that is actually running, not just the version that the management environment declares. This verification should be accompanied by testing of RBAC constraints and backups of necessary configurations so that recovery is not based on untested procedures.
See also: SourTrade Malvertising: The browser builds malware piece by piece
CVE -2026-73267 Multicluster Engine does not require advanced technical access, but does require an account within the environment. For this reason, the SecNews technical team recommends immediately checking tenant permissions, updating to a supported version, and continuously monitoring cluster management actions.
