Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

URL has been copied successfully!
CVE-2025-1097, CVE-2025-1098, CVE-2025-1974, CVE-2025-24513, CVE-2025-24514: Frequently Asked Questions About IngressNightmare
URL has been copied successfully!

Collecting Cyber-News from over 60 sources

CVE-2025-1097, CVE-2025-1098, CVE-2025-1974, CVE-2025-24513, CVE-2025-24514: Frequently Asked Questions About IngressNightmare

Frequently asked questions about five vulnerabilities in the Ingress NGINX Controller for Kubernetes, collectively known as IngressNightmare.

Background

The Tenable Security Response Team (SRT) has compiled this blog to answer Frequently Asked Questions (FAQ) regarding IngressNightmare.

FAQ

What is IngressNightmare? IngressNightmare is the name given to a series of vulnerabilities in the Ingress NGINX Controller for Kubernetes, an open source controller used for managing network traffic in Kubernetes clusters using NGINX as a reverse proxy and load balancer. What are the vulnerabilities associated with IngressNightmare? The following CVEs are associated with IngressNightmare:

CVE Description CVSSv3
CVE-2025-1097 Ingress NGINX Controller Configuration Injection via Unsanitized auth-tls-match-cn annotation 8.8
CVE-2025-1098 Ingress NGINX Controller Configuration Injection via Unsanitized Mirror Annotations 8.8
CVE-2025-1974 Ingress NGINX Admission Controller Remote Code Execution 9.8
CVE-2025-24513 Ingress NGINX Controller Auth Secret File Path Traversal Vulnerability 4.8
CVE-2025-24514 Ingress NGINX Controller Via Unsanitized Auth-URL Annotation 8.8

When was IngressNightmare first disclosed? Public disclosure of IngressNightmare happened on March 24 when news outlets, such as The Hacker News, began reporting on these vulnerabilities. At the time those articles were published, no patches were yet available from the Kubernetes team nor had a blog been published by the researchers who discovered these flaws. How critical are the IngressNightmare vulnerabilities? Based on the CVSS scores for these vulnerabilities, three are categorized as high severity, one is categorized as medium severity and one is categorized as critical severity. The most severe flaw, CVE-2025-1974, requires an unauthenticated remote attacker to be able to access the admission controller, a component in the Ingress NGINX Controller that has more privileged access within a Kubernetes cluster. Are the IngressNightmare vulnerabilities part of a toxic combination? Yes, the five vulnerabilities that make up IngressNightmare can be chained together as part of a toxic combination (or exploit chain). Successful exploitation of these flaws would grant an attacker the ability to access cluster secrets, which could result in a cluster takeover. Was this exploited as a zero-day? No, these vulnerabilities were reported to Kubernetes through coordinated disclosure. Is there a proof-of-concept (PoC) available for these vulnerabilities? As of March 24, there are no public proof-of-concept exploits for any of the five CVEs associated with IngressNightmare. Are patches or mitigations available for IngressNightmare? Yes, on the evening of March 24, the Kubernetes team published two fixed versions of Ingress NGINX Controller:

Affected product Affected versions Fixed version
Ingress NGINX Controller 1.12.0 1.12.1
Ingress NGINX Controller 1.11.4 and below 1.11.5

Additionally, customers can use the following command to determine if clusters are using ingress-nginx:

kubectl get pods --all-namespaces --selector app.kubernetes.io/name=ingress-nginx

For more specific information about mitigation steps, please refer to the Kubernetes blog. Does this also affect the NGINX Ingress Controller? No, while the names may sound similar, IngressNightmare does not affect the NGINX Ingress Controller from F5. Has Tenable released any product coverage for these vulnerabilities? A list of Tenable plugins for these vulnerabilities will be available on the individual CVE pages as they’re released: CVE-2025-1097 CVE-2025-1098 CVE-2025-1974 CVE-2025-24513 CVE-2025-24514 Our Plugins Pipeline displays all available plugins for these vulnerabilities, including upcoming plugins, as they are added. Additional coverage is being investigated by Tenable Research and this blog post will be updated accordingly.

Get more information

Ingress-nginx CVE-2025-1974: What You Need to Know IngressNightmare: Vulnerabilities in Ingress NGINX Join Tenable’s Security Response Team on the Tenable Community.
Learn more about Tenable One, the Exposure Management Platform for the modern attack surface.

First seen on securityboulevard.com

Jump to article: securityboulevard.com/2025/03/cve-2025-1097-cve-2025-1098-cve-2025-1974-cve-2025-24513-cve-2025-24514-frequently-asked-questions-about-ingressnightmare/

Loading

Share via Email
Share on Facebook
Tweet on X (Twitter)
Share on Whatsapp
Share on LinkedIn
Share on Xing
Copy link