Last scanned:
This base/runtime image is a clean foundation for building production images. It is an official Docker Official image pinned by digest, with a trust score of 100 and a pre-calculated threat score of 0. Although the stats show exposed_total 1, the exposed findings include none at severity 6.0 or higher and the exposed max severity is 0.0, while post_total is 0. No CVE IDs appear in the provided top findings, so there is no CVE-level remediation to call out from the inputs. Any images built on top inherit this clean baseline; keep digest pinning and routine rebuilds in place. 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.