EUVD-2026-57057
GHSA-hp26-rmxw-4cpv
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Hub-authenticated Application-create rights give PR:L over network with low complexity; the unvalidated annotation lets the controller cross into separately-managed spokes (S:C) for full C/I/A compromise.
Primary rating from Vendor (redhat).
CVSS VectorVendor: redhat
Lifecycle Timeline
2DescriptionCVE.org
A flaw was found in the multicloud-integrations component. The Application propagation controller processes the ocm-managed-cluster annotation from an Application Custom Resource (CR) without proper validation. A tenant with permissions to create Applications on the hub cluster can exploit this to target arbitrary managed clusters. This can force ArgoCD on the spoke clusters to synchronize attacker-controlled manifests, leading to arbitrary code execution or privilege escalation on those clusters.
AnalysisAI
Cross-cluster remote code execution in Red Hat Advanced Cluster Management for Kubernetes 2 (multicloud-integrations / ArgoCD pull-model integration) lets a low-privileged hub tenant who can create Application CRs redirect propagation to arbitrary managed spoke clusters. Because the Application propagation controller trusts the attacker-supplied ocm-managed-cluster annotation without validation, an attacker forces ArgoCD on targeted spokes to sync attacker-controlled manifests, yielding code execution or privilege escalation there. CVSS 9.9 with scope change; no public exploit identified at time of analysis and it is not listed in CISA KEV.
Technical ContextAI
The affected code is the multicloud-integrations component of RHACM, which implements the ArgoCD 'pull' model on top of Open Cluster Management (OCM): a controller on the hub reads Application Custom Resources and propagates the intended sync target to spoke (managed) clusters, where a local ArgoCD applies the manifests. The ocm-managed-cluster annotation is meant to indicate which managed cluster an Application belongs to, but the propagation controller consumes it as a trusted routing directive without authorization or tenancy validation. This matches CWE-441 (Unintended Proxy or Intermediary - 'Confused Deputy'): the highly-privileged controller uses its own cross-cluster credentials to act on an untrusted, tenant-supplied value, effectively lending its authority to the attacker. The CPE identifies the affected product as red_hat_advanced_cluster_management_for_kubernetes_2.
RemediationAI
No vendor-released patch version is identified in the provided data, so apply the Red Hat erratum for your RHACM 2.x stream once published and monitor https://access.redhat.com/security/cve/CVE-2026-72526 and Bugzilla 2514227 for the fixed z-stream build. As compensating controls until patched: tighten RBAC so tenants cannot freely create Application CRs on the hub, and constrain who may set or modify the ocm-managed-cluster annotation - enforce this with an admission policy (OPA/Gatekeeper or Kubernetes ValidationAdmissionPolicy) that rejects or pins the annotation to the tenant's authorized cluster set, accepting the trade-off of additional policy maintenance and possible friction for legitimate multi-cluster Applications. Additionally, scope each tenant's Applications to namespaces/AppProjects mapped only to their permitted managed clusters and audit ArgoCD sync activity on spokes for unexpected sources; note these controls reduce but do not eliminate the confused-deputy path if the propagation controller still trusts the annotation.
Cross-tenant bearer-token disclosure in Red Hat Advanced Cluster Management for Kubernetes 2 (RHACM) lets an authenticat
Unauthorized cross-tenant Secret and ConfigMap access in the multicloud-operators-channel component of Red Hat Advanced
Secret exfiltration across Kubernetes namespace boundaries in the multicloud-operators-subscription component of Red Hat
Privilege escalation in Red Hat Advanced Cluster Management for Kubernetes 2 lets a namespace-scoped tenant abuse the mu
Privilege escalation and cluster-wide arbitrary resource deployment affects the multicloud-operators-subscription compon
Privilege escalation in Red Hat Advanced Cluster Management's multicloud-operators-subscription controller lets a low-pr
Privilege escalation in Red Hat Advanced Cluster Management for Kubernetes 2 stems from the search-v2-operator being bou
Cross-cluster remote code execution in Red Hat Advanced Cluster Management for Kubernetes 2 (acm-search-v2-rhel9 search
Remote code execution as root on the Submariner gateway node is possible in cert-auth mode, affecting Submariner as bund
Cross-namespace Secret manipulation in the multicloud-operators-channel component of Red Hat Advanced Cluster Management
Command and SQL injection in Red Hat Advanced Cluster Management for Kubernetes 2 (acm-search-v2-rhel9) lets a privilege
Privilege escalation in Red Hat Advanced Cluster Management for Kubernetes 2 allows any attacker with local pod executio
Same technique Privilege Escalation
View allVendor StatusVendor
Share
External POC / Exploit Code
Leaving vuln.today