CVE-2026-24513 Affecting ingress-nginx-controller-1.15 package, versions *
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-MINIMOSLATEST-INGRESSNGINXCONTROLLER115-17216162
- published6 Jun 2026
- disclosed3 Feb 2026
Introduced: 3 Feb 2026
CVE-2026-24513 (opens in a new tab)How to fix?
There is no fixed version for Minimos:latest ingress-nginx-controller-1.15.
NVD Description
Note: Versions mentioned in the description apply only to the upstream ingress-nginx-controller-1.15 package and not the ingress-nginx-controller-1.15 package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
A security issue was discovered in ingress-nginx where the protection afforded by the auth-url Ingress annotation may not be effective in the presence of a specific misconfiguration.
If the ingress-nginx controller is configured with a default custom-errors configuration that includes HTTP errors 401 or 403, and if the configured default custom-errors backend is defective and fails to respect the X-Code HTTP header, then an Ingress with the auth-url annotation may be accessed even when authentication fails.
Note that the built-in custom-errors backend works correctly. To trigger this issue requires an administrator to specifically configure ingress-nginx with a broken external component.