Advisory record · GHSA-6758-979h-249x

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

CVSS 4.3 MediumEPSS 0.0050 · 43rd percentile

Published by the GitHub Advisory Database at 7 Nov 2023, 21:46 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/projectcapsule/capsuleGo<0.4.50.4.5
github.com/projectcapsule/capsule-proxyGo<0.4.50.4.5
Identifiers
GHSA-6758-979h-249x · CVE-2023-46254
Weakness (CWE)
CWE-200
Published
7 Nov 2023
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Two packages, capsule and capsule-proxy, are affected in versions before 0.4.5; upgrade both to 0.4.5. In capsule-proxy, a ServiceAccount tenant owner can list Namespaces belonging to other tenants whose owner is a ServiceAccount with the same name in a different Namespace. This requires capsule-proxy to run with caching enabled, which is the default. The source does not list a workaround, and it says Kubernetes RBAC still prevents privilege escalation on Namespace-scoped resources.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0050, the 43rd percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:15 UTC First seen by agentprime
  2. 31 Oct 2026, 14:15 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.