CVE-2026-15228: Kong Kubernetes Ingress Controller cluster-wide ingress configuration DoS via CA-certificate ID collision
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.4.18 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.5.11
Event History
Frequently Asked Questions
What is the severity of CVE-2026-15228?
The severity of CVE-2026-15228 is classified as high with a score of 7.1.
How do I fix CVE-2026-15228?
To mitigate CVE-2026-15228, restrict namespace-scoped Secret creation privileges to trusted users only.
What type of vulnerability is CVE-2026-15228?
CVE-2026-15228 is a denial of service (DoS) vulnerability in the Kong Kubernetes Ingress Controller.
What effects can CVE-2026-15228 have on my Kubernetes cluster?
CVE-2026-15228 can cause a cluster-wide ingress configuration denial of service, impacting service availability.
Who is affected by CVE-2026-15228?
Users with namespace-scoped Secret creation privileges in clusters using the Kong Kubernetes Ingress Controller are affected by CVE-2026-15228.