IngressNightmare: ingress-nginx Cluster Takeover RCE

What to do

Find controllers: kubectl get pods --all-namespaces --selector app.kubernetes.io/name=ingress-nginx, and note the image tags.
Upgrade to ingress-nginx v1.11.5, v1.12.1 or any later release.
If you cannot upgrade, disable the validating admission webhook (Helm: controller.admissionWebhooks.enabled=false; manual: delete the ingress-nginx-admission ValidatingWebhookConfiguration and remove --validating-webhook), then re-enable it after upgrading.
Use NetworkPolicy so only the Kubernetes API server can reach the admission webhook port, and make sure it is never exposed to the internet.
Plan a migration to Gateway API or another ingress controller, since ingress-nginx stopped receiving releases after March 2026.

How to check if you are affected or compromised

List controller image versions across all clusters and compare them against v1.11.5 / v1.12.1.
Check whether the admission webhook Service is reachable from workloads or from outside the cluster.
Review controller pod logs and audit logs for unexpected AdmissionReview requests or nginx -t errors mentioning ssl_engine or unusual annotations; the Kubernetes advisory lists no known IoCs.

What happened#

On March 24, 2025, the Kubernetes Security Response Committee announced fixes for five vulnerabilities in ingress-nginx, the community ingress controller that it says runs in over 40% of Kubernetes clusters. Wiz Research, which found the bugs, named the set IngressNightmare.

Three of the bugs are configuration injection flaws, each scored CVSS 8.8 (High): CVE-2025-24514 (auth-url annotation), CVE-2025-1097 (auth-tls-match-cn annotation) and CVE-2025-1098 (mirror annotations). On their own they require permission to create an Ingress object. CVE-2025-24513 is a path traversal in the admission controller, scored 4.8. The critical one is CVE-2025-1974 (CVSS 9.8). The validating admission webhook ran nginx -t against configuration built from the incoming request, so anyone who could reach the webhook over the pod network could deliver those injections with no credentials at all.

Wiz's chain worked like this. First, an attacker sends a crafted AdmissionReview straight to the webhook. The injected ssl_engine directive then loads a shared library that was smuggled in through NGINX's client-body temp file and is still reachable via /proc. The result is code execution in the controller pod. In a default install that pod can read every Secret in the cluster, which usually means full cluster takeover.

Who is affected#

Affected: ingress-nginx before v1.11.0, v1.11.0 through v1.11.4, and v1.12.0. Fixed: v1.11.5 and v1.12.1. The 1.10.x and older lines never received a patch. This is the kubernetes/ingress-nginx project, not the separate NGINX Ingress Controller from F5/NGINX Inc. To check whether you run it, use kubectl get pods --all-namespaces --selector app.kubernetes.io/name=ingress-nginx. No pods means you are not affected.

Do you really need to act?#

At disclosure Wiz estimated that about 43% of cloud environments were vulnerable, and it found over 6,500 clusters exposing vulnerable admission controllers to the public internet. Those clusters were at serious risk. For everyone else, the realistic attacker is something already inside: a compromised pod, a VPC neighbor, or a user on the corporate network. The Kubernetes post notes that in many setups the pod network is reachable from all of those. The CVSS attack-vector rating was debated in the advisory thread (Network vs. Adjacent), but either way no credentials are needed.

Exploit code is public. Wiz's database reports a public exploit and very high EPSS. As of the October 21, 2026 snapshot, none of the five CVEs is in CISA KEV, and we found no confirmed in-the-wild campaign in the sources we reviewed. Nineteen months on, most maintained clusters have upgraded. The open risk is forgotten clusters and pinned Helm charts. One more factor: Kubernetes retired ingress-nginx, and best-effort maintenance ended in March 2026, so any future bug will not be fixed.

What to do now#

Inventory every cluster with the kubectl selector above and record the image tags.
Upgrade to v1.11.5, v1.12.1 or later.
If you can't upgrade yet, disable the admission webhook. With Helm, set controller.admissionWebhooks.enabled=false. For manual installs, delete the ingress-nginx-admission ValidatingWebhookConfiguration and remove --validating-webhook from the controller args. Turn it back on after upgrading.
Restrict the webhook with NetworkPolicy so that only the API server can reach it.
Start migrating to Gateway API or another maintained controller.

How to tell if you were hit#

The Kubernetes advisory lists no known indicators of compromise. Ask security@kubernetes.io about suspected exploitation. Check whether the webhook Service was reachable from untrusted networks while you ran a vulnerable version. Review controller logs for AdmissionReview requests that did not come from the API server, and for nginx -t failures that mention ssl_engine or odd annotations. If exposure was plausible, rotate the Secrets the controller could read, which in default installs means all of them, and review recent RBAC and workload changes.

Timeline#

Dec 31, 2024 — Wiz reports CVE-2025-1974 and CVE-2025-24514 to Kubernetes.
Jan 21, 2025 — Last of the injection bugs (CVE-2025-1098) reported.
Feb 20, 2025 — Config validation removed from the admission controller (internal fix for CVE-2025-1974).
Mar 24, 2025 — Public disclosure; ingress-nginx v1.11.5 and v1.12.1 released.
Nov 11, 2025 — Kubernetes announces ingress-nginx retirement; best-effort maintenance until March 2026.

Vulnerability records

CVE-2025-1974 · A security issue was discovered in Kubernetes where under certain conditions, an unauthenticated attacker with access to the pod network can achieve arbitrary…
CVE-2025-1097 · A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-tls-match-cn` Ingress annotation can be used to…
CVE-2025-1098 · A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `mirror-target` and `mirror-host` Ingress annotations…
CVE-2025-24514 · A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-url` Ingress annotation can be used to inject…
CVE-2025-24513 · A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where attacker-provided data are included in a filename by the…

Sources

Original sources first: vendor and project advisories, CVE and government records, the discoverers’ write-ups. Every claim above links to one of these. See how the Security Desk works.