Image Builder vulnerabilitiesRanked by how likely they are to be used.
Image Builder is made by Kubernetes. We track 2 published vulnerabilities in it, across 0 versions. None of them is on the list of flaws known to be exploited today. If you run Image Builder, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Image Builder vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Image Builder's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Image Builder 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.
- 2.2%CVE-2024-9486Critical
A security issue was discovered in the Kubernetes Image Builder versions <= v0.1.37 where default credentials are enabled during the image build process.
- 1.7%CVE-2024-9594High
A security issue was discovered in the Kubernetes Image Builder versions <= v0.1.37 where default credentials are enabled during the image build process when using the Nutanix, OVA, QEMU or raw providers.
Running Image Builder? 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
A security issue was discovered in the Kubernetes Image Builder versions <= v0.1.37 where default credentials are enabled during the image build process. Virtual machine images built using the Proxmox provider do not disable these default credentials, and nodes using the resulting images may be accessible via these default credentials. The credentials can be used to gain root access. Kubernetes clusters are only affected if their nodes use VM images created via the Image Builder project with its Proxmox provider.
- Matched to
- Image Builder 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 2 published vulnerabilities listed under the name Image Builder, across 0 versions.
None of Image Builder's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Image Builder. 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.