CVE-2023-5043High· 7.6▾ MidnightPoC availableIngress nginx annotation injection causes arbitrary command execution
▾ Midnight zone — Critical, or high with PoC / in-the-wild
impact 41.8 · likelihood 0.4 · exploitation 12
A public proof-of-concept already exists for this vulnerability — see Exploit availability below.
Public exploit / PoC code seen in 1 source. Availability, not in-the-wild use.
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
2.2%
1 GitHub repo
A security issue was identified in ingress-nginx where the nginx.ingress.kubernetes.io/configuration-snippet annotation on an Ingress object (in the networking.k8s.io or extensions API group) can be used to inject arbitrary commands, and obtain the credentials of the ingress-nginx controller. In the default configuration, that credential has access to all secrets in the cluster.
This issue has been rated High (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L), and assigned CVE-2023-5043.
This bug affects ingress-nginx. If you do not have ingress-nginx installed on your cluster, you are not affected. You can check this by running kubectl get po -n ingress-nginx.
If you are running the “chrooted” ingress-nginx controller introduced in v1.2.0 (gcr.io/k8s-staging-ingress-nginx/controller-chroot), command execution is possible but credential extraction is not, so the High severity does not apply.
Multi-tenant environments where non-admin users have permissions to create Ingress objects are most affected by this issue.
<v1.9.0
v1.9.0
Ingress Administrators should set the --enable-annotation-validation flag to enforce restrictions on the contents of ingress-nginx annotation fields.
If you find evidence that this vulnerability has been exploited, please contact [email protected]
See ingress-nginx Issue #10571 for more details.
This vulnerability was reported by suanve
Thank You, CJ Cullen on behalf of the Kubernetes Security Response Committee
k8s.io/ingress-nginx < 1.9.0Upgrade to a patched release:
k8s.io/ingress-nginx 1.9.0Field changes observed since this record was first indexed.
Connected 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-2026-24513Low· 3.1ingress-nginx has Improper Check for Unusual or Exceptional Conditions
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