When NGINX Ingress Controller is configured with Custom Resource Definitions (CRDs) or Ingress annotations, an injection vulnerability exists in the configuration generator of NGINX Ingress Controller. Multiple user-controllable fields are written into the generated NGINX configuration without sanitization. An authenticated attacker with permission to create or modify these CRDs or annotations may craft values that inject arbitrary NGINX configuration directives. Impact: An authenticated attacker granted write access to NGINX Ingress Controller CRDs or Ingress annotations through the Kubernetes API may be able to inject arbitrary NGINX configuration directives, create or delete files, or disable services. There is no data plane exposure; this is a control plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://my.f5.com/manage/s/article/K000161800 Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 8.7 · f5NVD modified 2026-10-24 21:10
Affected (CPE criteria) 1
cpe:2.3:a:f5:nginx_ingress_controller:*:*:*:*:*:*:*:*
References 1
- https://my.f5.com/manage/s/article/K000161800 Mitigation, Vendor Advisory