# GO-2026-5010 - Kong Ingress Controller for Kubernetes (KIC): Secret-backed plugin configurations leak through non-sensitive diagnostics endpoint in github.

Source: https://junglewise.ai/threats/go-2026-5010-kong-ingress-controller-for-kubernetes-kic-secret-backed-6a1237f0  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-05-20  
License: CC BY 4.0 with a link back

Severity: info · Published 2026-05-20

Kong Ingress Controller for Kubernetes (KIC): Secret-backed plugin configurations leak through non-sensitive diagnostics endpoint in github.com/kong/kubernetes-ingress-controller

Technologies: [github.com/kong/kubernetes-ingress-controller (Go)](https://junglewise.ai/threats/technologies/github-com-kong-kubernetes-ingress-controller), [github.com/kong/kubernetes-ingress-controller/v2 (Go)](https://junglewise.ai/threats/technologies/github-com-kong-kubernetes-ingress-controller-v2), [github.com/kong/kubernetes-ingress-controller/v3 (Go)](https://junglewise.ai/threats/technologies/github-com-kong-kubernetes-ingress-controller-v3). Vendors: [Go](https://junglewise.ai/threats/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?** Informational severity, published 20 May 2026.

**Which products and versions are affected?** github.com/kong/kubernetes-ingress-controller (Go) SEMVER:introduced=0; github.com/kong/kubernetes-ingress-controller/v2 (Go) SEMVER:introduced=0; github.com/kong/kubernetes-ingress-controller/v3 (Go) SEMVER:introduced=0,fixed=3.5.7.

**Is there a fix for This vulnerability?** Yes. github.com/kong/kubernetes-ingress-controller/v3 (Go): upgrade to 3.5.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected?** Check whether you run github.com/kong/kubernetes-ingress-controller (Go), github.com/kong/kubernetes-ingress-controller/v2 (Go) or github.com/kong/kubernetes-ingress-controller/v3 (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/kong/kubernetes-ingress-controller/v3 (Go): upgrade to 3.5.7 or later

  ```sh
  go get github.com/kong/kubernetes-ingress-controller/v3@v3.5.7
  ```


## Affected products

- github.com/kong/kubernetes-ingress-controller (Go) SEMVER:introduced=0
- github.com/kong/kubernetes-ingress-controller/v2 (Go) SEMVER:introduced=0
- github.com/kong/kubernetes-ingress-controller/v3 (Go) SEMVER:introduced=0,fixed=3.5.7

## Related threats

- [GO-2026-5485 - Kong Ingress Controller for Kubernetes (KIC): Cross-namespace TLS Secret Exfiltration in Gateways with…](https://junglewise.ai/threats/go-2026-5485-kong-ingress-controller-for-kubernetes-kic-cross-namespace-2257cba3)
- [Kong Ingress Controller sensitive information leak in diagnostics endpoint](https://junglewise.ai/threats/kong-ingress-controller-sensitive-information-leak-in-diagnostics-6c22a38f)
