CVE-2026-30963
- Source
- https://cve.org/CVERecord?id=CVE-2026-30963
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-30963.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-30963
- Aliases
- Published
- 2026-06-01T18:00:43.797Z
- Modified
- 2026-07-08T08:12:26.724689987Z
- Severity
-
- 3.9 (Low) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:L CVSS Calculator
- Summary
- Capsule Namespace Hijacking via subresource
- Details
-
Capsule is a multi-tenancy and policy-based framework for Kubernetes. To defend against namespace hijacking achieved through update/patch operations on namespaces, Capsule uses a webhook to validate update requests targeting namespaces. However, in Kubernetes, the namespace/finalize and namespace/status subresource APIs can also modify various fields of a namespace, including the metadata field. Prior to version 0.13.0, the webhook does not define interception rules for these subresources. As a result, if a tenant administrator has permission to modify namespace/status or namespace/finalize, they can successfully perform namespace hijacking. Version 0.13.0 fixes the issue. Another mitigation is to add two subresources (namespaces and snamespaces/status with namespace/finalize within it) to the resources list in the ValidatingWebhookConfiguration rules.
- Database specific
{ "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/30xxx/CVE-2026-30963.json", "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-20" ] }- References
Affected packages
Git / github.com/projectcapsule/capsule
Affected ranges
- Type
- GIT
- Repo
- https://github.com/projectcapsule/capsule
- Events
-
Introduced0 Unknown introduced commit / All previous commits are affectedFixed
- Database specific
{ "source": [ "AFFECTED_FIELD", "CPE_RANGE", "REFERENCES" ], "cpe": "cpe:2.3:a:projectcapsule:capsule:*:*:*:*:*:*:*:*", "extracted_events": [ { "introduced": "0" }, { "fixed": "0.13.0" } ] }