IngressNightmare

Admission-controller vulnerabilities in Kubernetes ingress-nginx

Published Mar 24, 2025 4 related CVEs 1 vendor 1 product

Overview

IngressNightmare names the ingress-nginx vulnerabilities CVE-2025-1097, CVE-2025-1098, CVE-2025-24514 and CVE-2025-1974 researched by Wiz. Injection flaws and unsafe admission-controller configuration testing can combine to execute code in the ingress-nginx controller without Kubernetes API authentication when the admission endpoint is reachable.

Code execution inherits the controller service account permissions. Since the standard deployment can read Secrets across namespaces, a compromised controller can expose credentials and lead to wider cluster compromise. Reachability from a compromised pod or another internal workload can be sufficient; the admission webhook need not be publicly exposed.

The affected component is the community Kubernetes ingress-nginx controller, not every NGINX product or every Kubernetes ingress implementation. Versions 1.12.1 and 1.11.5 first fixed the disclosed set on March 24, 2025. CVE-2025-24513 was addressed in the same release batch but is a different issue; this insight covers the four CVEs of the original RCE chain.

The Kubernetes project subsequently announced ingress-nginx retirement, ending maintenance in March 2026. The 2025 patch levels describe historical remediation of these CVEs, not a supported long-term deployment target. Current remediation should include migration to a maintained ingress controller or Gateway API implementation, alongside isolation and investigation of the old controller.

Affected Technologies

Vendors
Products

Get vulnerability alerts

Follow the technologies you use and get notified about new vulnerabilities and updates to existing CVEs.

Start monitoring