CVE-2026-72508: Multicloud-operators-subscription: multicloud-operators-subscription: hub and spoke serviceaccounts bound to wildcard rbac (*/*/*)
A flaw was found in the multicloud-operators-subscription component of Red Hat Advanced Cluster Management (RHACM). This vulnerability allows a namespace-admin tenant to perform a confused-deputy attack by creating Subscription Custom Resources (CRs) that leverage a highly privileged ServiceAccount (SA). This enables the tenant to deploy arbitrary cluster-scoped resources, leading to privilege escalation and potential arbitrary code execution across the cluster.
Security readout for executives and security teams
Plain-English summary
A namespace administrator in an affected Red Hat Advanced Cluster Management environment can misuse an overly privileged service account to gain cluster-wide control. Successful abuse could expose or alter sensitive workloads, disrupt services, and potentially execute arbitrary code across the cluster.
Executive priority
Treat this as an urgent remediation for affected multi-tenant RHACM clusters. The required access is limited to a namespace administrator, but compromise can cross the namespace boundary and affect the entire cluster. Establish ownership, inventory affected builds, apply the applicable Red Hat guidance, and investigate suspicious Subscription activity.
Technical view
The multicloud-operators-subscription component binds hub-and-spoke service accounts to wildcard RBAC permissions. An authenticated namespace-admin can create Subscription custom resources that cause the privileged service account to deploy arbitrary cluster-scoped resources, producing a confused-deputy privilege escalation. The CVSS 3.1 score is 9.9, with low complexity, low privileges, no user interaction, and changed scope.
Likely exposure
Exposure applies to the listed multicluster-operators-subscription-rhel9 builds in RHACM 2.11 and 2.13 through 2.17. Risk is greatest in multi-tenant clusters where namespace administrators can create Subscription resources. RHACM 2.12 and other products or builds are not identified as affected in the supplied evidence.
Exploitation context
Abuse requires authenticated namespace-admin privileges but reportedly needs no user interaction and can occur over the network. The source bundle reports KEV=false and provides no evidence of active exploitation or a public exploit. Absence from KEV does not establish that exploitation has never occurred.
Researcher notes
The central trust-boundary failure is wildcard RBAC granted to service accounts reachable indirectly through tenant-controlled Subscription resources. Validate the effective authorization path, not merely the tenant's direct permissions. The supplied evidence does not identify fixed build numbers, a workaround, public proof-of-concept availability, or observed attacks.
Mitigation direction
Review the Red Hat erratum applicable to each deployed RHACM release and follow its remediation guidance.
Update affected multicluster-operators-subscription-rhel9 packages through supported Red Hat channels.
If updating is delayed, obtain vendor-approved compensating controls; the supplied evidence names no workaround.
Prioritize environments where separate or untrusted tenants hold namespace-admin permissions.
Validation and detection
Inventory RHACM releases and exact multicluster-operators-subscription-rhel9 package builds across hub and managed clusters.
Compare discovered builds with the affected identifiers listed for RHACM 2.11 and 2.13 through 2.17.
Confirm applicable Red Hat errata are installed using supported package and cluster-management records.
Review Subscription activity by namespace administrators for unexpected cluster-scoped resource creation.
Verify operator service-account permissions match Red Hat's post-remediation guidance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-250: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
5Timeline events
1ADP providers
9Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-250 · source CWE mapping
Execution with Unnecessary Privileges
Execution with Unnecessary Privileges represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.