Last scanned:
This image is safe for production use. The provided stats show 2 exposed and 1 post-exploit item, but their maximum severity is 0.0 and no CVE IDs appear in the top findings, so these do not alter the verdict. It is an official Docker Hub image pinned by digest, with a trust score of 100. No specific CVE mitigations or configuration caveats are applicable from the provided inputs.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-107891 | NONE0 | musl 1.2.5-r23 fixed in 1.2.5-r24 | — | Not Applicable |
| CVE-2026-107891 | NONE0 | musl-utils 1.2.5-r23 fixed in 1.2.5-r24 | — | 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.