ingress-nginx controller - configuration injection via unsanitized mirror annotations
A security issue was discovered in [ingress-nginx](https://github.com/kubernetes/ingress-nginx) where the `mirror-target` and `mirror-host` Ingress annotations can be used to inject arbitrary 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.)
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-1098US | — | Exploit | ||
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `mirror-target` and `mirror-host` Ingress annotations can be used to inject… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/kubernetes/ingress-nginxPACKAGE
- https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.11.5WEB
- https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.12.1WEB
- https://github.com/kubernetes/kubernetes/issues/131008WEB
- https://groups.google.com/g/kubernetes-security-announce/c/2qa9DFtN0cQWEB
- https://nvd.nist.gov/vuln/detail/CVE-2025-1098ADVISORY
- https://security.netapp.com/advisory/ntap-20250328-0008WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan