Namespace hijacking via unvalidated subresource metadata
Published Jun 1, 2026 · Updated Jun 1, 2026
Improper input validation in Project Capsule's Capsule before 0.13.0 allows remote authenticated users to hijack Kubernetes namespaces. The validating webhook omits namespace/status and namespace/finalize from its interception rules, so PATCH requests can replace namespace ownerReferences without Capsule's ownership check. Exploitation requires tenant-administrator RBAC permission to modify either subresource and reassigns a namespace to an attacker-controlled tenant.
Summary
What happened
Improper input validation in Project Capsule's Capsule before 0.13.0 allows remote authenticated users to hijack Kubernetes namespaces. The validating webhook omits namespace/status and namespace/finalize from its interception rules, so PATCH requests can replace namespace ownerReferences without Capsule's ownership check. Exploitation requires tenant-administrator RBAC permission to modify either subresource and reassigns a namespace to an attacker-controlled tenant.
The record
- CVE
- CVE-2026-30963
- Published
- Jun 1, 2026
- Updated
- Jun 1, 2026
- Vendor
- Project Capsule
- Product
- Capsule
- Classifications
- CWE-20, T1068
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jun 1, 2026CVE publishedPublication date reported by the CVE source.
- Jun 1, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.13.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 status PATCH proof of conceptproof 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