Kubernetes/SUSE ingress-nginx/Rancher Prime RKE2 ingress-nginx Configuration API mirror-target input validation

Summaryinfo

A vulnerability was found in Kubernetes/SUSE ingress-nginx and Rancher Prime RKE2 ingress-nginx. It has been rated as problematic. Affected by this vulnerability is an unknown functionality of the component Configuration API. The manipulation of the argument mirror-target leads to input validation. This vulnerability is referenced as CVE-2026-116472. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in Kubernetes/SUSE ingress-nginx and Rancher Prime RKE2 ingress-nginx (version unknown). It has been rated as problematic. This issue affects an unknown function of the component Configuration API. The manipulation of the argument mirror-target with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. Impacted is availability. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-116472 since 10/26/2026. The exploitation is known to be easy. The attack may be initiated remotely. The exploitation requires an enhanced level of successful authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 11/05/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Virtualization Software

Vendor

• Kubernetes
• SUSE

Name

• ingress-nginx
• Rancher Prime RKE2 ingress-nginx

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion