Cluster-wide privilege escalation via wildcard ServiceAccount RBAC
Published Aug 12, 2026 · Updated Aug 12, 2026
Privilege escalation in Red Hat Advanced Cluster Management for Kubernetes allows remote authenticated users to gain cluster-wide control. The application-manager add-on binds its ServiceAccount to default wildcard RBAC and honors tenant-created Subscription CRs with those privileges. Namespace-admin access on a managed cluster is sufficient to create arbitrary cluster-scoped resources, including workloads that execute code beyond the tenant namespace.
Summary
What happened
Privilege escalation in Red Hat Advanced Cluster Management for Kubernetes allows remote authenticated users to gain cluster-wide control. The application-manager add-on binds its ServiceAccount to default wildcard RBAC and honors tenant-created Subscription CRs with those privileges. Namespace-admin access on a managed cluster is sufficient to create arbitrary cluster-scoped resources, including workloads that execute code beyond the tenant namespace.
The record
- CVE
- CVE-2026-72508
- Published
- Aug 12, 2026
- Updated
- Aug 12, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Advanced Cluster Management for Kubernetes
- Classifications
- CWE-250, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 12, 2026CVE publishedPublication date reported by the CVE source.
- Aug 12, 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?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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