Description

A flaw was found in multicloud-integrations, a component of Red Hat Advanced Cluster Management (RHACM). This vulnerability allows an authenticated user, referred to as a tenant, to manipulate the GitOpsCluster controller. By exploiting this, a tenant can redirect sensitive spoke cluster bearer tokens from secure locations to a namespace they control. This unauthorized access to tokens can lead to the disclosure of critical information and bypass security policies within ArgoCD AppProjects.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "9.6",
  "pubDate": "2026-08-12T02:16:38.060Z",
  "pubdate": "2026-08-12T02:16:38.060Z",
  "executiveSummary": "A critical security vulnerability has been identified in multicloud-integrations, a core component of Red Hat Advanced Cluster Management (RHACM). This flaw exposes a severe authorization bypass within the GitOpsCluster controller, permitting an authenticated tenant user to manipulate cluster management workflows. By exploiting this weakness, an attacker can coerce the system into redirecting sensitive spoke cluster bearer tokens from their intended secure destinations directly into an attacker-controlled namespace. This unauthorized interception of authentication material leads to the unauthorized disclosure of critical infrastructure secrets and effectively breaches security boundaries enforced by ArgoCD AppProjects. The risk implication is severe, as compromised bearer tokens grant elevated control over managed spoke clusters, undermining multi-tenant isolation guarantees. Successful exploitation requires authenticated access to the environment with tenant privileges, allowing the user to interact with the vulnerable GitOpsCluster controller logic. No specific external network exposure beyond the standard authenticated interface is strictly required, as the vector relies on logical authorization flaws rather than network-level protocol degradation.",
  "technicalDetails": "The vulnerability resides within the GitOpsCluster controller component of multicloud-integrations, which facilitates the synchronization and management of GitOps targets across managed clusters in Red Hat Advanced Cluster Management. The root cause stems from insufficient validation and improper authorization enforcement within the controller when processing tenant-submitted configurations or interacting with sensitive secret references. Specifically, the controller fails to adequately restrict target namespaces for sensitive credentials during reconciliation operations.\nThe attack flow begins when an authenticated tenant user crafts a malicious or manipulated resource definition targeting the GitOpsCluster controller. Due to the lack of strict namespace scoping and validation in the controller's reconciliation logic, the user is able to influence where sensitive spoke cluster bearer tokens are dispatched. When the controller processes the manipulated input, it reads the high-privilege bearer tokens from their secure storage locations and inadvertently writes or mirrors them into a namespace under the direct control of the tenant.\nUpon successful redirection and interception of the spoke cluster bearer tokens, the attacker achieves unauthorized access to critical cluster credentials. This post-exploitation impact allows the adversary to completely bypass security boundaries and access controls defined within ArgoCD AppProjects. Armed with the sensitive bearer tokens, the authenticated tenant can interact directly with the underlying spoke clusters, escalating their privileges from a restricted tenant scope to potentially administrative control over managed cluster resources, thereby violating multi-tenant segregation principles within the deployment infrastructure."
}