Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.1amended

Capsule: Tenant owner bypasses Capsule's forbidden namespace/service/node label and annotation enforcement

CVE-2026-61672GHSA-gjw4-3v3v-rqxg

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/projectcapsule/capsule 0.13.7), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.1 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:H/A:N
EPSS
  • CVE-2026-61672: 0.33% estimated exploitation activity in the next 30 days; percentile 26.82 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary Capsule lets a cluster administrator forbid specific metadata keys that tenant owners must not place on their own resources: Tenant.spec.namespaceOptions.forbiddenLabels / forbiddenAnnotations (namespaces), Tenant.spec.serviceOptions.forbiddenLabels / forbiddenAnnotations (Services), and the cluster-wide forbidden worker-node labels/annotations. These lists are an isolation control — they exist to stop a tenant owner from setting metadata that other controllers or admission plugins key on (Pod Security Admission labels, kubernetes.io/metadata.name, LoadBalancer/externalIP service annotations, scheduler annotations, vendor labels that grant network reach, etc.). The validating webhooks enforce them through api.ValidateForbidden, which calls ForbiddenListSpec.ExactMatch(key) for every key the tenant submits. ExactMatch is broken. It sorts the denied list case-insensitively (sort.SliceStable with a strings.ToLower comparator) and then performs a byte-order binary search…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-gjw4-3v3v-rqxg

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6520

  3. Revision 1 · created ·

    Published from osv record GHSA-gjw4-3v3v-rqxg

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-61672

Advisory: Capsule: Tenant owner bypasses Capsule's forbidden namespace/service/node label and annotation enforcement
IDs: CVE-2026-61672, GHSA-gjw4-3v3v-rqxg
Record: https://patchnext.com/advisories/cve-2026-61672 (revision 3, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/projectcapsule/capsule 0.13.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/projectcapsule/capsule: affected <= 0.13.6; fixed in 0.13.7

## Suggested inspection (read-only)
- Go github.com/projectcapsule/capsule: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/projectcapsule/capsule.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-gjw4-3v3v-rqxg (OSV record GHSA-gjw4-3v3v-rqxg lists affected ranges: Go github.com/projectcapsule/capsule >=0 <0.13.7 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6520 (OSV record GO-2026-6520 lists affected ranges: Go github.com/projectcapsule/capsule >=0 <0.13.7 (fixed))
- Verified: https://github.com/advisories/GHSA-gjw4-3v3v-rqxg (GitHub-reviewed advisory GHSA-gjw4-3v3v-rqxg lists affected ranges: Go github.com/projectcapsule/capsule >=0 <=0.13.6)

Commands are suggestions: review each one before running it.

Loading voting…