Vulnerabilities in pkg:golang/github.com/kong/kubernetes-ingress-controller/v3

PACKAGE
Advisory Summary

GHSA-3278-c88v-xrh4 is a MODERATE secret-backed plugin configurations leak through vulnerability (CWE-201: Insertion of Sensitive Information Into Sent Data) affecting Github.com/kong/kubernetes ingress controller/v3 libraries in the Go ecosystem. The issue involves secret-backed plugin configurations leak through non-sensitive diagnostics endpoint. Remediation is available by upgrading affected packages to version 3.5.7.

2 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:golang/github.com/kong/kubernetes-ingress-controller/v3

2 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:golang/github.com/kong/kubernetes-ingress-controller/v3. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-3278-c88v-xrh4 - MODERATE Kong Ingress Controller for Kubernetes (KIC): Secret-backed plugin configurations leak through non-sensitive diagnostics endpoint
GHSA-m23h-6mwm-39m8 - MODERATE Kong Ingress Controller for Kubernetes (KIC): Cross-namespace TLS Secret Exfiltration in Gateways with GatewayClass missing `konghq.com/gatewayclass-unmanaged: 'true'` annotation

GHSA-3278-c88v-xrh4 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-3278-c88v-xrh4
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-201: Insertion of Sensitive Information Into Sent Data
Affected Product Github.com/kong/kubernetes ingress controller/v3
Package Ecosystem Go
Published Date
Last Updated

How to Fix GHSA-3278-c88v-xrh4

To remediate this vulnerability, upgrade all affected Github.com/kong/kubernetes ingress controller/v3 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/kong/kubernetes-ingress-controller/v3 fixed: 3.5.7
Upgrade github.com/kong/kubernetes-ingress-controller/v3 to 3.5.7
github.com/kong/kubernetes-ingress-controller/v2 fixed: Latest secure release
Upgrade github.com/kong/kubernetes-ingress-controller/v2 to Latest secure release
github.com/kong/kubernetes-ingress-controller fixed: Latest secure release
Upgrade github.com/kong/kubernetes-ingress-controller to Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/kong/kubernetes-ingress-controller/v3

How to Check if You Are Affected

To determine whether your application is affected by GHSA-3278-c88v-xrh4, inspect your project dependencies for Github.com/kong/kubernetes ingress controller/v3:

inspect dependencies for github.com/kong/kubernetes-ingress-controller/v3

Analyze the terminal output to locate any version of Github.com/kong/kubernetes ingress controller/v3 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.5.7), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-201: Insertion of Sensitive Information Into Sent Data, where the code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor. In Github.com/kong/kubernetes ingress controller/v3, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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: 1. You are using Kong Ingress Controller with **diagnostics enabled** (`--dump-config=true`). 2. You have **not explicitly enabled** sensitive dumping (`--dump-sensitive-config=false`), creating an expectation of redaction. 3. You use `KongPlugin` or `KongClusterPlugin` resources that reference Kubernetes Secrets via **`configFrom.secretKeyRef`**. 4. The KIC diagnostics port (default `10256`) is reachable by other workloads or users within your cluster. You are not affected if: - The `--dump-config` flag is set to `false` (default behavior). - You do not use secret-backed configurations in your Kong plugins. - Access to the KIC pod's diagnostic port is strictly blocked by NetworkPolicies. ## Mitigation 1. **Disable Diagnostics**: If not actively debugging, disable the diagnostic server by setting `--dump-config=false`. 2. **Network Isolation**: Implement a `NetworkPolicy` to restrict access to the KIC diagnostics port (default `10256`), ensuring only authorized administrative pods or IPs can reach it. 3. **Restrict Port-Forwarding**: Limit `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.

GHSA-3278-c88v-xrh4 Affected Github.com/kong/kubernetes ingress controller/v3 Versions

3 component(s)
Fixed Versions:
3.5.7
Product / Package Ecosystem Affected Versions Fixed Version
github.com/kong/kubernetes-ingress-controller/v3
Go
< 3.5.7
3.5.7
github.com/kong/kubernetes-ingress-controller/v2
Go
≤ 2.12.8
github.com/kong/kubernetes-ingress-controller
Go
≤ 1.3.4

