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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 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
- 31 Oct 2026, 14:15 UTC First seen by agentprime
- 31 Oct 2026, 14:15 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-6758-979h-249x
- OSV: GHSA-6758-979h-249x
- github.com/projectcapsule/capsule-proxy/security/advisories/GHSA-6758-979h-249x
- nvd.nist.gov/vuln/detail/CVE-2023-46254
- github.com/projectcapsule/capsule-proxy/commit/615202f7b02eaec7681336bd63daed1f39ae00c5
- github.com/projectcapsule/capsule-proxy
- github.com/projectcapsule/capsule-proxy/releases/tag/v0.4.5