GitHub Advisoryadvisory · Go
GHSA-4g2f-xcph-2335 ingress-nginx has Improper Check for Unusual or Exceptional Conditions
LOW
Official page ↗
- Aliases
- CVE-2026-24513
- Ecosystem
- Go
- Packages
- k8s.io/ingress-nginx
- Severity
- Low
- CVSS vector
- CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
- Weaknesses
- CWE-754
- Reviewed
- 2026-02-04
Affected packages
• Go k8s.io/ingress-nginx: < 1.13.7 → fixed in 1.13.7
• Go k8s.io/ingress-nginx: >= 1.14.0, < 1.14.3 → fixed in 1.14.3
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. Triggering this issue requires an administrator to specifically configure ingress-nginx with a broken external component.
Related
Alias · CVE (1)
- CVE-2026-24513 A security issue was discovered in ingress-nginx where the protection afforded by the `auth-url` Ingress annotation may not be effective in… vulnerability
Weakness · CWE (1)
- CWE-754 Improper Check for Unusual or Exceptional Conditions weakness