CVE-2025-1974: IngressNightmare: Unauthenticated RCE in Kubernetes ingress-nginx
CVE-2025-1974 is a critical vulnerability in the Kubernetes ingress-nginx admission controller and part of the IngressNightmare vulnerability set. An unauthenticated attacker who can reach the validating admission webhook can submit crafted Ingress admission requests that expose vulnerable NGINX configuration processing. Chaining this access with related configuration-injection vulnerabilities can achieve arbitrary code execution during NGINX configuration validation in the ingress-nginx controller context. Affected releases include versions before 1.11.0, versions 1.11.0 through 1.11.4, and version 1.12.0. The vulnerability has a CVSS v3.1 score of 9.8 and can expose Kubernetes Secrets accessible to the controller, which has cluster-wide Secret access by default.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation compromises the ingress-nginx controller's execution context and can disclose accessible Kubernetes Secrets, including credentials and service-account tokens. Default cluster-wide Secret permissions substantially increase the exposure. Stolen credentials and controller permissions can enable privilege escalation, lateral movement, modification or disruption of cluster resources, and potentially complete cluster takeover. The extent of compromise depends on the controller's permissions and the privileges associated with exposed credentials.
Mitigation
If you can’t patch tonight, do this now.
If immediate upgrading is impossible, temporarily disable the ingress-nginx Validating Admission Controller. For Helm installations, set controller.admissionWebhooks.enabled=false. For manual installations, delete the ingress-nginx-admission ValidatingWebhookConfiguration and remove the --validating-webhook argument from the controller Deployment or DaemonSet. Alternatively, restrict admission-webhook network access to the Kubernetes API server and deny access from untrusted workloads and external networks. Reduce the controller's Secret-access scope where feasible and monitor for suspicious controller execution and Secret access.
Remediation
Patch, then assume compromise.
Upgrade ingress-nginx to version 1.11.5 or later within the 1.11 branch, version 1.12.1 or later within the 1.12 branch, or a newer fixed release. Corresponding patched Helm chart releases include 4.11.5 and 4.12.1. Re-enable admission validation after upgrading if it was temporarily disabled. Investigate suspected prior exploitation: patching does not remove an existing compromise. Review controller logs and Kubernetes API events, and rotate exposed credentials if compromise is established.
Exploits
21 exploits validated by Mallory's analysis. Hidden: 8 rejected by Mallory's analysis as not a working exploit; 3 not yet analyzed, such as Exploit-DB entries.
References
Frequently asked questions
- Is CVE-2025-1974 exploited in the wild?
- Yes. As of Nov 7, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2025-1974?
- Yes. Mallory tracks 21 public exploits or proofs of concept for CVE-2025-1974, the earliest disclosed Mar 24, 2025.
- Is there a patch for CVE-2025-1974?
- Upgrade ingress-nginx to version 1.11.5 or later within the 1.11 branch, version 1.12.1 or later within the 1.12 branch, or a newer fixed release. Corresponding patched Helm chart releases include 4.11.5 and 4.12.1.
- How severe is CVE-2025-1974?
- CVE-2025-1974 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 99.4% (100th percentile) as of Nov 7, 2026.
Recent activity
45 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.