Last scanned:
This base/runtime image is a clean foundation for building production images. It is an official Docker Hub image pinned by digest, and the provided stats show no exposed-surface vulnerabilities and a maximum exposed severity of 0.0. There is one post-exploit-only finding with max severity 2.92, which is below the thresholds for attention in this context. Images built on top of it should still follow normal patching and scanning practices, but the provided inputs do not indicate meaningful inherited risk. 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-111497 | LOW2.92 | brotli-libs 1.2.0-r1 fixed in 1.2.1-r0 | — | Post-Exploit |
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.