References

Frequently Asked Questions

What is GHSA-3278-c88v-xrh4?
GHSA-3278-c88v-xrh4 is a security vulnerability in Github.com/kong/kubernetes ingress controller/v3 involving Secret-backed plugin configurations leak through non-sensitive diagnostics endpoint under CWE-201: Insertion of Sensitive Information Into Sent Data.
Which Github.com/kong/kubernetes ingress controller/v3 versions are affected?
Affected versions include releases prior to 3.5.7 across affected packages: github.com/kong/kubernetes-ingress-controller/v3, github.com/kong/kubernetes-ingress-controller/v2, github.com/kong/kubernetes-ingress-controller.
What version fixes GHSA-3278-c88v-xrh4?
Upgrading to 3.5.7 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/kong/kubernetes-ingress-controller/v3 affected?
Yes, github.com/kong/kubernetes-ingress-controller/v3 is affected in releases prior to 3.5.7. Upgrade your dependency to 3.5.7 or later.
Is github.com/kong/kubernetes-ingress-controller/v2 affected?
Yes, github.com/kong/kubernetes-ingress-controller/v2 is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What CWE is associated with GHSA-3278-c88v-xrh4?
GHSA-3278-c88v-xrh4 is classified under CWE-201: Insertion of Sensitive Information Into Sent Data (The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.).
How can I check Go dependencies for GHSA-3278-c88v-xrh4?
Run the dependency tree command: 'inspect dependencies for github.com/kong/kubernetes-ingress-controller/v3'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-3278-c88v-xrh4",
  "modified" : "2026-06-08T20:13:51Z",
  "published" : "2026-05-19T19:28:48Z",
  "aliases" : [ ],
  "summary" : "Kong Ingress Controller for Kubernetes (KIC): Secret-backed plugin configurations leak through non-sensitive diagnostics endpoint",
  "details" : "## Summary\n\nA 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.\n\nBecause 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.\n\n## Am I affected?\n\nYou are affected if all of the following hold:\n1. You are using Kong Ingress Controller with **diagnostics enabled** (`--dump-config=true`).\n2. You have **not explicitly enabled** sensitive dumping (`--dump-sensitive-config=false`), creating an expectation of redaction.\n3. You use `KongPlugin` or `KongClusterPlugin` resources that reference Kubernetes Secrets via **`configFrom.secretKeyRef`**.\n4. The KIC diagnostics port (default `10256`) is reachable by other workloads or users within your cluster.\n\nYou are not affected if:\n- The `--dump-config` flag is set to `false` (default behavior).\n- You do not use secret-backed configurations in your Kong plugins.\n- Access to the KIC pod's diagnostic port is strictly blocked by NetworkPolicies.\n\n## Mitigation\n\n1. **Disable Diagnostics**: If not actively debugging, disable the diagnostic server by setting `--dump-config=false`.\n2. **Network Isolation**: Implement a `NetworkPolicy` to restrict access to the KIC diagnostics port (default `10256`), ensuring only authorized administrative pods or IPs can reach it.\n3. **Restrict Port-Forwarding**: Limit `kubectl port-forward` RBAC permissions to prevent unauthorized users from accessing the pod's local ports.\n\n## Fix\n\nThe 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.\n\nUsers should upgrade to the latest patched version of Kong Ingress Controller to ensure diagnostic dumps are correctly redacted.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/kong/kubernetes-ingress-controller/v3"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.5.7"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.5.6"
    }
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/kong/kubernetes-ingress-controller/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "2.12.8"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/kong/kubernetes-ingress-controller"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "1.3.4"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/Kong/kubernetes-ingress-controller/security/advisories/GHSA-3278-c88v-xrh4"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/Kong/kubernetes-ingress-controller"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-201" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-19T19:28:48Z",
    "nvd_published_at" : null
  }
}