CVE-2026-61672 json
Capsule: Tenant owner bypasses Capsule's forbidden namespace/service/node label and annotation enforcement
published last mo. modified last mo. also EUVD-2026-83164 , GHSA-gjw4-3v3v-rqxg , GO-2026-6520
- cvss
- 7.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
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. When an administrator's forbidden list mixes capitalized and lowercase keys or otherwise has different case-insensitive and byte ordering, the binary search can return false for a key that is present. An authenticated tenant owner can then pass the missed key through api.ValidateForbidden and bypass configured namespace, Service, or delegated node metadata restrictions, potentially influencing cluster policies, network exposure, or scheduling outside the tenant boundary. Uniformly lowercase lists whose two orderings coincide are not affected. This issue is fixed in version 0.13.7.
Patch / fix
- go github.com/projectcapsule/capsule 0.13.7
- clastix capsule 0.13.7
Is CVE-2026-61672 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.33% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/projectcapsule/capsule/security/advisories/GHSA-gjw4-3v3v-rqxg referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:H/A:N |
| GitHub | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/projectcapsule/capsule | <0.13.7 |
0.13.7 |
Affected products
- projectcapsule capsule
Classification
References
-
github.com
/projectcapsule/capsule/pull/1982
web, patch
-
github.com
/projectcapsule/capsule/commit/755cef54bf4a1bc56d6692130132bc70755bef46
web, patch
-
github.com
/projectcapsule/capsule/security/advisories/GHSA-gjw4-3v3v-rqxg
exploit, web, advisory
-
github.com
/projectcapsule/capsule/releases/tag/v0.13.7
web
-
github.com
/projectcapsule/capsule
package
Sources
- CVE List CVE-2026-61672
- GitHub Advisory GHSA-gjw4-3v3v-rqxg
- NVD CVE-2026-61672
- OSV GO-2026-6520
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.