{"id":"CVE-2026-116472","aliases":[],"summary":"ingress-nginx mirror-target self-DOS","published_at":"2026-11-05T18:13:29.564Z","modified_at":"2026-11-12T18:59:36.855Z","products":[{"slug":"ingress-nginx","name":"Ingress-NGINX","category":"kubernetes-container"}],"rating":{"severity":"low","score":2.7,"vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L","attack_path":"internet_authenticated","user_interaction":false,"malicious":false},"fix_available":false,"kev":{"listed":false,"ransomware":false},"public_exploit":false,"exploits":[],"epss":{"score":0.004110000096261501,"percentile":0.36063000559806824,"date":"2026-11-18T00:00:00Z"},"priority":3.7,"details":"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.","affected_stack":[{"ecosystem":"CVE","package":"Kubernetes/ingress-nginx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"provider":"cvelistv5","source":"CVE-2026-116472","relation":"self"}],"affected_other":[{"ecosystem":"CVE","package":"SUSE/Rancher Prime RKE2 ingress-nginx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.15.2-prime1"}]}],"fixed":["1.15.2-prime1"],"provider":"cvelistv5","source":"CVE-2026-116472","relation":"self"}],"product_status":[{"vendor":"Red Hat","product":"All currently supported Red Hat products","cpe":"cpe:/a:redhat","status":"not_affected","packages":[],"package_count":0,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2026-116472"}],"records":[{"provider":"cvelistv5","source_id":"CVE-2026-116472","relation":"self","url":"https://www.cve.org/CVERecord?id=CVE-2026-116472","license":"CC-BY-4.0","published_at":"2026-11-05T18:13:29.564Z","modified_at":"2026-11-12T18:59:36.855Z","summary":"ingress-nginx mirror-target self-DOS","details":"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.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L","source":"CVE-2026-116472"}],"affected":[{"ecosystem":"CVE","package":"Kubernetes/ingress-nginx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"provider":"cvelistv5","source":"CVE-2026-116472","relation":"self"},{"ecosystem":"CVE","package":"SUSE/Rancher Prime RKE2 ingress-nginx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.15.2-prime1"}]}],"fixed":["1.15.2-prime1"],"provider":"cvelistv5","source":"CVE-2026-116472","relation":"self"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://github.com/kubernetes/kubernetes/issues/143852"}]},{"provider":"redhat-vex","source_id":"CVE-2026-116472","relation":"self","url":"https://access.redhat.com/security/cve/CVE-2026-116472","license":"CC-BY-4.0","published_at":"2026-11-05T18:13:29.564Z","modified_at":"2026-11-07T06:04:04.986977Z","summary":"ingress-nginx: ingress-nginx: Denial of Service via mirror-target annotation","details":"A flaw was found in ingress-nginx. An authenticated user with permission to create Ingress resources can leverage the mirror-target annotation to send write commands to an unauthenticated internal configuration interface. This action corrupts the controller configuration, resulting in a Denial of Service (DoS) where all data plane network traffic is dropped.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L","source":"CVE-2026-116472"}],"affected":[],"product_status":[{"vendor":"Red Hat","product":"All currently supported Red Hat products","cpe":"cpe:/a:redhat","status":"not_affected","packages":[],"package_count":0,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2026-116472"}],"references":[{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-116472.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2026-116472"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2026-116472"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-116472"},{"type":"WEB","url":"https://github.com/kubernetes/kubernetes/issues/143852"}]}],"references":[{"type":"ADVISORY","url":"https://github.com/kubernetes/kubernetes/issues/143852"},{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-116472.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2026-116472"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2026-116472"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-116472"}],"sources":[{"provider":"cvelistv5","source_id":"CVE-2026-116472","url":"https://www.cve.org/CVERecord?id=CVE-2026-116472","license":"CC-BY-4.0","modified_at":"2026-11-12T18:59:36.855Z","relation":"self"},{"provider":"redhat-vex","source_id":"CVE-2026-116472","url":"https://access.redhat.com/security/cve/CVE-2026-116472","license":"CC-BY-4.0","modified_at":"2026-11-07T06:04:04.986977Z","relation":"self"}]}
