EUVD-2026-63590
GHSA-rf6j-x765-j4p2
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Kubernetes API is network-accessible; HelmRelease create equals PR:L; namespace boundary crossing warrants S:C; credential exfiltration yields C:H with no integrity or availability impact.
Primary rating from Vendor (redhat).
CVSS VectorVendor: redhat
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Lifecycle Timeline
2DescriptionCVE.org
A flaw was found in the multicloud-operators-subscription component of Red Hat Advanced Cluster Management (RHACM). A tenant with HelmRelease create permissions can exploit this vulnerability by manipulating the secretRef.Namespace field. This allows the GetSecret() function in the HelmRelease controller to fetch sensitive credentials from any namespace, which are then sent to an attacker-controlled Helm repository. This can lead to the exfiltration of credentials from arbitrary namespace Secrets, resulting in information disclosure.
AnalysisAI
Credential exfiltration in RHACM's multicloud-operators-subscription component allows an authenticated tenant with HelmRelease create permissions to bypass Kubernetes namespace isolation by manipulating the secretRef.Namespace field, causing the HelmRelease controller to fetch Secrets from arbitrary namespaces and transmit them to an attacker-controlled Helm repository. The CVSS S:C (scope changed) metric confirms this breaks the namespace boundary that Kubernetes multi-tenancy depends on, enabling low-privileged lateral movement across namespace security domains. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | The attacker must possess a valid Kubernetes identity in the RHACM-managed cluster with RBAC `create` permission on `HelmRelease` resources (and optionally `update` for iteration) in at least one namespace - this is the sole prerequisite for triggering the vulnerable `GetSecret()` code path. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 score of 7.7 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N) accurately characterizes this as a high-severity, low-complexity, network-reachable vulnerability requiring only low privileges - specifically, HelmRelease create access in any single namespace. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker holding a valid cluster account with HelmRelease create permission in namespace `tenant-a` creates a HelmRelease manifest setting `secretRef.Namespace: kube-system` and `secretRef.Name: cloud-provider-credentials`, while pointing the Helm chart repository URL at an attacker-controlled server. When the RHACM HelmRelease controller reconciles the resource, it calls `GetSecret()` with the attacker-supplied namespace, retrieves the cloud provider credential Secret from `kube-system` without namespace authorization checks, and transmits the credential as part of the Helm repository authentication handshake to the attacker's server. … |
| Remediation | Apply the Red Hat errata for CVE-2026-73137 targeting the multicloud-operators-subscription component in RHACM 2.x; the exact fix version was not independently confirmed from available references, so consult https://access.redhat.com/security/cve/CVE-2026-73137 for the specific advisory package and upgrade path. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: inventory all RHACM-managed clusters and identify which enforce multi-tenant isolation; audit RBAC to determine how many service accounts or users hold HelmRelease create permissions across namespaces. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
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
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
Cross-cluster traffic redirection in Submariner (as shipped with Red Hat Advanced Cluster Management for Kubernetes 2) a
Privilege escalation in Red Hat Advanced Cluster Management for Kubernetes 2 stems from the search-v2-operator being bou
Cross-cluster traffic interception in Submariner (shipped within Red Hat Advanced Cluster Management for Kubernetes 2) a
Improper access control in Lighthouse - the cross-cluster service-discovery component of Submariner shipped with Red Hat
Cross-cluster remote code execution in Red Hat Advanced Cluster Management for Kubernetes 2 (acm-search-v2-rhel9 search
Same weakness CWE-200 – Information Exposure
View allSame technique Information Disclosure
View allVendor StatusVendor
Share
External POC / Exploit Code
Leaving vuln.today