Vulnerability · Published Feb 3, 2026 · Assigned by kubernetes
CVE-2026-24513ingress-nginx auth-url protection bypass
Low 3.1
In plain English
A low-severity security flaw in ingress-nginx from Kubernetes. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 28% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official 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 packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Go | k8s.io/ingress-nginx | 1.13.7 | GHSA-4g2f-xcph-2335 |
| Go | k8s.io/ingress-nginx | 1.14.3 | GHSA-4g2f-xcph-2335 |
| Go | k8s.io/ingress-nginx | no fix listed | GO-2026-4419 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Kubernetes | ingress-nginx | 0 – before 1.13.70 – before 1.14.3 |
Weakness: CWE-754 · Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N