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

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

- **Identifiers:** `GHSA-6758-979h-249x` · `CVE-2023-46254`
- **State:** Confirmed
- **Severity:** CVSS 4.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 7 Nov 2023
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

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.

## Affected packages

- `github.com/projectcapsule/capsule` (Go): affected `<0.4.5`; fixed in `0.4.5`
- `github.com/projectcapsule/capsule-proxy` (Go): affected `<0.4.5`; fixed in `0.4.5`

## 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

- 4.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`, from 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](https://osv.dev/vulnerability/GHSA-6758-979h-249x)

## Sources

- [GitHub Advisory Database: GHSA-6758-979h-249x](https://github.com/advisories/GHSA-6758-979h-249x)
- [OSV: GHSA-6758-979h-249x](https://osv.dev/vulnerability/GHSA-6758-979h-249x)
- <https://github.com/projectcapsule/capsule-proxy/security/advisories/GHSA-6758-979h-249x>
- <https://nvd.nist.gov/vuln/detail/CVE-2023-46254>
- <https://github.com/projectcapsule/capsule-proxy/commit/615202f7b02eaec7681336bd63daed1f39ae00c5>
- <https://github.com/projectcapsule/capsule-proxy>
- <https://github.com/projectcapsule/capsule-proxy/releases/tag/v0.4.5>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-6758-979h-249x>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-6758-979h-249x/>. Everything for agents: <https://agentprime.io/llms.txt>.
