CVE-2026-15228 (GCVE-0-2026-15228)

Vulnerability from cvelistv5 – Published: 2026-07-29 15:28 – Updated: 2026-07-29 15:53
VLAI
Title
Kong Kubernetes Ingress Controller cluster-wide ingress configuration DoS via CA-certificate ID collision
Summary
Kong Kubernetes Ingress Controller (KIC) allows a user with namespace-scoped Secret creation privileges to cause a cluster-wide ingress configuration denial of service. KIC collects CA-certificate Secrets across all watched namespaces using a label selector alone, without ingress-class or namespace restrictions. The CA-certificate primary key is derived from a user-supplied field in the Secret. Duplicate CA-certificate IDs cause Kong Gateway to reject the entire configuration document and halting all ingress changes cluster-wide.
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-07-29 15:53 UTC
Assigner
Kong CNA under the mitre root
CNA scorecard B 85/100 over 17 records in the last 180 days details
Impacted products
Vendor Product Version CPE status
Affected: 3.4.0 , < 3.4.18 (semver)
Affected: 3.5.0 , < 3.5.11 (semver)
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-15228",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-07-29T15:53:16.091813Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-07-29T15:53:22.898Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "collectionURL": "https://github.com",
          "defaultStatus": "unaffected",
          "packageName": "Kong/kubernetes-ingress-controller",
          "repo": "https://github.com/Kong/kubernetes-ingress-controller",
          "versions": [
            {
              "lessThan": "3.4.18",
              "status": "affected",
              "version": "3.4.0",
              "versionType": "semver"
            },
            {
              "lessThan": "3.5.11",
              "status": "affected",
              "version": "3.5.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "configurations": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eYou are affected if\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003cstrong\u003eall\u003c/strong\u003e\u003cspan\u003e\u0026nbsp;\u003c/span\u003eof the following hold:\u003c/p\u003e\u003col\u003e\u003cli\u003eKIC is configured without\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003cstrong\u003e`--watch-namespace\u003c/strong\u003e\u003cspan\u003e\u0026nbsp;\u003c/span\u003eCLI flag, causing the KIC to watch Secrets cluster-wide.\u003c/li\u003e\u003cli\u003eYour cluster hosts\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003cstrong\u003emultiple tenants\u003c/strong\u003e\u003cspan\u003e\u0026nbsp;\u003c/span\u003ewhere not all users are fully trusted.\u003c/li\u003e\u003cli\u003eUntrusted users have RBAC permission to\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003cstrong\u003ecreate Secrets\u003c/strong\u003e\u003cspan\u003e\u0026nbsp;\u003c/span\u003ein any namespace watched by the\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003ccode\u003eControlPlane\u003c/code\u003e, and are not prevented from applying\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003ccode\u003ekonghq.com/ca-cert=true\u003c/code\u003e\u003cspan\u003e\u0026nbsp;\u003c/span\u003elabels.\u003c/li\u003e\u003c/ol\u003e\u003cp\u003eYou are\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003cstrong\u003enot\u003c/strong\u003e\u003cspan\u003e\u0026nbsp;\u003c/span\u003eaffected if:\u003c/p\u003e\u003cul\u003e\u003cli\u003eKIC has\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003ccode\u003e--watch-namespace\u003c/code\u003e\u003cspan\u003e\u0026nbsp;\u003c/span\u003ethat is set to only include trusted namespaces.\u003c/li\u003e\u003cli\u003eRBAC policies prevent untrusted users from creating Secrets with the labels\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003ccode\u003ekonghq.com/ca-cert=true\u003c/code\u003e\u003cspan\u003e\u0026nbsp;\u003c/span\u003ein any namespace watched by KIC.\u003c/li\u003e\u003c/ul\u003e"
            }
          ],
          "value": "You are affected if\u00a0all\u00a0of the following hold:\n\n  *  KIC is configured without\u00a0`--watch-namespace\u00a0CLI flag, causing the KIC to watch Secrets cluster-wide.\n  *  Your cluster hosts\u00a0multiple tenants\u00a0where not all users are fully trusted.\n  *  Untrusted users have RBAC permission to\u00a0create Secrets\u00a0in any namespace watched by the\u00a0ControlPlane, and are not prevented from applying\u00a0konghq.com/ca-cert=true\u00a0labels.\n\n\nYou are\u00a0not\u00a0affected if:\n\n  *  KIC has\u00a0--watch-namespace\u00a0that is set to only include trusted namespaces.\n  *  RBAC policies prevent untrusted users from creating Secrets with the labels\u00a0konghq.com/ca-cert=true\u00a0in any namespace watched by KIC."
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eKong Kubernetes Ingress Controller (KIC) allows a user with namespace-scoped Secret creation privileges to cause a cluster-wide ingress configuration denial of service. KIC collects CA-certificate Secrets across all watched namespaces using a label selector alone, without ingress-class or namespace restrictions. The CA-certificate primary key is derived from a user-supplied field in the Secret. Duplicate CA-certificate IDs cause Kong Gateway to reject the entire configuration document and halting all ingress changes cluster-wide.\u003c/p\u003e"
            }
          ],
          "value": "Kong Kubernetes Ingress Controller (KIC) allows a user with namespace-scoped Secret creation privileges to cause a cluster-wide ingress configuration denial of service. KIC collects CA-certificate Secrets across all watched namespaces using a label selector alone, without ingress-class or namespace restrictions. The CA-certificate primary key is derived from a user-supplied field in the Secret. Duplicate CA-certificate IDs cause Kong Gateway to reject the entire configuration document and halting all ingress changes cluster-wide."
        }
      ],
      "impacts": [
        {
          "capecId": "CAPEC-240",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-240 Resource Injection"
            }
          ]
        },
        {
          "descriptions": [
            {
              "lang": "en",
              "value": "Denial of Service"
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 7.1,
            "baseSeverity": "HIGH",
            "exploitMaturity": "NOT_DEFINED",
            "privilegesRequired": "LOW",
            "providerUrgency": "NOT_DEFINED",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "HIGH",
            "vulnConfidentialityImpact": "NONE",
            "vulnIntegrityImpact": "NONE",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-862",
              "description": "CWE-862",
              "lang": "en",
              "type": "CWE"
            }
          ]
        },
        {
          "descriptions": [
            {
              "cweId": "CWE-400",
              "description": "CWE-400",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-07-29T15:28:30.362Z",
        "orgId": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
        "shortName": "Kong"
      },
      "references": [
        {
          "url": "https://github.com/Kong/kubernetes-ingress-controller/security/advisories/GHSA-g9h6-h2xj-mf78"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cspan\u003eUsers should upgrade to the patched version of KIC (3.4.18; 3.5.11)\u003c/span\u003e"
            }
          ],
          "value": "Users should upgrade to the patched version of KIC (3.4.18; 3.5.11)"
        }
      ],
      "source": {
        "discovery": "EXTERNAL"
      },
      "title": "Kong Kubernetes Ingress Controller cluster-wide ingress configuration DoS via CA-certificate ID collision",
      "workarounds": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003col\u003e\u003cli\u003e\u003cp\u003e\u003cstrong\u003eRestrict watch scope\u003c/strong\u003e: Set\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003ccode\u003e--watch-namespace\u003c/code\u003e\u003cspan\u003e\u0026nbsp;\u003c/span\u003e(or env\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003ccode\u003eCONTROLLER_WATCH_NAMESPACE\u003c/code\u003e) to only include trusted namespaces. This prevents the embedded KIC from ingesting Secrets from untrusted namespaces.\u003c/p\u003e\u003c/li\u003e\u003cli\u003e\u003cp\u003e\u003cstrong\u003eRestrict Secret labeling via RBAC\u003c/strong\u003e: Use Kubernetes RBAC to prevent untrusted users from creating or modifying Secrets with the labels\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003ccode\u003ekonghq.com/secret=true\u003c/code\u003e\u003cspan\u003e\u0026nbsp;\u003c/span\u003eand\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003ccode\u003ekonghq.com/ca-cert=true\u003c/code\u003e. Consider using an admission webhook or OPA/Kyverno policy to enforce this label restriction.\u003c/p\u003e\u003c/li\u003e\u003cli\u003e\u003cp\u003e\u003cstrong\u003eAudit existing CA-cert Secrets\u003c/strong\u003e: Inspect Secrets labeled\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003ccode\u003ekonghq.com/ca-cert=true\u003c/code\u003e\u003cspan\u003e\u0026nbsp;\u003c/span\u003eacross all watched namespaces for unexpected or duplicate\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003ccode\u003edata.id\u003c/code\u003e\u003cspan\u003e\u0026nbsp;\u003c/span\u003evalues. Remove any that were not provisioned by a trusted operator.\u003c/p\u003e\u003c/li\u003e\u003c/ol\u003e"
            }
          ],
          "value": "*  \n\nRestrict watch scope: Set\u00a0--watch-namespace\u00a0(or env\u00a0CONTROLLER_WATCH_NAMESPACE) to only include trusted namespaces. This prevents the embedded KIC from ingesting Secrets from untrusted namespaces.\n\n\n  *  \n\nRestrict Secret labeling via RBAC: Use Kubernetes RBAC to prevent untrusted users from creating or modifying Secrets with the labels\u00a0konghq.com/secret=true\u00a0and\u00a0konghq.com/ca-cert=true. Consider using an admission webhook or OPA/Kyverno policy to enforce this label restriction.\n\n\n  *  \n\nAudit existing CA-cert Secrets: Inspect Secrets labeled\u00a0konghq.com/ca-cert=true\u00a0across all watched namespaces for unexpected or duplicate\u00a0data.id\u00a0values. Remove any that were not provisioned by a trusted operator."
        }
      ],
      "x_generator": {
        "engine": "Vulnogram 1.0.4"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
    "assignerShortName": "Kong",
    "cveId": "CVE-2026-15228",
    "datePublished": "2026-07-29T15:28:30.362Z",
    "dateReserved": "2026-07-09T10:50:51.533Z",
    "dateUpdated": "2026-07-29T15:53:22.898Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-15228",
      "date": "2026-11-04",
      "epss": "0.00228",
      "percentile": "0.13674"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "collectionURL": "https://github.com",
                "defaultStatus": "unaffected",
                "packageName": "Kong/kubernetes-ingress-controller",
                "repo": "https://github.com/Kong/kubernetes-ingress-controller",
                "versions": [
                  {
                    "lessThan": "3.4.18",
                    "status": "affected",
                    "version": "3.4.0",
                    "versionType": "semver"
                  },
                  {
                    "lessThan": "3.5.11",
                    "status": "affected",
                    "version": "3.5.0",
                    "versionType": "semver"
                  }
                ]
              }
            ],
            "source": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "Kong Kubernetes Ingress Controller (KIC) allows a user with namespace-scoped Secret creation privileges to cause a cluster-wide ingress configuration denial of service. KIC collects CA-certificate Secrets across all watched namespaces using a label selector alone, without ingress-class or namespace restrictions. The CA-certificate primary key is derived from a user-supplied field in the Secret. Duplicate CA-certificate IDs cause Kong Gateway to reject the entire configuration document and halting all ingress changes cluster-wide."
          }
        ],
        "id": "CVE-2026-15228",
        "lastModified": "2026-07-30T14:15:31.167",
        "metrics": {
          "cvssMetricV40": [
            {
              "cvssData": {
                "Automatable": "NOT_DEFINED",
                "Recovery": "NOT_DEFINED",
                "Safety": "NOT_DEFINED",
                "attackComplexity": "LOW",
                "attackRequirements": "NONE",
                "attackVector": "NETWORK",
                "availabilityRequirement": "NOT_DEFINED",
                "baseScore": 7.1,
                "baseSeverity": "HIGH",
                "confidentialityRequirement": "NOT_DEFINED",
                "exploitMaturity": "NOT_DEFINED",
                "integrityRequirement": "NOT_DEFINED",
                "modifiedAttackComplexity": "NOT_DEFINED",
                "modifiedAttackRequirements": "NOT_DEFINED",
                "modifiedAttackVector": "NOT_DEFINED",
                "modifiedPrivilegesRequired": "NOT_DEFINED",
                "modifiedSubAvailabilityImpact": "NOT_DEFINED",
                "modifiedSubConfidentialityImpact": "NOT_DEFINED",
                "modifiedSubIntegrityImpact": "NOT_DEFINED",
                "modifiedUserInteraction": "NOT_DEFINED",
                "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
                "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
                "modifiedVulnIntegrityImpact": "NOT_DEFINED",
                "privilegesRequired": "LOW",
                "providerUrgency": "NOT_DEFINED",
                "subAvailabilityImpact": "NONE",
                "subConfidentialityImpact": "NONE",
                "subIntegrityImpact": "NONE",
                "userInteraction": "NONE",
                "valueDensity": "NOT_DEFINED",
                "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
                "version": "4.0",
                "vulnAvailabilityImpact": "HIGH",
                "vulnConfidentialityImpact": "NONE",
                "vulnIntegrityImpact": "NONE",
                "vulnerabilityResponseEffort": "NOT_DEFINED"
              },
              "source": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
              "type": "Secondary"
            }
          ],
          "ssvcV203": [
            {
              "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "ssvcData": {
                "id": "CVE-2026-15228",
                "options": [
                  {
                    "exploitation": "none"
                  },
                  {
                    "automatable": "no"
                  },
                  {
                    "technicalImpact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-07-29T15:53:16.091813Z",
                "version": "2.0.3"
              }
            }
          ]
        },
        "published": "2026-07-29T16:17:49.723",
        "references": [
          {
            "source": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
            "url": "https://github.com/Kong/kubernetes-ingress-controller/security/advisories/GHSA-g9h6-h2xj-mf78"
          }
        ],
        "sourceIdentifier": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
        "vulnStatus": "Awaiting Analysis",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-400"
              },
              {
                "lang": "en",
                "value": "CWE-862"
              }
            ],
            "source": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
            "type": "Secondary"
          }
        ]
      }
    },
    "vulnrichment": {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-15228",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-07-29T15:53:16.091813Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-07-29T15:53:19.209Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "collectionURL": "https://github.com",
              "defaultStatus": "unaffected",
              "packageName": "Kong/kubernetes-ingress-controller",
              "repo": "https://github.com/Kong/kubernetes-ingress-controller",
              "versions": [
                {
                  "lessThan": "3.4.18",
                  "status": "affected",
                  "version": "3.4.0",
                  "versionType": "semver"
                },
                {
                  "lessThan": "3.5.11",
                  "status": "affected",
                  "version": "3.5.0",
                  "versionType": "semver"
                }
              ]
            }
          ],
          "configurations": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/html",
                  "value": "\u003cp\u003eYou are affected if\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003cstrong\u003eall\u003c/strong\u003e\u003cspan\u003e\u0026nbsp;\u003c/span\u003eof the following hold:\u003c/p\u003e\u003col\u003e\u003cli\u003eKIC is configured without\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003cstrong\u003e`--watch-namespace\u003c/strong\u003e\u003cspan\u003e\u0026nbsp;\u003c/span\u003eCLI flag, causing the KIC to watch Secrets cluster-wide.\u003c/li\u003e\u003cli\u003eYour cluster hosts\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003cstrong\u003emultiple tenants\u003c/strong\u003e\u003cspan\u003e\u0026nbsp;\u003c/span\u003ewhere not all users are fully trusted.\u003c/li\u003e\u003cli\u003eUntrusted users have RBAC permission to\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003cstrong\u003ecreate Secrets\u003c/strong\u003e\u003cspan\u003e\u0026nbsp;\u003c/span\u003ein any namespace watched by the\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003ccode\u003eControlPlane\u003c/code\u003e, and are not prevented from applying\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003ccode\u003ekonghq.com/ca-cert=true\u003c/code\u003e\u003cspan\u003e\u0026nbsp;\u003c/span\u003elabels.\u003c/li\u003e\u003c/ol\u003e\u003cp\u003eYou are\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003cstrong\u003enot\u003c/strong\u003e\u003cspan\u003e\u0026nbsp;\u003c/span\u003eaffected if:\u003c/p\u003e\u003cul\u003e\u003cli\u003eKIC has\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003ccode\u003e--watch-namespace\u003c/code\u003e\u003cspan\u003e\u0026nbsp;\u003c/span\u003ethat is set to only include trusted namespaces.\u003c/li\u003e\u003cli\u003eRBAC policies prevent untrusted users from creating Secrets with the labels\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003ccode\u003ekonghq.com/ca-cert=true\u003c/code\u003e\u003cspan\u003e\u0026nbsp;\u003c/span\u003ein any namespace watched by KIC.\u003c/li\u003e\u003c/ul\u003e"
                }
              ],
              "value": "You are affected if\u00a0all\u00a0of the following hold:\n\n  *  KIC is configured without\u00a0`--watch-namespace\u00a0CLI flag, causing the KIC to watch Secrets cluster-wide.\n  *  Your cluster hosts\u00a0multiple tenants\u00a0where not all users are fully trusted.\n  *  Untrusted users have RBAC permission to\u00a0create Secrets\u00a0in any namespace watched by the\u00a0ControlPlane, and are not prevented from applying\u00a0konghq.com/ca-cert=true\u00a0labels.\n\n\nYou are\u00a0not\u00a0affected if:\n\n  *  KIC has\u00a0--watch-namespace\u00a0that is set to only include trusted namespaces.\n  *  RBAC policies prevent untrusted users from creating Secrets with the labels\u00a0konghq.com/ca-cert=true\u00a0in any namespace watched by KIC."
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/html",
                  "value": "\u003cp\u003eKong Kubernetes Ingress Controller (KIC) allows a user with namespace-scoped Secret creation privileges to cause a cluster-wide ingress configuration denial of service. KIC collects CA-certificate Secrets across all watched namespaces using a label selector alone, without ingress-class or namespace restrictions. The CA-certificate primary key is derived from a user-supplied field in the Secret. Duplicate CA-certificate IDs cause Kong Gateway to reject the entire configuration document and halting all ingress changes cluster-wide.\u003c/p\u003e"
                }
              ],
              "value": "Kong Kubernetes Ingress Controller (KIC) allows a user with namespace-scoped Secret creation privileges to cause a cluster-wide ingress configuration denial of service. KIC collects CA-certificate Secrets across all watched namespaces using a label selector alone, without ingress-class or namespace restrictions. The CA-certificate primary key is derived from a user-supplied field in the Secret. Duplicate CA-certificate IDs cause Kong Gateway to reject the entire configuration document and halting all ingress changes cluster-wide."
            }
          ],
          "impacts": [
            {
              "capecId": "CAPEC-240",
              "descriptions": [
                {
                  "lang": "en",
                  "value": "CAPEC-240 Resource Injection"
                }
              ]
            },
            {
              "descriptions": [
                {
                  "lang": "en",
                  "value": "Denial of Service"
                }
              ]
            }
          ],
          "metrics": [
            {
              "cvssV4_0": {
                "Automatable": "NOT_DEFINED",
                "Recovery": "NOT_DEFINED",
                "Safety": "NOT_DEFINED",
                "attackComplexity": "LOW",
                "attackRequirements": "NONE",
                "attackVector": "NETWORK",
                "baseScore": 7.1,
                "baseSeverity": "HIGH",
                "exploitMaturity": "NOT_DEFINED",
                "privilegesRequired": "LOW",
                "providerUrgency": "NOT_DEFINED",
                "subAvailabilityImpact": "NONE",
                "subConfidentialityImpact": "NONE",
                "subIntegrityImpact": "NONE",
                "userInteraction": "NONE",
                "valueDensity": "NOT_DEFINED",
                "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
                "version": "4.0",
                "vulnAvailabilityImpact": "HIGH",
                "vulnConfidentialityImpact": "NONE",
                "vulnIntegrityImpact": "NONE",
                "vulnerabilityResponseEffort": "NOT_DEFINED"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-862",
                  "description": "CWE-862",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            },
            {
              "descriptions": [
                {
                  "cweId": "CWE-400",
                  "description": "CWE-400",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-07-29T15:28:30.362Z",
            "orgId": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
            "shortName": "Kong"
          },
          "references": [
            {
              "url": "https://github.com/Kong/kubernetes-ingress-controller/security/advisories/GHSA-g9h6-h2xj-mf78"
            }
          ],
          "solutions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/html",
                  "value": "\u003cspan\u003eUsers should upgrade to the patched version of KIC (3.4.18; 3.5.11)\u003c/span\u003e"
                }
              ],
              "value": "Users should upgrade to the patched version of KIC (3.4.18; 3.5.11)"
            }
          ],
          "source": {
            "discovery": "EXTERNAL"
          },
          "title": "Kong Kubernetes Ingress Controller cluster-wide ingress configuration DoS via CA-certificate ID collision",
          "workarounds": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/html",
                  "value": "\u003col\u003e\u003cli\u003e\u003cp\u003e\u003cstrong\u003eRestrict watch scope\u003c/strong\u003e: Set\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003ccode\u003e--watch-namespace\u003c/code\u003e\u003cspan\u003e\u0026nbsp;\u003c/span\u003e(or env\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003ccode\u003eCONTROLLER_WATCH_NAMESPACE\u003c/code\u003e) to only include trusted namespaces. This prevents the embedded KIC from ingesting Secrets from untrusted namespaces.\u003c/p\u003e\u003c/li\u003e\u003cli\u003e\u003cp\u003e\u003cstrong\u003eRestrict Secret labeling via RBAC\u003c/strong\u003e: Use Kubernetes RBAC to prevent untrusted users from creating or modifying Secrets with the labels\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003ccode\u003ekonghq.com/secret=true\u003c/code\u003e\u003cspan\u003e\u0026nbsp;\u003c/span\u003eand\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003ccode\u003ekonghq.com/ca-cert=true\u003c/code\u003e. Consider using an admission webhook or OPA/Kyverno policy to enforce this label restriction.\u003c/p\u003e\u003c/li\u003e\u003cli\u003e\u003cp\u003e\u003cstrong\u003eAudit existing CA-cert Secrets\u003c/strong\u003e: Inspect Secrets labeled\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003ccode\u003ekonghq.com/ca-cert=true\u003c/code\u003e\u003cspan\u003e\u0026nbsp;\u003c/span\u003eacross all watched namespaces for unexpected or duplicate\u003cspan\u003e\u0026nbsp;\u003c/span\u003e\u003ccode\u003edata.id\u003c/code\u003e\u003cspan\u003e\u0026nbsp;\u003c/span\u003evalues. Remove any that were not provisioned by a trusted operator.\u003c/p\u003e\u003c/li\u003e\u003c/ol\u003e"
                }
              ],
              "value": "*  \n\nRestrict watch scope: Set\u00a0--watch-namespace\u00a0(or env\u00a0CONTROLLER_WATCH_NAMESPACE) to only include trusted namespaces. This prevents the embedded KIC from ingesting Secrets from untrusted namespaces.\n\n\n  *  \n\nRestrict Secret labeling via RBAC: Use Kubernetes RBAC to prevent untrusted users from creating or modifying Secrets with the labels\u00a0konghq.com/secret=true\u00a0and\u00a0konghq.com/ca-cert=true. Consider using an admission webhook or OPA/Kyverno policy to enforce this label restriction.\n\n\n  *  \n\nAudit existing CA-cert Secrets: Inspect Secrets labeled\u00a0konghq.com/ca-cert=true\u00a0across all watched namespaces for unexpected or duplicate\u00a0data.id\u00a0values. Remove any that were not provisioned by a trusted operator."
            }
          ],
          "x_generator": {
            "engine": "Vulnogram 1.0.4"
          }
        }
      },
      "cveMetadata": {
        "assignerOrgId": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
        "assignerShortName": "Kong",
        "cveId": "CVE-2026-15228",
        "datePublished": "2026-07-29T15:28:30.362Z",
        "dateReserved": "2026-07-09T10:50:51.533Z",
        "dateUpdated": "2026-07-29T15:53:22.898Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.