Kubernetes · Kubernetes · published 2026-11-05
CVE-2026-116472ingress-nginx mirror-target self-DOS
Routine No exploitation evidence; EPSS 0.4%.
CVE-2026-116472 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 36% of all CVEs. This Kubernetes vulnerability: CVSS 2.7 (v3.1). Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Patch events
OrchestrationKubernetes
Kubernetes: ingress-nginx mirror-target self-DOS
Why: Vendor security release for server software (most severe: CVE-2026-116472).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.4% (36th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 2.7 (v3.1)CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Kubernetes ingress-nginx
0to before*(affected)
- SUSE Rancher Prime RKE2 ingress-nginx
0to before1.15.2-prime1(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.