Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
2.7

CVE-2026-116472: Ingress-nginx can be stopped by malicious Ingress

CVE-2026-116472 · published 16 days ago
Summary

If someone can create an Ingress object in your Kubernetes cluster that uses the ingress‑nginx controller, they can corrupt the controller’s internal configuration and cause all traffic to be dropped until the controller is restarted or the configuration is changed. This affects clusters that run the ingress‑nginx component (including the Rancher Prime RKE2 version). Update to the latest ingress‑nginx release or restrict who can create Ingress resources to stop the issue.

What to do
  • Update kubernetes ingress-nginx to version * or later.
  • Update suse rancher prime rke2 ingress-nginx to version 1.15.2-prime1 or later.
Affected software
VendorProductAffected versions
kubernetes ingress-nginx < *
suse rancher prime rke2 ingress-nginx < 1.15.2-prime1
Original advisory text
ingress-nginx mirror-target self-DOS
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.

Due 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.

In 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.
Fix within
Internet-facing 60 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit
  • Gives an attacker partial control
Severity
2.7 Low
Exploitation
<1% chance of attack within 30 days
Type
CWE-20Improper Input Validation
Timeline
Published5 Nov 2026
Updated22 Nov 2026
First seen5 Nov 2026
Sources
CVE-2026-116472 · MITRE
Track software like this
Free during beta