Cross-namespace secret exfiltration via secretRef.Namespace
Published Aug 20, 2026 · Updated Aug 20, 2026
Information disclosure in RHACM allows remote authenticated users to read cross-namespace Secrets through HelmRelease creation. In Red Hat Advanced Cluster Management's multicloud-operators-subscription component, the HelmRelease controller's GetSecret() function trusts the tenant-controlled secretRef.Namespace field and uses the controller's privileged client to fetch a Secret from any namespace, then sends those credentials as HTTP Basic Auth to the referenced Helm repository. Exploitation requires permission to create HelmRelease resources, and the published record bounds the impact to unauthorized disclosure of Secret data from other namespaces.
Summary
What happened
Information disclosure in RHACM allows remote authenticated users to read cross-namespace Secrets through HelmRelease creation. In Red Hat Advanced Cluster Management's multicloud-operators-subscription component, the HelmRelease controller's GetSecret() function trusts the tenant-controlled secretRef.Namespace field and uses the controller's privileged client to fetch a Secret from any namespace, then sends those credentials as HTTP Basic Auth to the referenced Helm repository. Exploitation requires permission to create HelmRelease resources, and the published record bounds the impact to unauthorized disclosure of Secret data from other namespaces.
The record
- CVE
- CVE-2026-73137
- Published
- Aug 20, 2026
- Updated
- Aug 20, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Advanced Cluster Management for Kubernetes
- Classifications
- CWE-200
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 20, 2026CVE publishedPublication date reported by the CVE source.
- Aug 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo