Last scanned:
This image is safe for production use. It is an official Docker Hub image pinned by digest, and the pre-calculated threat score is 0. The vulnerability stats show 2 exposed findings, but none reach severity 6.0 and the maximum exposed severity is 0.0, with no post-exploit-only findings. No CVE IDs are present in the provided top findings, so no specific CVEs are cited. Standard container hardening and digest-pinning remain good practice for production.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-107891 | NONE0 | musl 1.2.5-r12 fixed in 1.2.5-r13 | — | Not Applicable |
| CVE-2026-107891 | NONE0 | musl-utils 1.2.5-r12 fixed in 1.2.5-r13 | — | Not Applicable |
| 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.