Ingress-nginx contains a flaw that allows an attacker to inject configuration directives into nginx by manipulating the path field of an Ingress resource. This vulnerability can lead to arbitrary code execution within the ingress-nginx controller and the disclosure of Secrets the controller can read, which in a default installation includes all cluster Secrets.

The vulnerability affects installations of the ingress-nginx controller for Kubernetes. Specific affected versions are not listed, so any version of the controller that has not yet applied the fix is potentially impacted. The default configuration permits the controller to access every Secret cluster‑wide, increasing the risk.

With a CVSS score of 8.8, the vulnerability is considered high severity. Its EPSS score is less than 1%, indicating a very low probability of public exploitation at present. The vulnerability is not in the CISA KEV catalog. Exploitation would require the ability to create or modify an Ingress object with a crafted path field; the attack vector is likely internal to the cluster and dependent on role‑based access controls that allow users to create Ingress resources.