CVE-2026-72526: Multicloud-integrations: multicloud-integrations: pull-model propagation allows hub tenant to target arbitrary spoke cluster via unvalidated ocm-managed-cluster annotation

Published Aug 11, 2026
·
Updated

A flaw was found in the multicloud-integrations component of Red Hat Advanced Cluster Management (RHACM). The Application propagation controller takes the tenant-controlled ocm-managed-cluster annotation verbatim from an Application CR and uses it as the ManifestWork namespace without authorization checks. The only validation is a bare existence check on the target ManagedCluster. A tenant with Application create permissions in any hub namespace can generate ManifestWorks targeting arbitrary managed clusters, resulting in spoke cluster-admin ArgoCD syncing attacker-controlled manifests.

Upstream repo: https://github.com/stolostron/multicloud-integrations Audited commit: d88a168 Jira tracker: ACM-38643

Other sources

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.

NVD

Affected Software

2 affected components
Red Hat Red Hat Advanced Cluster Management (RHACM)
multicloud-integrations

Event History

Aug 11, 2026
Data Sourced
via Red Hat·05:38 PM
DescriptionSeverityAffected Software
Aug 12, 2026
CVE Published
via MITRE·01:10 AM
Data Sourced
via MITRE·01:10 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:16 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is the severity of CVE-2026-72526?

The severity of CVE-2026-72526 is critical with a score of 9.9.

2

How does CVE-2026-72526 affect multicloud-integrations?

CVE-2026-72526 allows a hub tenant with appropriate permissions to exploit an unvalidated annotation to target arbitrary spoke clusters.

3

What can an attacker achieve by exploiting CVE-2026-72526?

An attacker can potentially gain unauthorized access and control over arbitrary spoke clusters due to the flawed propagation mechanism.

4

How do I fix CVE-2026-72526?

To fix CVE-2026-72526, ensure that proper validation is implemented for the `ocm-managed-cluster` annotation in the Application propagation controller.

5

What are the impacts of CVE-2026-72526 on system security?

CVE-2026-72526 poses a high risk to system security by allowing unauthorized actions on critical components in a multicloud environment.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203