Last scanned:
This base/runtime image is a clean foundation for building production images. The supplied stats list 1 exposed finding, but it has a maximum severity of 0.0, no findings at 6.0 or higher, and no post-exploit-only findings; the pre-calculated threat score is 0. The image is an official Docker Hub image pinned by digest, so provenance is trusted. Any images built on top would inherit this low-risk baseline, though their own added packages and configuration still need normal review. No CVE IDs are available in the provided findings to cite. Note: this is a general-purpose base/runtime image — many findings live in components that an application built on top may never load, so actual exploitability depends on the final image. For an accurate risk picture, re-scan the final application image with context.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-85091 | NONE0 | zlib 1.3.2-r0 fixed in 1.3.2-r1 | 0.4% Theoretical Threat | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.