Last scanned:
This image is safe for production use. The vulnerability stats report 3 exposed findings, but none reach severity 6.0 or higher and the maximum severity is 5.44, with no post-exploit findings. The image comes from a popular community publisher rated reliable and is pinned by digest. No specific CVE IDs are present in the supplied top findings, so no CVE-specific mitigations are required by this assessment.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-111943 | MEDIUM5.44 | stdlib v1.27.2 fixed in 1.26.10, 1.27.3 | — | Directly ExposedContext importance: MEDIUM |
| 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.