CVE-2025-1097High· 8.8▾ MidnightPoC availablengress-nginx controller - configuration injection via unsanitized auth-tls-match-cn annotation
▾ Midnight zone — Critical, or high with PoC / in-the-wild
impact 48.4 · likelihood 7.1 · exploitation 12
A public proof-of-concept already exists for this vulnerability — see Exploit availability below.
Public exploit / PoC code seen in 3 sources. Availability, not in-the-wild use.
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
36%
Exploit-DB · 2 GitHub repos · Nuclei ×1 (last check)
A security issue was discovered in ingress-nginx where the auth-tls-match-cn Ingress annotation can be used to inject configuration into nginx. This can lead to arbitrary code execution in the context of the ingress-nginx controller, and disclosure of Secrets accessible to the controller. (Note that in the default installation, the controller can access all Secrets cluster-wide.)
k8s.io/ingress-nginx < 1.11.5k8s.io/ingress-nginx >= 1.12.0-beta.0, < 1.12.1Upgrade to a patched release:
k8s.io/ingress-nginx 1.11.5k8s.io/ingress-nginx 1.12.1Connected by shared product, vendor, weakness, or advisory.
CVE-2025-24513Medium· 4.8ingress-nginx controller - auth secret file path traversal vulnerability
CVE-2026-24514Medium· 6.5ingress-nginx vulnerable to Allocation of Resources Without Limits or Throttling
CVE-2026-24513Low· 3.1ingress-nginx has Improper Check for Unusual or Exceptional Conditions
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