NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2026-24513: ingress-nginx has Improper Check for Unusual or Exceptional Conditions

lowCVSS 3.1 3.1GHSA-4g2f-xcph-2335

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,…

Published Feb 4, 2026

Affected packages

k8s.io/ingress-nginx

Ecosystem
Go
Affected
< 1.13.7
Fixed in
1.13.7
Check
go list -m k8s.io/ingress-nginx

k8s.io/ingress-nginx

Ecosystem
Go
Affected
>= 1.14.0, < 1.14.3
Fixed in
1.14.3
Check
go list -m k8s.io/ingress-nginx

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Go vulnerabilities

All Go entries