3.1
Low
CVE-2026-24513 A security issue was discovered in ingress-nginx where the protection afforded by the `auth-url` Ingress annotation…
Description
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.
Affected products and versions
| Product | Affected versions | Fixed in |
|---|---|---|
| ingress-nginx 1.14 | earliest → < 1.14.3 | 1.14.3 |
| ingress-nginx 1.13 | earliest → < 1.13.7 | 1.13.7 |
Other CVEs of ingress-nginx
The 18 CVEs of ingress-nginx →
CVE-2026-116472
ingress-nginx mirror-target self-DOS
2.7
Low
CVE-2026-4342
A security issue was discovered in ingress-nginx where a combination of Ingress annotations can be used to inject…
8.8
High
CVE-2026-3288
A security issue was discovered in ingress-nginx where the `nginx.ingress.kubernetes.io/rewrite-target` Ingress…
8.8
High
CVE-2025-15566
A security issue was discovered in ingress-nginx where the `nginx.ingress.kubernetes.io/auth-proxy-set-headers`…
8.8
High