CVE-2026-24513Low· 3.1▾ Sunlitingress-nginx has Improper Check for Unusual or Exceptional Conditions
▾ Sunlit zone — Low / medium · no exploitation signal
impact 17.1 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Sep 12.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.3%
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.
k8s.io/ingress-nginx < 1.13.7k8s.io/ingress-nginx >= 1.14.0, < 1.14.3Upgrade to a patched release:
k8s.io/ingress-nginx 1.13.7k8s.io/ingress-nginx 1.14.3Connected by shared product, vendor, weakness, or advisory.
CVE-2025-1097High· 8.8ngress-nginx controller - configuration injection via unsanitized auth-tls-match-cn annotation
CVE-2026-24514Medium· 6.5ingress-nginx vulnerable to Allocation of Resources Without Limits or Throttling
CVE-2025-24513Medium· 4.8ingress-nginx controller - auth secret file path traversal vulnerability
CVE-2021-25745High· 8.1Improper Input Validation in k8s.io/ingress-nginx
CVE-2018-1002104Medium· 5.3Kubernetes ingress exposes sensitive information
CVE-2020-8553Medium· 5.9ingress-nginx component for Kubernetes allows file overwrite