Last scanned:
This image is safe for production use. It has two exposed items reported, but the maximum exposed severity is 5.44 and there are zero exposed findings at or above severity 6 or 7; no post-exploit-only findings are present. The image also benefits from strong community reputation, over 163 million pulls, and digest pinning, which reduces supply-chain ambiguity. No CVE IDs are present in the provided findings inputs, so no specific CVE-based risk is cited.
| 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 |
| 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.