Last scanned:
This image is safe for production use. It has a pre-calculated threat score of 0, and the provided vulnerability stats show 3 exposed findings, none at severity 6.0 or higher, with an exposed max severity of 0.0. No post-exploit-only findings are present, and no CVE IDs were provided in the findings to cite. The image also benefits from strong trust signals: a popular community publisher, a reliable reputation verdict, and digest pinning for immutability.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-107891 | NONE0 | musl 1.2.6-r2 fixed in 1.2.6-r3 | — | Not Applicable |
| CVE-2026-107891 | NONE0 | musl-utils 1.2.6-r2 fixed in 1.2.6-r3 | — | Not Applicable |
| CVE-2026-85091 | NONE0 | zlib 1.3.2-r0 fixed in 1.3.2-r1 | 0.4% Theoretical Threat | Not Applicable |
| GO-2026-5932 | NONE0 | golang.org/x/crypto v0.58.0 No fix yet | — | 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.