Cluster-wide privilege escalation via mismatched curator identity
Published Aug 12, 2026 · Updated Aug 25, 2026
Improper privilege management in Red Hat multicluster engine allows remote authenticated users to gain cluster-wide control. The cluster-curator-controller accepts a ClusterCurator whose name and namespace differ, then creates a cluster-scoped ClusterRoleBinding. Namespace-local permission to create that resource is sufficient; the resulting binding permits secrets access and modification, cluster actions, and deletion of hosted clusters or node pools.
Summary
What happened
Improper privilege management in Red Hat multicluster engine allows remote authenticated users to gain cluster-wide control. The cluster-curator-controller accepts a ClusterCurator whose name and namespace differ, then creates a cluster-scoped ClusterRoleBinding. Namespace-local permission to create that resource is sufficient; the resulting binding permits secrets access and modification, cluster actions, and deletion of hosted clusters or node pools.
The record
- CVE
- CVE-2026-73269
- Published
- Aug 12, 2026
- Updated
- Aug 25, 2026
- Vendor
- 389 Directory Server
- Product
- multicluster engine for Kubernetes
- Classifications
- CWE-269, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 12, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 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