Projectcapsule vulnerabilities
We track 5 vulnerabilities in Projectcapsule products across 2 products. 5 are rated high or critical, and none are known to be exploited. The most recent was published on September 18, 2026.
Latest Projectcapsule vulnerabilities
- 7.1 High severity
capsule: Incorrect Comparison
Capsule is a multi-tenancy and policy-based framework for Kubernetes. Prior to 0.13.7, ForbiddenListSpec.ExactMatch in pkg/api/forbidden_list.go sorts denied metadata keys case-insensitively and then uses sort.SearchStrings, which assumes byte-order sorting. W
- 9.1 Critical severity
Capsule is a multi-tenancy and policy-based framework for Kubernetes.
Capsule is a multi-tenancy and policy-based framework for Kubernetes. The Capsule Controller runs with cluster-admin privileges. Although the TenantResource RawItems processing logic forcibly sets the namespace, this is ineffective for cluster-scoped resources
- 9.0 Critical severity
capsule: Incorrect Authorization
Capsule is a multi-tenancy and policy-based framework for Kubernetes. A namespace label injection vulnerability in Capsule v0.10.3 and earlier allows authenticated tenant users to inject arbitrary labels into system namespaces (kube-system, default, capsule-sy
- 8.8 High severity
capsule: Incorrect Authorization
Capsule is a multi-tenancy and policy-based framework for Kubernetes. In Capsule v0.7.0 and earlier, the tenant-owner can patch any arbitrary namespace that has not been taken over by a tenant (i.e., namespaces without the ownerReference field), thereby gainin
- 9.8 Critical severity
capsule-proxy: Improper Authentication
capsule-proxy is a reverse proxy for the capsule operator project. Affected versions are subject to a privilege escalation vulnerability which is based on a missing check if the user is authenticated based on the `TokenReview` result. All the clusters running