EUVD-2026-57059
GHSA-37c6-v768-8x6w
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Network vector via Kubernetes API; PR:L reflects required namespace-admin role; S:C captures cross-namespace Secret access outside the attacker's authorization boundary; no integrity or availability impact.
Primary rating from Vendor (redhat).
CVSS VectorVendor: redhat
Lifecycle Timeline
2DescriptionCVE.org
A flaw was found in multicloud-operators-subscription. A privileged user, specifically a namespace administrator capable of creating Channel and Subscription resources, can exploit this vulnerability. By manipulating the Channel.Spec.SecretRef.Namespace field, the user can cause the system to copy sensitive Secret contents from other namespaces into their own, leading to information disclosure.
AnalysisAI
Secret exfiltration across Kubernetes namespace boundaries in the multicloud-operators-subscription component of Red Hat Advanced Cluster Management for Kubernetes 2 allows an authenticated namespace administrator to read Kubernetes Secrets from arbitrary namespaces outside their own authorization domain. By setting Channel.Spec.SecretRef.Namespace to a target namespace, the attacker causes the subscription controller to autonomously copy sensitive Secret contents into a namespace the attacker controls, violating the Kubernetes namespace isolation model. No public exploit code has been identified at time of analysis, but the scope-changed CVSS vector (S:C, C:H) and the sensitivity of Kubernetes Secret payloads - which frequently contain credentials, API tokens, and TLS private keys - make this a high-priority finding in any multi-tenant RHACM deployment.
Technical ContextAI
The multicloud-operators-subscription operator is a core component of Red Hat Advanced Cluster Management for Kubernetes (RHACM) 2.x (CPE: cpe:2.3:a:red_hat:red_hat_advanced_cluster_management_for_kubernetes_2:*:*:*:*:*:*:*:*), responsible for managing GitOps-style Channel and Subscription custom resources across multi-cluster Kubernetes environments. The vulnerability maps to CWE-639 (Authorization Bypass Through User-Controlled Key), where the attacker supplies a user-controlled namespace value in Channel.Spec.SecretRef.Namespace that the subscription controller treats as an authoritative pointer when locating Secrets to copy. Because the controller operates with elevated cluster-level RBAC permissions that span namespace boundaries, a namespace-scoped user can indirectly leverage those permissions to access Secrets they were never explicitly granted. Kubernetes Secrets routinely carry cloud provider credentials, registry pull secrets, database passwords, and TLS certificates, making their unauthorized disclosure a cascading confidentiality risk across dependent workloads.
RemediationAI
The primary remediation is to apply the vendor-released patch once confirmed available per the Red Hat advisory at https://access.redhat.com/security/cve/CVE-2026-66878; no specific fixed version number was present in the available input data, so operators must monitor that advisory and the Bugzilla tracker at https://bugzilla.redhat.com/show_bug.cgi?id=2514226 for patch release details. As an immediate compensating control, audit and minimize the set of users and service accounts that hold permissions to create Channel and Subscription custom resources within RHACM, since these are the exact capabilities required for exploitation - restricting this role reduces the attacker population without requiring downtime. Deploying a Kubernetes admission webhook or OPA/Gatekeeper policy that rejects Channel resources where Spec.SecretRef.Namespace differs from the Channel's own namespace directly blocks the exploitable field manipulation with low operational overhead, though the trade-off is that any legitimate cross-namespace SecretRef usage in existing workflows must be audited and re-authorized before enforcement. Additionally, enabling Kubernetes audit logging for Secret read and create events across namespaces can provide detection coverage while a patch is pending.
Cross-cluster remote code execution in Red Hat Advanced Cluster Management for Kubernetes 2 (multicloud-integrations / A
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
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 Authentication Bypass
View allVendor StatusVendor
Share
External POC / Exploit Code
Leaving vuln.today