GHSA-m23h-6mwm-39m8: Github.com/kong/kubernetes ingress controller/v3 Cross-namespace TLS Secret Exfiltration Vulnerability

MODERATE
CWE-200
Published
Advisory Summary

GHSA-m23h-6mwm-39m8 is a MODERATE cross-namespace tls secret exfiltration vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Github.com/kong/kubernetes ingress controller/v3 libraries in the Go ecosystem. The issue involves cross-namespace tls secret exfiltration in gateways with gatewayclass missing `konghq.com/gatewayclass-unmanaged: 'true'` annotation. Remediation is available by upgrading affected packages to version 3.5.7, 3.4.14.

GHSA-m23h-6mwm-39m8 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-m23h-6mwm-39m8
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product Github.com/kong/kubernetes ingress controller/v3
Package Ecosystem Go
Published Date
Last Updated

How to Fix GHSA-m23h-6mwm-39m8

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/v3 fixed: 3.4.14
Upgrade github.com/kong/kubernetes-ingress-controller/v3 to 3.4.14
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-m23h-6mwm-39m8, 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-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. 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 exfiltration of TLS certificates and private keys across Kubernetes namespace boundaries. In "managed" mode (where the `GatewayClass` lacks an unmanaged annotation), the Gateway TLS translator skips critical status checks. This bypass allows the translator to fetch Secrets from any namespace KIC watches, even when a `ReferenceGrant` explicitly denies access or is missing. An actor with RBAC permissions to create or modify Gateways in a low-privileged namespace can reference a Secret in a high-privileged namespace, causing KIC to "leak" that Secret's sensitive private key material into the Kong dataplane configuration. ## Am I affected? You are affected if all of these hold: 1. You are using Kong Ingress Controller with the **Gateway API**. 2. Your `GatewayClass` is operating in **managed mode** (default behavior, no unmanaged annotation). 3. KIC is configured to **watch multiple namespaces** (multi-tenant environment). 4. Users have RBAC permissions to `create` or `update` `gateways.gateway.networking.k8s.io` in their own namespaces. You are not affected if any of this: - You only use KIC for `Ingress` resources (not Gateway API). - Your `GatewayClass` uses the `konghq.com/gateway-unmanaged` annotation. - KIC is restricted via RBAC or configuration to only watch a single namespace. - You have strictly limited Gateway creation/modification permissions to trusted cluster administrators only. ## Mitigation 1. **Add unmanaged gateway annotation**: add the `konghq.com/gateway-unmanaged` annotation to your `GatewayClass` ### Additional best practicies 1. **Restrict Gateway RBAC**: Limit the ability to create or modify Gateway resources to high-trust administrative users until a patch is applied. 2. **Namespace Isolation**: If possible, limit the namespaces KIC is permitted to watch using the `WATCH_NAMESPACE` environment variable or specific RBAC RoleBindings. ## Fix The fix mandates `ReferenceGrant` validation for all cross-namespace certificate references. By requiring a `Programmed: True` listener status, the translator now strictly authorizes external Secret access while maintaining default access for same-namespace certificates, effectively closing the exfiltration vector. Fixed in [#7920](https://github.com/Kong/kubernetes-ingress-controller/pull/7920), with backports to supported release branches in [#7921](https://github.com/Kong/kubernetes-ingress-controller/pull/7921) and [#7922](https://github.com/Kong/kubernetes-ingress-controller/pull/7922). Upgrade to one of the following patched versions (or later): - **3.4.14** - **3.5.7** ## CVSS `CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:P` = **5.6 Medium**

GHSA-m23h-6mwm-39m8 Affected Github.com/kong/kubernetes ingress controller/v3 Versions

