Authenticated ManagedCluster deletion via unchecked namespace field
Published Aug 21, 2026 · Updated Aug 25, 2026
Authorization bypass in Red Hat multicluster engine for Kubernetes allows remote authenticated users to delete any ManagedCluster. The deleteResources() function treats tenant-controlled ClusterClaim spec.namespace as the target name without verifying ownership. Standard ClusterClaim create and delete permissions suffice to remove the hub local-cluster or another tenant's cluster, interrupting cluster management.
Summary
What happened
Authorization bypass in Red Hat multicluster engine for Kubernetes allows remote authenticated users to delete any ManagedCluster. The deleteResources() function treats tenant-controlled ClusterClaim spec.namespace as the target name without verifying ownership. Standard ClusterClaim create and delete permissions suffice to remove the hub local-cluster or another tenant's cluster, interrupting cluster management.
The record
- CVE
- CVE-2026-73267
- Published
- Aug 21, 2026
- Updated
- Aug 25, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-602, T1485
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 21, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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