{"id":"CVE-2026-116472","published":"2026-11-05T19:17:10.690","lastModified":"2026-11-05T22:17:48.357","description":"A security issue was discovered in ingress-nginx where a user with permission to create an Ingress may be able to cause denial of service of the ingress-nginx data plane, or possibly redirect traffic from other Ingresses. Kubernetes clusters are only affected if they are using ingress-nginx.\n\nDue to a missing check, the mirror-target Ingress annotation can be used to target an unauthenticated configuration API within the ingress-nginx controller, allowing write commands to be submitted. Corrupting the data within that configuration API results in all traffic through ingress-nginx being dropped until an Ingress configuration change or a controller restart causes the data to be recreated correctly.\n\nIn principle, this write access could also be used to redirect traffic from other Ingresses controlled by the same ingress-nginx instance. In practice, there is negligible additional risk: such redirection would require privileged information about internal ingress-nginx state, and users can already redirect traffic from other Ingresses controlled by the same ingress-nginx anyway.","cvssScore":2.7,"cvssSeverity":"LOW","cvssVector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L","cwes":["CWE-20"],"vendors":[],"products":[],"references":[{"url":"https://github.com/kubernetes/kubernetes/issues/143852","tags":[]},{"url":"http://www.openwall.com/lists/oss-security/2026/11/05/4","tags":[]}],"exploitRefs":[{"url":"https://github.com/kubernetes/kubernetes/issues/143852","tags":[]}],"hasPoc":true,"ai":null}