Projectcapsule maintains the Capsule multi-tenancy and resource-sharing solution for Kubernetes, with its disclosed vulnerabilities centering on input validation and authorization controls within the tenant-isolation layer. The observed weakness classes reflect the authentication and access-control boundaries critical to a multi-tenant platform; current severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Projectcapsule over time
Signals from CVEs in this vendor scope (3 CVEs).
3 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2026-22872CRITICAL Capsule is a multi-tenancy and policy-based framework for Kubernetes. The Capsule Controller runs with cluster-admin privileges. Although the TenantResource RawItems processing log | Jun 1, 2026 | 9.1 | 40 | NO | NO |
CVE-2024-39690HIGH 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 | Aug 20, 2024 | 8.8 | 24 | NO | NO |
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 w | Jun 1, 2026 | 2.7 | 19 | NO | NO |
Signals from CVEs in this vendor scope (3 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Projectcapsule.
Media articles that mention a CVE ID that affects a product developed by Projectcapsule — matched by CVE ID, not by vendor name.