Capsule Tenant Metadata Enforcement Bypass Identified

The GitHub Security Advisory database has disclosed a high-severity vulnerability in projectcapsule/capsule, published on September 18, 2026. This issue allows tenant owners to bypass Capsule's enforcement of forbidden namespace, service, and node metadata keys, which are intended to isolate tenants and prevent metadata-driven cross-tenant or system effects. The vulnerability stems from a flaw in the `ExactMatch` function used by Capsule's validating webhooks. Specifically, the function incorrectly sorts the forbidden metadata list case-insensitively but performs a byte-order binary search, leading to false negatives when the list mixes uppercase and lowercase keys. As a result, tenant owners can set metadata keys explicitly prohibited by the cluster administrator.

Operators should carefully review their current configurations for forbidden metadata lists and check for any mixed-case entries, as these are particularly susceptible to this bug. Additionally, they should monitor tenant activity for any unexpected metadata keys that could exploit this vulnerability. If upgrading to a patched version is not immediately possible, administrators may need to implement temporary external controls or monitoring to mitigate the risk of cross-tenant interference. This issue highlights the importance of validating isolation controls in multi-tenant environments, as similar vulnerabilities could arise in other projects relying on metadata enforcement mechanisms.