CVE-2026-24513: low-severity vulnerability in Kubernetes ingress-nginx
ingress-nginx auth-url protection bypass
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
8Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 3.1epss 0.3%
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.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
Affected products
Kubernetes · ingress-nginxRelated CVEs — Kubernetes ingress-nginx
In the same product, most dangerous first.
CVE-2023-5044HIGHCode injection via nginx.ingress.kubernetes.io/permanent-redirect annotationEPSS 53.7%CVE-2024-7646HIGHCVE-2024-7646EPSS 27.0%CVE-2026-3288HIGHingress-nginx rewrite-target nginx configuration injectionEPSS 7.0%CVE-2023-5043HIGHIngress nginx annotation injection causes arbitrary command executionEPSS 2.5%CVE-2022-4886HIGHIngress-nginx `path` sanitization can be bypassed with `log_format` directiveEPSS 1.7%CVE-2026-4342HIGHingress-nginx comment-based nginx configuration injectionEPSS 1.5%