CVE-2026-61794 json
Capsule: Malformed ForbiddenAnnotations.Regex can bypass Tenant validation and trigger namespace admission panic
published last mo. modified last mo. also EUVD-2026-83055 , GHSA-gxjc-74v5-3vx3 , GO-2026-6521
- cvss
- 6.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 48%
- public exploits
- 0
- none known
Summary
Capsule is a multi-tenancy and policy-based framework for Kubernetes. From 0.13.0 until 0.13.7, the Tenant update validation in internal/webhook/tenant/validation/forbidden_annotations_regex.go compiles ForbiddenLabels.Regex for both the labels and annotations checks instead of validating ForbiddenAnnotations.Regex. An administrator who can update a Tenant can therefore persist a malformed ForbiddenAnnotations.Regex while leaving the labels expression valid. Namespace creation or update later passes the stored expression through pkg/api/forbidden_list.go, where regexp.MustCompile can panic during forbidden metadata validation and deny namespace operations for the affected tenant. 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-61794 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.59% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/projectcapsule/capsule/security/advisories/GHSA-gxjc-74v5-3vx3 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.8 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H |
| GitHub | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/projectcapsule/capsule | >=0.13.0, <0.13.7 |
0.13.7 |
Affected products
- projectcapsule capsule
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
github.com
/projectcapsule/capsule/pull/1983
web, patch
-
github.com
/projectcapsule/capsule/commit/8d89d6865df6f41c7faa22fc9e807a57b01bfd0e
web, patch
-
github.com
/projectcapsule/capsule/security/advisories/GHSA-gxjc-74v5-3vx3
exploit, web, advisory
-
github.com
/projectcapsule/capsule/releases/tag/v0.13.7
web
-
github.com
/projectcapsule/capsule
package
Sources
- CVE List CVE-2026-61794
- GitHub Advisory GHSA-gxjc-74v5-3vx3
- NVD CVE-2026-61794
- OSV GO-2026-6521
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.