Last scanned:
This base/runtime image is a clean foundation for building production images. It is an official Docker Hub image pinned by digest, which supports reproducibility and provenance. The provided stats show one exposed-surface entry, but its maximum severity is 0.0 and there are no findings at 6.0 or above; post-exploit-only total is 0. No CVE IDs were present in the supplied findings, so there are no specific inherited CVEs to remediate from this data. 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.