CVE-2026-24513

published 3 Feb 2026 · updated 18 Feb 2026

ingress-nginx auth-url protection bypass

3.1LowCVSS 3.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 1.13.7 and 1.14.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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Kubernetes<1.13.7, <1.14.31.13.7, 1.14.3

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-24513 severity on Zeptric[![CVE-2026-24513](https://zeptric.io/badge/cve/CVE-2026-24513.svg)](https://zeptric.io/cve/CVE-2026-24513)