Container Images With Known Vulnerabilities
Container images in use contain operating system packages or libraries with publicly known vulnerabilities for which fixes are available.
| Severity | High |
| CVSS 3.1 | 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H Open in the calculator |
| CVSS 4.0 | 9.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-1395: Dependency on Vulnerable Third-Party Component |
| OWASP Top 10 | A03:2025 Software Supply Chain Failures |
| MITRE ATT&CK | T1190 Exploit Public-Facing Application, T1210 Exploitation of Remote Services |
| Category | Outdated Components |
Description
Container images bundle an operating system userland and application dependencies, which stay at the versions present when the image was built. Unless images are rebuilt and redeployed regularly, they accumulate packages and libraries with publicly known vulnerabilities, even when the application code itself has not changed. Images based on full distributions also carry many packages the application never uses, such as shells, compilers and package managers, and images whose base distribution has reached end of life receive no fixes at all.
Depending on the vulnerability, an attacker who can reach a vulnerable component may be able to exploit it to run code in the container, read data or cause a denial of service. Code execution in a container exposes its data, secrets and service account token, and is the usual first step towards attacking the node and the rest of the cluster.
The weakness is identified by scanning images, in registries or as deployed, with tools such as Trivy or Grype, which compare installed package versions with vulnerability databases and report CVE identifiers, severities and fixed versions. Scanner output needs interpretation, because the real risk depends on which vulnerabilities are exploitable in the way the image is used: a vulnerability matters most when the affected component is reachable by an attacker, for example a network-facing library or the runtime the application uses, and much less when it sits in a package that is never executed. Remotely exploitable flaws in network-facing components therefore deserve priority.
Remediation
- Rebuild images regularly from updated base images and dependency versions, and redeploy them, rather than running images built once; automate this in the CI/CD pipeline.
- Scan images in the pipeline and fail builds that introduce critical or high-severity vulnerabilities with available fixes, and rescan deployed images continuously as new vulnerabilities are published.
- Use minimal base images, such as distroless or slim variants that contain only what the application needs, and keep package managers and shells out of production images.
- Replace base images whose distribution is no longer supported.
- Prioritise fixes by exploitability, starting with network-facing components and vulnerabilities known to be exploited in the wild, such as those in CISA's Known Exploited Vulnerabilities catalogue.
- Use admission policies to stop images that fail scanning, or that come from unapproved registries, from running.
Confirm the fix by rescanning the deployed images and checking that the reported vulnerabilities are gone or formally accepted.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.