k8s.io/ingress-nginx (go) has 17 known vulnerabilities, the worst rated CRITICAL. Upgrade to 1.14.3 or later to clear all of them. No malicious-package signal is recorded.
A security issue was discovered in Kubernetes where under certain conditions, an unauthenticated attacker with access to the pod network can achieve arbitrary…
// questionsIs k8s.io/ingress-nginx safe to install?
CyberXYZ does not call a package safe in absolute terms. It records 17 known vulnerabilities for k8s.io/ingress-nginx (go), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does k8s.io/ingress-nginx have known vulnerabilities?
Yes. CyberXYZ records 17 known vulnerabilities for k8s.io/ingress-nginx (go), the worst rated CRITICAL. These include GHSA-mgvx-rpfc-9mpv, GHSA-f53h-mxv9-cp98, GHSA-9h3p-52vh-959w, GHSA-jx8c-56mg-h6vp, GHSA-fwwp-xcxw-39vq.
Which version of k8s.io/ingress-nginx should I use?
1.14.3 or later clears every advisory recorded for k8s.io/ingress-nginx (go). Check the release you pick before installing it.
How do I check k8s.io/ingress-nginx before installing?
Search k8s.io/ingress-nginx in CyberXYZ Check at https://cyberxyz.io/check?q=k8s.io%2Fingress-nginx. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 13:07 UTC. The most recent advisory here was published 2026-03-20. Updated continuously from NVD, GHSA, OSV and CNA feeds.