Loading story…
Red Hat disclosed CVE-2026-72526, a critical vulnerability in the multicloud-integrations component of Red Hat Advanced Cluster Management for Kubernetes 2. The flaw is caused by improper validation of the ocm-managed-cluster annotation in an Application custom resource handled by the Application propagation controller. Red Hat scored the issue CVSS 9.9 and classified it as CWE-441, a confused deputy-style authorization bypass.
An authenticated tenant with permission to create Application resources on the hub cluster can exploit the bug to target arbitrary managed spoke clusters, causing ArgoCD on those clusters to synchronize attacker-controlled manifests. Red Hat said successful exploitation could lead to arbitrary code execution or privilege escalation up to cluster-admin on connected spoke clusters. The affected package is listed as rhacm2/multicloud-integrations-rhel9, and Red Hat said no acceptable mitigation is currently available.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
Red Hat last modified its CVE-2026-72526 entry, continuing to list the product as affected and stating that no acceptable mitigation was available. The entry links the issue to Bugzilla 2514227.
Red Hat received CVE-2026-72526 via secalert@redhat.com. The vulnerability affects the rhacm2/multicloud-integrations-rhel9 package in Red Hat Advanced Cluster Management for Kubernetes 2.
Red Hat published CVE-2026-72526 for Red Hat Advanced Cluster Management for Kubernetes 2, describing a critical authorization-bypass flaw in multicloud-integrations caused by improper validation of the ocm-managed-cluster annotation. The issue can let a tenant with Application creation rights on the hub cluster target arbitrary spoke clusters and potentially achieve code execution or privilege escalation up to cluster-admin.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
3 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourceaccess.redhat.com
Open sourcebugzilla.redhat.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Red Hat Advanced Cluster Management for Kubernetes 2 is affected by **CVE-2026-10090**, an Important privilege escalation flaw in the `multicluster-operators-subscription` component that can let a user with namespace-scoped `edit` rights gain full `cluster-admin` access. Red Hat assigned the issue a **CVSS v3.1 score of 9.9**, and the Canadian Centre for Cyber Security issued advisory **AV26-803** urging organizations to review Red Hat guidance and apply updates when available. According to Red Hat's bug report and CVE record, the Application Subscription controller can be abused by creating a malicious Channel and Subscription that point to an attacker-controlled Helm repository. The controller then applies the Helm chart with elevated privileges without verifying the creator holds the required `open-cluster-management:subscription-admin` role and without restricting deployed resources to the subscription namespace, allowing deployment of cluster-scoped objects such as a `ClusterRoleBinding` that grants the attacker's ServiceAccount the `cluster-admin` ClusterRole. Red Hat said no mitigation meeting its product security criteria is currently available, and credited Christopher Lusk of North Echo Security Research with reporting the flaw.
Aug 14, 2026
Red Hat disclosed **`CVE-2026-73269`**, a critical privilege-escalation flaw in the `cluster-curator-controller` component used by **OpenShift Multicluster Engine for Kubernetes**. The bug allows a tenant with only namespace-level access to create a crafted `ClusterCurator` resource whose `metadata.name` differs from `metadata.namespace`, triggering the controller to create a cluster-scoped `ClusterRoleBinding` and, in some cases, a `RoleBinding` in an arbitrary namespace. Those bindings can attach the tenant’s namespace-local `cluster-installer` service account to the powerful curator role, effectively breaking namespace isolation. Successful exploitation can elevate a local tenant to **cluster-wide privileges**, including access to and manipulation of secrets, management of cluster actions, and deletion of hosted clusters or node pools. The issue carries a **CVSS 3.1 score of 9.9** and affects `multicluster-engine/cluster-curator-controller-rhel9`. Red Hat advised organizations to apply vendor fixes and reduce exposure by restricting creation of `ClusterCurator` resources through RBAC, enforcing matching `metadata.name` and `metadata.namespace` with an admission controller, and reviewing permissions that allow creation of cluster-scoped resources.
Aug 13, 2026
Red Hat disclosed **CVE-2026-73268**, an Important-severity flaw in the `cluster-curator-controller` component of **Multicluster Engine for Kubernetes** that can let a tenant escalate privileges to the controller’s level. The issue stems from the `CreateJob()` function improperly unmarshaling user-controlled data from `spec.install.overrideJob` into a Kubernetes `Job` without validating dangerous fields, enabling arbitrary Job specification injection by users who can create or update `ClusterCurator` resources. Successful exploitation can cause the injected Job to run under the controller’s privileged ServiceAccount, potentially allowing arbitrary code execution, access to cluster-wide secrets, and control over managed cluster resources. Red Hat scored the bug **9.9 CVSS v3.1** and linked it to **CWE-94**; affected software includes `multicluster-engine/cluster-curator-controller-rhel9`. Recommended mitigations include applying vendor fixes, tightening **RBAC** so only trusted administrators can manage `clustercurators.cluster.open-cluster-management.io`, and reviewing controller privileges and validation controls around Job creation.
Aug 13, 2026