github.com/kong/kubernetes-ingress-controller/v3
Affected
- introduced
0, fixed3.5.7(semver)
Fixed versions
3.5.7
Fix
- Fixed version
3.5.7go get github.com/kong/kubernetes-ingress-controller/[email protected]
Advisory
Also known as: GO-2026-5010
Kong Ingress Controller for Kubernetes (KIC): Secret-backed plugin configurations leak through non-sensitive diagnostics endpoint
Summary
A vulnerability in the Kong Ingress Controller (KIC) allows for the unauthorized exposure of sensitive plugin credentials through the diagnostics interface. Even when configured to redact sensitive information (using --dump-sensitive-config=false), KIC fails to sanitize the Plugins field in diagnostic configuration dumps. This causes secrets referenced via configFrom.secretKeyRef to be resolved and displayed in plaintext.
Because the diagnostics HTTP endpoints require no authentication, any process within the cluster network capable of reaching the KIC pod can exfiltrate sensitive data, including API keys, bearer tokens, and database passwords.
Am I affected?
You are affected if all of the following hold:
--dump-config=true).--dump-sensitive-config=false), creating an expectation of redaction.KongPlugin or KongClusterPlugin resources that reference Kubernetes Secrets via `configFrom.secretKeyRef`.10256) is reachable by other workloads or users within your cluster.You are not affected if:
--dump-config flag is set to false (default behavior).Mitigation
--dump-config=false.NetworkPolicy to restrict access to the KIC diagnostics port (default 10256), ensuring only authorized administrative pods or IPs can reach it.kubectl port-forward RBAC permissions to prevent unauthorized users from accessing the pod's local ports.Fix
The fix introduces proper sanitization for the Plugins field within the configuration state. When sensitive dumping is disabled, the controller now replaces all plugin configuration values with a redaction placeholder before they are served via the diagnostics endpoints. Additionally, it is recommended to ensure your deployment environment follows the principle of least privilege regarding network access to controller components.
Users should upgrade to the latest patched version of Kong Ingress Controller to ensure diagnostic dumps are correctly redacted.
Medium Basis: The source's own band: MODERATE
0, fixed 3.5.7 (semver)3.5.7
3.5.7go get github.com/kong/kubernetes-ingress-controller/[email protected]0, last affected 2.12.8 (semver)None listed
No fixed version is listed.
0, last affected 1.3.4 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0