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.

Project Subscriptions

Vendors Products
Kubernetes Subscribe
Ingress-nginx Subscribe
Rancher Prime Rke2 Ingress-nginx Subscribe
Advisories

No advisories yet.

Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

Fri, 06 Nov 2026 17:00:00 +0000

Type Values Removed Values Added
First Time appeared Kubernetes
Kubernetes ingress-nginx
Suse
Suse rancher Prime Rke2 Ingress-nginx
Vendors & Products Kubernetes
Kubernetes ingress-nginx
Suse
Suse rancher Prime Rke2 Ingress-nginx

Fri, 06 Nov 2026 12:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-918
References
Metrics threat_severity

None

threat_severity

Low


Thu, 05 Nov 2026 22:30:00 +0000

Type Values Removed Values Added
References

Thu, 05 Nov 2026 18:30:00 +0000

Type Values Removed Values Added
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. 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.
Title ingress-nginx mirror-target self-DOS
Weaknesses CWE-20
References
Metrics cvssV3_1

{'score': 2.7, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L'}


Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: kubernetes

Published:

Updated: 2026-11-05T22:05:45.488Z

Reserved: 2026-10-26T22:36:13.547Z

Link: CVE-2026-116472

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-11-05T19:17:10.690

Modified: 2026-11-06T20:39:15.033

Link: CVE-2026-116472

cve-icon Redhat

Severity : Low

Publid Date: 2026-11-05T18:13:29Z

Links: CVE-2026-116472 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-11-06T16:35:50Z

Weaknesses