Kubernetes vulnerabilitiesRanked by how likely they are to be used.
Kubernetes is made by Jenkins. We track 7 published vulnerabilities listed under that exact name, across 82 versions. None of them is on the list of flaws known to be exploited today. Jenkins lists newer releases under their own names, such as Kubernetes Ci, so check those pages too.
We keep watching the known-exploited list.
Is Kubernetes listed under other names? Yes.
Jenkins also lists Kubernetes under more specific names, such as Kubernetes Ci and Kubernetes Continuous Deploy. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Kubernetes vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Kubernetes's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Kubernetes 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.
- 1.6%CVE-2021-21661Medium
Jenkins Kubernetes CLI Plugin 1.10.0 and earlier does not perform permission checks in several HTTP endpoints, allowing attackers with Overall/Read permission to enumerate credentials IDs of credentials stored in...
- 1.4%CVE-2018-1999040High
An exposure of sensitive information vulnerability exists in Jenkins Kubernetes Plugin 1.10.1 and earlier in KubernetesCloud.java that allows attackers to capture credentials with a known credentials ID stored in...
- 1.3%CVE-2018-1000187Medium
A exposure of sensitive information vulnerability exists in Jenkins Kubernetes Plugin 1.7.0 and older in ContainerExecDecorator.java that results in sensitive variables such as passwords being written to logs.
- 1.3%CVE-2020-2307Medium
Jenkins Kubernetes Plugin 1.27.3 and earlier allows low-privilege users to access possibly sensitive Jenkins controller environment variables.
- 1.2%CVE-2020-2308Medium
A missing permission check in Jenkins Kubernetes Plugin 1.27.3 and earlier allows attackers with Overall/Read permission to list global pod template names.
- 1.1%CVE-2020-2309Medium
A missing/An incorrect permission check in Jenkins Kubernetes Plugin 1.27.3 and earlier allows attackers with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins.
- 0.5%CVE-2023-30513High
Jenkins Kubernetes Plugin 3909.v1f2c633e8590 and earlier does not properly mask (i.e., replace with asterisks) credentials in the build log when push mode for durable task logging is enabled.
Running Kubernetes? 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
Jenkins Kubernetes CLI Plugin 1.10.0 and earlier does not perform permission checks in several HTTP endpoints, allowing attackers with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins.
- Matched to
- Kubernetes 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 7 published vulnerabilities listed under the name Kubernetes, across 82 versions.
None of Kubernetes's vulnerabilities is on the list of flaws known to be exploited today.
Jenkins also lists Kubernetes under more specific names, such as Kubernetes Ci and Kubernetes Continuous Deploy. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Kubernetes. 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.