github.com/projectcapsule/capsule vulnerabilities
- Registry
- Go
- Latest
- 0.15.2
21 known advisories
The latest version, 0.15.2, is affected by 1 of them.
Is your project on an affected github.com/projectcapsule/capsule?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for github.com/projectcapsule/capsule
Capsule: hostnameRegexHandler.OnUpdate validates stale (old) Tenant regex, allowing invalid AllowedHostnames regex to bypass webhook validation in github.com/projectcapsule/capsule
- Affected
- >=0.13.0 <0.13.7
- Fixed in
- 0.13.7
Capsule: Tenant owner bypasses Capsule's forbidden namespace/service/node label and annotation enforcement in github.com/projectcapsule/capsule
- Affected
- <0.13.7
- Fixed in
- 0.13.7
Capsule: Malformed ForbiddenAnnotations.Regex can bypass Tenant validation and trigger namespace admission panic in github.com/projectcapsule/capsule
- Affected
- >=0.13.0 <0.13.7
- Fixed in
- 0.13.7
Capsule: hostnameRegexHandler.OnUpdate validates stale (old) Tenant regex, allowing invalid AllowedHostnames regex to bypass webhook validation
- Affected
- >=0.13.0 <0.13.7
- Fixed in
- 0.13.7
Capsule: Tenant owner bypasses Capsule's forbidden namespace/service/node label and annotation enforcement
- Affected
- <0.13.7
- Fixed in
- 0.13.7
Capsule: Malformed ForbiddenAnnotations.Regex can bypass Tenant validation and trigger namespace admission panic
- Affected
- >=0.13.0 <0.13.7
- Fixed in
- 0.13.7
Capsule: CapsuleConfiguration NodeMetadata regex fields lack webhook validation, allowing MustCompile panic on all Node admission requests in github.com/projectcapsule/capsule
- Affected
- <0.13.8
- Fixed in
- 0.13.8
Capsule has an incomplete fix of CVE-2026-22872: TenantResource RawItems and Generators still allow cluster-scoped resource creation (cross-tenant privilege escalation) in github.com/projectcapsule/capsule
- Affected
- >=0.13.0 <0.13.8
- Fixed in
- 0.13.8
Capsule has an incomplete fix of CVE-2026-22872: TenantResource RawItems and Generators still allow cluster-scoped resource creation (cross-tenant privilege escalation)
- Affected
- >=0.13.0 <0.13.8
- Fixed in
- 0.13.8
Capsule: CapsuleConfiguration NodeMetadata regex fields lack webhook validation, allowing MustCompile panic on all Node admission requests
- Affected
- <0.13.8
- Fixed in
- 0.13.8
Capsule TenantResource RawItems Cluster-Scoped Resource Creation Vulnerability in github.com/projectcapsule/capsule
- Affected
- <0.13.0
- Fixed in
- 0.13.0
Capsule: Incomplete fix of CVE-2026-30963: singular/plural typo leaves namespaces/finalize unprotected in github.com/projectcapsule/capsule
- Affected
- >=0.13.0 <0.13.6
- Fixed in
- 0.13.6
Capsule: Incomplete fix of CVE-2026-30963: singular/plural typo leaves namespaces/finalize unprotected
- Affected
- >=0.13.0 <0.13.6
- Fixed in
- 0.13.6
Capsule Namespace Hijacking via subresource in github.com/projectcapsule/capsule
- Affected
- <0.13.0
- Fixed in
- 0.13.0
Capsule TenantResource RawItems Cluster-Scoped Resource Creation Vulnerability
- Affected
- <0.13.0
- Fixed in
- 0.13.0
Capsule Namespace Hijacking via subresource
- Affected
- <0.13.0
- Fixed in
- 0.13.0
Capsule tenant owners with "patch namespace" permission can hijack system namespaces label in github.com/projectcapsule/capsule
- Affected
- <0.10.4
- Fixed in
- 0.10.4
Capsule tenant owners with "patch namespace" permission can hijack system namespaces label
- Affected
- <0.10.4
- Fixed in
- 0.10.4
Capsule tenant owner with "patch namespace" permission can hijack system namespaces in github.com/projectcapsule/capsule
- Affected
- All versions
- Fixed in
- No fix released
Capsule tenant owner with "patch namespace" permission can hijack system namespaces
- Affected
- <0.7.1
- Fixed in
- 0.7.1
capsule-proxy service discloses Namespaces of colliding tenants to owners of different tenants with the same ServiceAccount name
- Affected
- <0.4.5
- Fixed in
- 0.4.5
Is your github.com/projectcapsule/capsule version vulnerable?
- github.com/projectcapsule/capsule 0.151 advisory in 0.15.2
- github.com/projectcapsule/capsule 0.141 advisory in 0.14.6
- github.com/projectcapsule/capsule 0.131 advisory in 0.13.11
- github.com/projectcapsule/capsule 0.129 advisories in 0.12.4
- github.com/projectcapsule/capsule 0.119 advisories in 0.11.2
- github.com/projectcapsule/capsule 0.109 advisories in 0.10.9
Which of your client projects still run an old github.com/projectcapsule/capsule?
NPMscan reads the go.mod in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Go packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Go registry.