Loading vulnerability…
Arbitrary Managed-Cluster Targeting in Red Hat ACM multicloud-integrations
CVE-2026-72526 is an authorization-bypass flaw in the multicloud-integrations component of Red Hat Advanced Cluster Management for Kubernetes 2. The Application propagation controller insufficiently validates the managed-cluster selection annotation on Application custom resources. Consequently, a hub-cluster tenant authorized to create Applications can cause propagation to arbitrary connected managed clusters, rather than only clusters within that tenant's authorized scope. This constitutes a confused-deputy condition in which the propagation infrastructure performs privileged cross-cluster actions on behalf of an insufficiently authorized tenant.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
An attacker can cause ArgoCD instances on arbitrary targeted spoke clusters to synchronize attacker-controlled manifests. This can result in high-impact compromise of those clusters, including arbitrary code execution and privilege escalation up to cluster-administrator privileges. The authorization bypass crosses the hub-to-spoke trust boundary and affects confidentiality, integrity, and availability of targeted managed clusters.
If you can’t patch tonight, do this now.
No mitigation meeting the vendor's product-security criteria is currently available. Restricting the ability to create Application custom resources on the hub cluster to fully trusted principals can reduce exposure until a vendor remediation is available.
Patch, then assume compromise.
Apply the vendor-provided fix for CVE-2026-72526 in Red Hat Advanced Cluster Management for Kubernetes 2, specifically updates addressing the multicloud-integrations component. Remediation requires correcting validation and authorization handling for the ocm-managed-cluster annotation in the Application propagation workflow so that Application resources cannot target unauthorized managed clusters. If fixed packages or releases are available from the vendor, affected deployments should be upgraded promptly.
No public exploits tracked yet. Mallory keeps watching.
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.