Database/Container, Kubernetes & orchestration
Capsule: webhook rule typo lets a tenant user retag a namespace and cross tenant boundaries
Impact
Capsule's Helm chart registered its validating webhook against the resource name namespace/finalize instead of namespaces/finalize, so a PUT to /api/v1/namespaces/{namespace}/finalize never matches the rule and the webhook is simply not invoked. A user holding namespaces/finalize RBAC can therefore change the namespace's tenant label - the exact field Capsule uses to decide which tenant owns a namespace. On a shared GPU cluster where Capsule is the thing keeping teams apart, that means a namespace can be moved under a different tenant, taking its quotas, node pools and policy set with it. matchPolicy: Equivalent does not save you here, since it reconciles API group and version, not a misspelled resource name. Affects 0.13.0 through 0.13.5.
Who can reach it
An authenticated cluster user who already holds namespaces/finalize permission on a namespace; no node access needed, just the Kubernetes API.
What to do
Upgrade Capsule to 0.13.6, which corrects the webhook resource name in charts/capsule/templates/configuration.yaml. This is a chart/controller update - roll the Helm release and let the webhook configuration re-apply; no node drain or reboot. Until then, audit who holds namespaces/finalize and review namespace tenant labels for unexpected changes.
References
Related entries
- BuildKit: NTFS junctions inside the cache root escape the cache mount on Windows container workersCVE-2026-15788 · BuildKitMedium
- containerd: CRI checkpoint import does not validate image references in checkpoint metadataCVE-2026-50195 · containerdMedium
- Kubernetes (kubelet): Pod writes to its own /etc/hosts unaccounted for in evictionCVE-2020-8557 · Kubernetes (kubelet)Medium
- Calico: Route hijacking via the floating IP featureCVE-2022-28224 · CalicoMedium
- containerd: Unbounded memory consumption in containerd daemon via repeated ExecSyncCVE-2022-31030 · containerdMedium
- cosign / sigstore: Multiple verify-blob flaws cause successful verification of unsigned or wrongly-signed artifactsCVE-2022-36056 · cosign / sigstoreMedium
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.