Is CVE-2026-53487 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-53487 being exploited in the wild.

How severe is CVE-2026-53487?

Medium severity, with a CVSS score of 4.3, published 21 August 2026.

Which products and versions are affected?

github.com/zxh326/kite (Go) <= 0.12.2, SEMVER:introduced=0,fixed=0.12.3.

Is there a fix for CVE-2026-53487?

Yes. github.com/zxh326/kite (Go): upgrade to 0.12.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-53487 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-53487?

Check whether you run github.com/zxh326/kite (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-53487: Kite RBAC bypass in /api/v1/overview

Q: Is there a fix for CVE-2026-53487?

Yes. github.com/zxh326/kite (Go): upgrade to 0.12.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-53487 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-53487?

Check whether you run github.com/zxh326/kite (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-53487 · Severity: medium · CVSS 4.3 · Published 2026-08-21

Kite, a tool for managing Kubernetes clusters, contains a security flaw where an authenticated user can view sensitive summary information about clusters they are not authorized to access. By manipulating a specific request header, a low-privileged user can see aggregate data such as the total number of nodes, pods, and namespaces in other clusters. This could lead to the exposure of infrastructure scale and resource utilization details to unauthorized personnel.

Technologies: github.com/zxh326/kite (Go). Vendors: Go.

Quick answers

Is CVE-2026-53487 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-53487 being exploited in the wild.
How severe is CVE-2026-53487?: Medium severity, with a CVSS score of 4.3, published 21 August 2026.
Which products and versions are affected?: github.com/zxh326/kite (Go) <= 0.12.2, SEMVER:introduced=0,fixed=0.12.3.
Is there a fix for CVE-2026-53487?: Yes. github.com/zxh326/kite (Go): upgrade to 0.12.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-53487 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-53487?: Check whether you run github.com/zxh326/kite (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/zxh326/kite (Go): upgrade to 0.12.3 or later
```
go get github.com/zxh326/kite@v0.12.3
```

Technical details

A missing authorization check in the `/api/v1/overview` endpoint allows authenticated users to bypass Role-Based Access Control (RBAC) boundaries. The vulnerability exists because the overview route is registered before the global `RBACMiddleware` is applied in `routes.go`. Additionally, the `GetOverview` handler only verifies that a user has at least one role, failing to validate if the user has permissions for the specific cluster requested via the `x-cluster-name` header. An attacker with valid credentials for one cluster can retrieve aggregate data (nodes, pods, namespaces, services, and CPU/memory capacity) for any other configured cluster. The issue is fixed in version 0.12.3.

Affected products

zxh326 kite <= 0.12.2

Identifiers

CVE-2026-53487
GHSA-gvhc-wv3v-7pf8
GO-2026-5941

Timeline

2026-05-31: disclosed: Initial report to vendor
2026-07-07: advisory: GitHub Advisory published
2026-07-07: patched: Fix released in version 0.12.3

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.