4 component(s)
Fixed Versions:
3.5.73.4.14
Product / Package Ecosystem Affected Versions Fixed Version
github.com/kong/kubernetes-ingress-controller/v3
Go
≥ 3.5.0
< 3.5.7
3.5.7
github.com/kong/kubernetes-ingress-controller/v3
Go
< 3.4.14
3.4.14
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-m23h-6mwm-39m8?
GHSA-m23h-6mwm-39m8 is a security vulnerability in Github.com/kong/kubernetes ingress controller/v3 involving Cross-namespace TLS Secret Exfiltration in Gateways with GatewayClass missing `konghq.com/gatewayclass-unmanaged: 'true'` annotation under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which Github.com/kong/kubernetes ingress controller/v3 versions are affected?
Affected versions include releases prior to 3.5.7, 3.4.14 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-m23h-6mwm-39m8?
Upgrading to 3.5.7, 3.4.14 (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, 3.4.14. Upgrade your dependency to 3.5.7, 3.4.14 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-m23h-6mwm-39m8?
GHSA-m23h-6mwm-39m8 is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check Go dependencies for GHSA-m23h-6mwm-39m8?
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-m23h-6mwm-39m8",
  "modified" : "2026-05-19T19:30:23Z",
  "published" : "2026-05-19T19:30:23Z",
  "aliases" : [ ],
  "summary" : "Kong Ingress Controller for Kubernetes (KIC): Cross-namespace TLS Secret Exfiltration in Gateways with GatewayClass missing `konghq.com/gatewayclass-unmanaged: 'true'` annotation",
  "details" : "## Summary\n\nA vulnerability in the Kong Ingress Controller (KIC) allows for the unauthorized exfiltration of TLS certificates and private keys across Kubernetes namespace boundaries. In \"managed\" mode (where the `GatewayClass` lacks an unmanaged annotation), the Gateway TLS translator skips critical status checks. This bypass allows the translator to fetch Secrets from any namespace KIC watches, even when a `ReferenceGrant` explicitly denies access or is missing.\n\nAn actor with RBAC permissions to create or modify Gateways in a low-privileged namespace can reference a Secret in a high-privileged namespace, causing KIC to \"leak\" that Secret's sensitive private key material into the Kong dataplane configuration.\n\n## Am I affected?\n\nYou are affected if all of these hold:\n1. You are using Kong Ingress Controller with the **Gateway API**.\n2. Your `GatewayClass` is operating in **managed mode** (default behavior, no unmanaged annotation).\n3. KIC is configured to **watch multiple namespaces** (multi-tenant environment).\n4. Users have RBAC permissions to `create` or `update` `gateways.gateway.networking.k8s.io` in their own namespaces.\n\nYou are not affected if any of this:\n- You only use KIC for `Ingress` resources (not Gateway API).\n- Your `GatewayClass` uses the `konghq.com/gateway-unmanaged` annotation.\n- KIC is restricted via RBAC or configuration to only watch a single namespace.\n- You have strictly limited Gateway creation/modification permissions to trusted cluster administrators only.\n\n## Mitigation\n\n1. **Add unmanaged gateway annotation**: add the `konghq.com/gateway-unmanaged` annotation to your `GatewayClass`\n\n### Additional best practicies\n\n1. **Restrict Gateway RBAC**: Limit the ability to create or modify Gateway resources to high-trust administrative users until a patch is applied.\n2. **Namespace Isolation**: If possible, limit the namespaces KIC is permitted to watch using the `WATCH_NAMESPACE` environment variable or specific RBAC RoleBindings.\n\n## Fix\n\nThe fix mandates `ReferenceGrant` validation for all cross-namespace certificate references. By requiring a `Programmed: True` listener status, the translator now strictly authorizes external Secret access while maintaining default access for same-namespace certificates, effectively closing the exfiltration vector.\n\nFixed in [#7920](https://github.com/Kong/kubernetes-ingress-controller/pull/7920), with backports to supported release branches in [#7921](https://github.com/Kong/kubernetes-ingress-controller/pull/7921) and [#7922](https://github.com/Kong/kubernetes-ingress-controller/pull/7922).\n\nUpgrade to one of the following patched versions (or later):\n- **3.4.14**\n- **3.5.7**\n\n## CVSS\n\n`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:P` = **5.6 Medium**",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:P"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/kong/kubernetes-ingress-controller/v3"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.5.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/v3"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.4.14"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.4.13"
    }
  }, {
    "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-m23h-6mwm-39m8"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Kong/kubernetes-ingress-controller/pull/7920"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Kong/kubernetes-ingress-controller/pull/7921"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Kong/kubernetes-ingress-controller/pull/7922"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/Kong/kubernetes-ingress-controller"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-19T19:30:23Z",
    "nvd_published_at" : null
  }
}