CVE-2021-25748Medium· 6.5▾ SunlitIngress-nginx `path` sanitization can be bypassed with newline character
▾ Sunlit zone — Low / medium · no exploitation signal
impact 35.8 · 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 Aug 7.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.7%
A security issue was discovered in ingress-nginx where a user that can create or update ingress objects can use a newline character to bypass the sanitization of the spec.rules[].http.paths[].path field of an Ingress object (in the networking.k8s.io or extensions API group) to obtain the credentials of the ingress-nginx controller. In the default configuration, that credential has access to all secrets in the cluster.
k8s.io/ingress-nginx < 1.2.1Upgrade to a patched release:
k8s.io/ingress-nginx 1.2.1Connected 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-24513Low· 3.1ingress-nginx has Improper Check for Unusual or Exceptional Conditions
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