CVE-2026-116472
Last modified
CVE-2026-116472 is a low-severity vulnerability rated 2.7/10 on the CVSS scale. 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.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Kubernetes | ingress-nginx | < * |
| SUSE | Rancher Prime RKE2 ingress-nginx | < 1.15.2-prime1 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-116472?
How severe is CVE-2026-116472?
How do I fix CVE-2026-116472?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-116461A vulnerability was determined in Omega Solution Restro POS …4.3
- CVE-2026-116463A vulnerability was identified in FastStone Image Viewer up …6.3
- CVE-2026-116467A security flaw has been discovered in ggml-org llama.cpp up…5.3
- CVE-2026-116469MISP Guard, a proxy-based security filter for MISP feed dist…7.1
- CVE-2026-11647Use after free in Printing in Google Chrome on Android prior…8.3
- CVE-2026-116471A security flaw has been discovered in BKWLD Decoy up to 5.1…4.3
- CVE-2026-116474The `GITEA_TOKEN` of a Gitea Actions job authenticates as th…
- CVE-2026-116476A weakness has been identified in a2aproject a2a-dotnet up t…5.4
- CVE-2026-116477A security vulnerability has been detected in a2aproject a2a…4.3
- CVE-2026-116478A vulnerability was detected in a2aproject a2a-go up to 2.4.…5.3
- CVE-2026-116479A flaw has been found in a2aproject a2a-java up to 1.2.0.Fin…4.3
- CVE-2026-11648Use after free in FullScreen in Google Chrome on Windows pri…8.8
Are you affected by CVE-2026-116472?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
