capsule-proxy service discloses Namespaces of colliding tenants to owners of different tenants with the same ServiceAccount name

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2023-46254: 0.41% estimated exploitation activity in the next 30 days; percentile 35.82 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A bug in the RoleBinding reflector used by capsule-proxy gives ServiceAccount tenant owners the right to list Namespaces of other tenants backed by the same owner kind and name. Details - Tenant solar, owned by a ServiceAccount named tenant-owner in the Namespace solar - Tenant wind, owned by a ServiceAccount named tenant-owner in the Namespace wind Please, notice the same ServiceAccount name, although in different namespaces. The Tenant owner solar would be able to list the namespaces of the Tenant wind and vice-versa, although this is not correct. The bug introduces an exfiltration vulnerability since allows the listing of Namespace resources of other Tenants, although just in some specific conditions: 1. capsule-proxy runs with the --disable-caching=false (default value: false) 2. Tenant owners are ServiceAccount, with the same resource name, but in different Namespaces. The CVE doesn't allow any privilege escalation on the outer tenant Namespace-scoped resources, since…

Published by the source

7 Nov 2023, 21:46 UTC

Last modified by the source

7 Nov 2023, 21:46 UTC

Source last checked

26 Oct 2026, 14:59 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6758-979h-249x

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

# Patch Next advisory brief: CVE-2023-46254

Advisory: capsule-proxy service discloses Namespaces of colliding tenants to owners of different tenants with the same ServiceAccount name
IDs: CVE-2023-46254, GHSA-6758-979h-249x
Record: https://patchnext.com/advisories/cve-2023-46254 (revision 1, source checked 26 Oct 2026, 14:59 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
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.4.5; github.com/projectcapsule/capsule-proxy 0.4.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/projectcapsule/capsule: affected <= 0.4.4; fixed in 0.4.5
- Go github.com/projectcapsule/capsule-proxy: affected <= 0.4.4; fixed in 0.4.5

## Suggested inspection (read-only)
- Go github.com/projectcapsule/capsule: check the installed version with your package manager.
- Go github.com/projectcapsule/capsule-proxy: 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, github.com/projectcapsule/capsule-proxy.
- 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://github.com/advisories/GHSA-6758-979h-249x (GitHub-reviewed advisory GHSA-6758-979h-249x lists affected ranges: Go github.com/projectcapsule/capsule >=0 =0 <=0.4.4)

Commands are suggestions: review each one before running it.