k8s.io/ingress-nginx
Affected
- introduced
0, fixed1.13.7(semver)
Fixed versions
1.13.7
Fix
- Fixed version
1.13.7go get k8s.io/[email protected]
Advisory
Also known as: CVE-2026-24513, GO-2026-4419
ingress-nginx has Improper Check for Unusual or Exceptional Conditions
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.
Low Basis: The source's own band: LOW
0, fixed 1.13.7 (semver)1.13.7
1.13.7go get k8s.io/[email protected]1.14.0, fixed 1.14.3 (semver)1.14.3
1.14.3go get k8s.io/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0