CVE-2026-24512 Affecting ingress-nginx-controller-1.13 package, versions <1.13.9-r14
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CHAINGUARDLATEST-INGRESSNGINXCONTROLLER113-17801774
- published3 Jul 2026
- disclosed3 Feb 2026
Introduced: 3 Feb 2026
CVE-2026-24512 (opens in a new tab)How to fix?
Upgrade Chainguard ingress-nginx-controller-1.13 to version 1.13.9-r14 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream ingress-nginx-controller-1.13 package and not the ingress-nginx-controller-1.13 package as distributed by Chainguard.
See How to fix? for Chainguard relevant fixed versions and status.
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.)