Vulnerability in github.com/zxh326/kite (CVE-2026-53487)
Summary
Vulnerability in github.com/zxh326/kite (CVE-2026-53487). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/v1/overview. Mitigation: upgrade to 0.12.3 or later.
Original description
The description as published by the source.
Summary
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.
The issue is present on current main commit 38c9bb9d4b746c0d2a8252f3c35cdfa07ab01c21 and latest release v0.12.2 at commit 0aae35abb2d6a8adf623fe60349261aa48753ccc.
Impact
A low-privileged user who only has access to one cluster can set x-cluster-name to another configured cluster and retrieve aggregate inventory and resource sizing data for that cluster. The response includes total node, pod, namespace, service, CPU, and memory values. This bypasses the cluster membership boundary used elsewhere in Kite.
The validated impact is confidentiality only. I did not prove Kubernetes mutation, pod names, secret values, kubeconfig contents, or bearer token exposure through this endpoint.
Technical details
routes.go registers /api/v1/overview before the global RBAC middleware is applied:
routes.go:131-133:/api/v1getsRequireAuth()andClusterMiddleware(cm).routes.go:135:/api/v1/overviewis registered.routes.go:171:api.Use(middleware.RBACMiddleware())is applied only after overview and several other routes are registered.
`pkg/middleware/cluster.go:21…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-53487 has been found in github.com/zxh326/kite.
Attackers can target a specific entry point like GET /api/v1/overview over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade github.com/zxh326/kite to 0.12.3 or later.
If unsure, ask your IT team or search "github.com/zxh326/kite CVE-2026-53487" on the vendor's site.
CVE-2026-53487 (github.com/zxh326/kite) — CWE-862 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/v1/overview / GetOverview / routes.go / ClientSet
Patched: 0.12.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in github.com/zxh326/kite. Attackers reach the vulnerable code path via GET /api/v1/overview.
Check the vendor advisory for the affected versions of github.com/zxh326/kite. Attack surface: GET /api/v1/overview / GetOverview / routes.go / ClientSet.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 0.12.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/v1/overview requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/zxh326/kite' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/zxh326/kite' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/zxh326/kiteを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/v1/overview' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/v1/overviewへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/zxh326/kite to 0.12.3ステージング環境で 0.12.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/v1/overview on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com