Kubernetes ingress-nginx up to 1.13.6/1.14.1 rules.http.paths.path input validation

Summaryinfo

A vulnerability was found in Kubernetes ingress-nginx up to 1.13.6/1.14.1. It has been classified as very critical. This affects an unknown part. Performing a manipulation of the argument rules.http.paths.path results in input validation. This vulnerability is identified as CVE-2026-24512. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as very critical, was found in Kubernetes ingress-nginx up to 1.13.6/1.14.1. This affects an unknown code block. The manipulation of the argument rules.http.paths.path 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 where the `rules.http.paths.path` Ingress field 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 advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-24512 since 01/23/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/09/2026).

The vulnerability scanner Nessus provides a plugin with the ID 297852 (Ingress-NGINX Controller < 1.13.7 / 1.14.x < 1.14.3 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 1.13.7 or 1.14.2 eliminates this vulnerability.

The vulnerability is also documented in the databases at Tenable (297852), EUVD (EUVD-2026-6096) and CERT Bund (WID-SEC-2026-0289). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

• Open Source Kubernetes

Productinfo

Type

• Virtualization Software

Vendor

• Kubernetes

Name

• ingress-nginx

Version

• 1.13.0
• 1.13.1
• 1.13.2
• 1.13.3
• 1.13.4
• 1.13.5
• 1.13.6
• 1.14.0
• 1.14.1

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion