Kubernetes ingress-nginx up to 1.11.4/1.12.0 IngressNightmare input validation

Summaryinfo

A vulnerability was found in Kubernetes ingress-nginx up to 1.11.4/1.12.0. It has been classified as very critical. Impacted is an unknown function. Performing a manipulation results in input validation. This vulnerability is identified as CVE-2025-24514. The attack can be initiated remotely. Additionally, an exploit exists.

Detailsinfo

A vulnerability was found in Kubernetes ingress-nginx up to 1.11.4/1.12.0. It has been classified as very critical. This affects an unknown code block. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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 configuration into nginx. This can lead to arbitrary code execution in the context of the ingress-nginx controller, and disclosure of Secrets accessible to the controller. (Note that in the default installation, the controller can access all Secrets cluster-wide.)

The weakness was released by Sagi Tzadik as 131006. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-24514 since 01/23/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are unknown but a public exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/06/2026).

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at Exploit-DB (52475) and CERT Bund (WID-SEC-2025-0629). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Affected

• SUSE openSUSE
• IBM InfoSphere Information Server
• Open Source Kubernetes

Productinfo

Type

• Virtualization Software

Vendor

• Kubernetes

Name

• ingress-nginx

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.10
• 1.11
• 1.11.0
• 1.11.1
• 1.11.2
• 1.11.3
• 1.11.4
• 1.12.0

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion