Is This vulnerability exploited in the wild?

No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

How severe is This vulnerability?

Medium severity, with a CVSS score of 6.5, published 24 July 2026.

Which products and versions are affected?

github.com/zxh326/kite (Go) >= 0.6.9, <= 0.14.0.

Is there a fix for This vulnerability?

A patch was published on 2026-07-19: Fix merged into main branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is This vulnerability attacked?

It is attacked over the network, in a network appliance.

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.

Kite Kubernetes proxy path traversal in API endpoints

Q: Is there a fix for This vulnerability?

A patch was published on 2026-07-19: Fix merged into main branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is This vulnerability attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected?

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.

Severity: medium · CVSS 6.5 · Published 2026-07-24

Kite, a Kubernetes management tool, contains a vulnerability in how it handles proxy requests to cluster resources. An authenticated user with limited access to a single namespace can use specially crafted web requests to bypass security boundaries and view sensitive information across the entire cluster, including secrets and configuration data. This could lead to the exposure of credentials or other private data managed by the Kubernetes environment.

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

Quick answers

Is This vulnerability exploited in the wild?: No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?: Medium severity, with a CVSS score of 6.5, published 24 July 2026.
Which products and versions are affected?: github.com/zxh326/kite (Go) >= 0.6.9, <= 0.14.0.
Is there a fix for This vulnerability?: A patch was published on 2026-07-19: Fix merged into main branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?: It is attacked over the network, in a network appliance.
Am I affected?: 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.

Technical details

A path traversal vulnerability exists in Kite versions 0.6.9 through 0.14.0 due to improper canonicalization of URL paths before authorization. The application performs RBAC checks against the original namespace and resource parameters but subsequently decodes the proxy path and passes it to url.JoinPath, which resolves '..' segments. An attacker with 'get' permissions on pods or services in one namespace can use encoded traversal segments (e.g., %2e%2e/) to reach different Kubernetes API endpoints. This allows the disclosure of cluster-wide resources using Kite's service account permissions. The issue is fixed in version 0.14.1.

Affected products

kite-org Kite 0.6.9 - 0.14.0

Timeline

2026-07-19: patched: Fix merged into main branch
2026-07-23: disclosed: Initial advisory publication
2026-07-24: advisory: GitHub reviewed advisory published

References

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