GHSA-4g2f-xcph-2335
ingress-nginx has Improper Check for Unusual or Exceptional Conditions
At a glance
- Published
- Updated
- CVE
- CVE-2026-24513
- Aliases
- GO-2026-4419
- CVSS_V3
- CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
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.
Affected packages
| Package | Versions |
|---|---|
| Go · k8s.io/ingress-nginx | introduced 0, fixed 1.13.7 |
| Go · k8s.io/ingress-nginx | introduced 1.14.0, fixed 1.14.3 |
References
- https://nvd.nist.gov/vuln/detail/CVE-2026-24513 ADVISORY
- https://github.com/kubernetes/kubernetes/issues/136679 WEB
- https://github.com/kubernetes/ingress-nginx PACKAGE
Sources
| Source | Licence |
|---|---|
| OSV.dev | CC-BY 4.0 — GitHub Advisory Database |