EUVD-2026-50353Severity by source
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
Authenticated namespace-scoped Secret creator (PR:L) over the network with low complexity; availability-only impact, and S:C because a single-namespace actor halts ingress across all other namespaces.
Primary rating from Vendor (Kong).
CVSS VectorVendor: Kong
Lifecycle Timeline
2DescriptionCVE.org
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.
Articles & Coverage 1
AnalysisAI
Cluster-wide ingress denial of service in Kong Kubernetes Ingress Controller (KIC) allows a tenant holding only namespace-scoped Secret creation rights to halt all ingress configuration changes across every watched namespace. Because KIC gathers CA-certificate Secrets by label selector alone - ignoring ingress-class and namespace boundaries - and derives the CA-certificate primary key from a user-supplied Secret field, a low-privileged user can create a duplicate CA-certificate ID that forces Kong Gateway to reject the entire configuration document. Reported by Kong; no public exploit identified at time of analysis and not listed in CISA KEV.
Technical ContextAI
Kong Ingress Controller is the Go-based control-plane component that translates Kubernetes Ingress, Gateway API, and Kong custom resources into Kong Gateway configuration. CA-certificate Secrets (Secrets carrying a CA cert consumed by mTLS/verification plugins) are discovered globally via a Kubernetes label selector, but KIC omits the ingress-class filter and namespace scoping that normally isolate tenants. The primary key (ID) used to deduplicate CA certificates in the generated Kong config comes from a field the Secret creator controls. This is a CWE-862 Missing Authorization weakness: KIC trusts a value crossing a tenant boundary without verifying the actor is authorized to influence cluster-wide state, so two Secrets in different namespaces can collide on the same CA-certificate ID and produce an invalid config document that Kong Gateway refuses wholesale.
Affected ProductsAI
Kong Kubernetes Ingress Controller (KIC), the ingress controller for Kong Gateway on Kubernetes. Specific fixed and affected version ranges were not included in the provided data and should be confirmed from the vendor GitHub Security Advisory GHSA-g9h6-h2xj-mf78 (https://github.com/Kong/kubernetes-ingress-controller/security/advisories/GHSA-g9h6-h2xj-mf78). No CPE string was provided. The downstream affected component is Kong Gateway, which rejects the KIC-generated configuration document.
RemediationAI
Upgrade Kong Ingress Controller to the fixed release identified in the vendor advisory GHSA-g9h6-h2xj-mf78 (https://github.com/Kong/kubernetes-ingress-controller/security/advisories/GHSA-g9h6-h2xj-mf78); an exact patched version was not present in the provided data, so confirm the fixed version directly from that advisory before deploying. As compensating controls until patched: tighten RBAC so untrusted or tenant users cannot create Secrets carrying the CA-certificate label KIC selects on (restrict Secret create/update in shared namespaces, or scope the label to trusted operators only), which prevents attacker-controlled Secrets from entering KIC's global collection at the cost of requiring operators to provision CA Secrets centrally. Additionally, use a Kubernetes admission/validating policy (e.g. OPA Gatekeeper or Kyverno) to reject Secrets whose user-supplied CA-certificate ID field collides with existing IDs or that carry the CA label outside approved namespaces; the trade-off is added admission-control maintenance and the need to enumerate legitimate CA-certificate IDs. Where feasible, limit KIC's watched namespaces to trusted tenants to shrink the blast radius, accepting that this reduces multi-tenant flexibility.
More in Kubernetes
View allA critical vulnerability in Kubernetes ingress-nginx controller allows unauthenticated attackers with pod network access
Credential-harvesting malware compromised 84 versions of 42 TanStack npm packages on 2026-05-11 via chained GitHub Actio
Kubernetes ingress-nginx contains a configuration injection vulnerability via the mirror-target and mirror-host Ingress
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-url` Ingres
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-tls-match-c
Kubernetes API server in all versions allow an attacker who is able to create a ClusterIP service and set the spec.exter
A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able to escalate
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Rated critical severity (CVSS 9.9), this vulne
Unauthenticated remote attackers can trigger complete database overwrites, server-side file reads, and SSRF attacks agai
The Kubernetes integration in GitLab Enterprise Edition 11.x before 11.2.8, 11.3.x before 11.3.9, and 11.4.x before 11.4
Fluentd configuration injection in the kube-logging Logging operator before 6.6.0 allows a namespace-scoped user who can
Kyverno Kubernetes policy engine prior to 1.x has a privilege escalation vulnerability (CVSS 9.9) allowing policy bypass
Same weakness CWE-862 – Missing Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today