Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

Kite Kubernetes proxy path traversal allows authenticated users to bypass RBAC and read cluster-wide resourcesGHSA-c534-2w9c-x7fm

MEDIUMFix: kite-org/kite#638

GHSA-c534-2w9c-x7fm is a medium-severity (CVSS 6.5) vulnerability in github.com/zxh326/kite. A fix is available for github.com/zxh326/kite — see the affected versions and patch details below.

Also known asGO-2026-6105
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Aug 18, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐹github.com/zxh326/kite

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

Kite versions 0.6.9 through 0.14.0 authorize Kubernetes proxy requests against the pod or service identified by the original route parameters. Encoded path traversal segments can cause the upstream URL to resolve to a different Kubernetes API endpoint after authorization.

Impact

An authenticated user with get permission on pods or services in one namespace can cause Kite to issue GET requests to Kubernetes API endpoints outside that namespace using Kite's service account.

With Kite's default Helm RBAC configuration, this allows cluster-wide resource disclosure, including Secrets. The validated impact is confidentiality only; resource modification and denial of service were not demonstrated.

Deployments using a restricted Kite service account are affected only up to the permissions granted to that service account.

Technical details

The authorization check is performed against the original namespace and kind route parameters. The proxy path is subsequently decoded and passed to url.JoinPath, which resolves .. segments and can produce an upstream URL outside the authorized pod or service proxy prefix.

Two input locations were affected:

  1. Encoded traversal segments in the proxy catch-all path.
  2. Encoded traversal and slash characters in the resource name.

Reproduction

  1. Create a user with a role granting only pods:get in namespace default.
  2. Create any pod in default (e.g. nginx).
  3. Send the following request (auth cookie required):
curl --path-as-is --cookie "auth_token=<JWT>" \
  'http://<kite-host>/api/v1/_clusters/<cluster>/namespaces/default/pods/nginx/proxy/%2e%2e/%2e%2e/%2e%2e/%2e%2e/kube-system/secrets'

Patches

Fixed in Kite 0.14.1.

Workarounds

Upgrade to 0.14.1 or later.

If upgrading is temporarily impossible, reject encoded dot segments and encoded slashes at the reverse proxy and restrict Kite's Kubernetes service account permissions. Reverse-proxy normalization should not be treated as a permanent fix.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/zxh326/kite≥ 0.6.9&&< 0.14.10.14.1go get github.com/zxh326/kite@v0.14.1

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/zxh326/kite, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/zxh326/kite to 0.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c534-2w9c-x7fm is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

## Summary Kite versions 0.6.9 through 0.14.0 authorize Kubernetes proxy requests against the pod or service identified by the original route parameters. Encoded path traversal segments can cause the upstream URL to resolve to a different Kubernetes API endpoint after authorization. ## Impact An authenticated user with `get` permission on pods or services in one namespace can cause Kite to issue GET requests to Kubernetes API endpoints outside that namespace using Kite's service account. With Kite's default Helm RBAC configuration, this allows cluster-wide resource disclosure, including Se
O3 Security · Impact-Aware SCA

Is GHSA-c534-2w9c-x7fm in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Kite Kubernetes proxy path traversal allows authenticated…