Namespace hijacking via skipped owner-reference validation
Published Aug 20, 2024 · Updated Aug 14, 2025
Incorrect authorization in Capsule 0.7.0 and earlier allows remote authenticated users to seize unowned Kubernetes namespaces. The owner-reference update webhook returns without validation when the existing namespace has no ownerReferences, allowing a tenant owner to add the tenant as controller. Tenant-owner status, namespace patch permission, and a direct PATCH request are required; exploitation grants control of targets such as kube-system.
Summary
What happened
Incorrect authorization in Capsule 0.7.0 and earlier allows remote authenticated users to seize unowned Kubernetes namespaces. The owner-reference update webhook returns without validation when the existing namespace has no ownerReferences, allowing a tenant owner to add the tenant as controller. Tenant-owner status, namespace patch permission, and a direct PATCH request are required; exploitation grants control of targets such as kube-system.
The record
- CVE
- CVE-2024-39690
- Published
- Aug 20, 2024
- Updated
- Aug 14, 2025
- Vendor
- Clastix
- Product
- Capsule
- Classifications
- CWE-863
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 20, 2024CVE publishedPublication date reported by the CVE source.
- Aug 14, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=0.7.0
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
- Namespace ownerReference patch reproductionproof of concept · demonstrated
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