Ingress-Nginx vulnerabilitiesRanked by how likely they are to be used.
Ingress-Nginx is made by Kubernetes. We track 8 published vulnerabilities in it, across 119 versions. None of them is on the list of flaws known to be exploited today. If you run Ingress-Nginx, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Ingress-Nginx vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Ingress-Nginx's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Ingress-Nginx flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 57%CVE-2023-5044High
Code injection via nginx.ingress.kubernetes.io/permanent-redirect annotation.
- 2.2%CVE-2023-5043High
Ingress nginx annotation injection causes arbitrary command execution.
- 2.1%CVE-2021-25742High
A security issue was discovered in ingress-nginx where a user that can create or update ingress objects can use the custom snippets feature to obtain all secrets in the cluster.
- 1.6%CVE-2022-4886High
Ingress-nginx `path` sanitization can be bypassed with `log_format` directive.
- 1.4%CVE-2021-25746High
A security issue was discovered in ingress-nginx where a user that can create or update ingress objects can use .metadata.annotations in an Ingress object (in the networking.k8s.io or extensions API group) to obtain...
- 1.2%CVE-2021-25745High
A security issue was discovered in ingress-nginx where a user that can create or update ingress objects can use the spec.rules[].http.paths[].path field of an Ingress object (in the networking.k8s.io or extensions...
- 0.9%CVE-2020-8553Medium
The Kubernetes ingress-nginx component prior to version 0.28.0 allows a user with the ability to create namespaces and to read and create ingress objects to overwrite the password file of another ingress which uses...
- 0.7%CVE-2021-25748Medium
A security issue was discovered in ingress-nginx where a user that can create or update ingress objects can use a newline character to bypass the sanitization of the `spec.rules[].http.paths[].path` field of an...
Running Ingress-Nginx? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Code injection via nginx.ingress.kubernetes.io/permanent-redirect annotation.
- Matched to
- Ingress-Nginx on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 8 published vulnerabilities listed under the name Ingress-Nginx, across 119 versions.
None of Ingress-Nginx's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Ingress-Nginx. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.