Last scanned:
This image is safe for production use. Although the supplied stats show 13 exposed findings and 12 post-exploit-only findings, none reach severity 6.0; the maximum exposed severity is 5.1 and the maximum post-exploit-only severity is 2.51. The image also has a RELIABLE trust verdict with a score of 90, popular community usage, and digest pinning for immutability. No CVE IDs were provided in the top findings, so no specific CVE-driven risk can be highlighted from the supplied data. Maintain the digest pin and monitor future image updates, but the current evidence does not justify blocking production deployment.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-33818 | MEDIUM5.1 | stdlib v1.26.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56862 | MEDIUM5.1 | stdlib v1.26.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78669 | MEDIUM5.1 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97032 | MEDIUM4.02 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56853 | LOW3.83 | stdlib v1.26.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-97031 | LOW3.83 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | LOW3.6 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56857 | LOW2.8 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-39821 | LOW2.51 | stdlib v1.26.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-56858 | LOW2.48 | stdlib v1.26.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-46600 | LOW2.29 | stdlib v1.26.5 fixed in 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-56859 | LOW2.29 | stdlib v1.26.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-56860 | LOW2.29 | stdlib v1.26.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-78667 | LOW2.29 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-56854 | LOW2.08 | golang.org/x/crypto v0.54.0 fixed in 0.55.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-56866 | LOW1.99 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-94439 | LOW1.99 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-94448 | LOW1.87 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56855 | LOW1.62 | golang.org/x/crypto v0.54.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-78662 | LOW1.62 | golang.org/x/crypto v0.54.0 fixed in 0.56.0 | 0.4% Theoretical Threat | Post-Exploit |
| GO-2026-5932 | NONE0 | golang.org/x/crypto v0.54.0 No fix yet | — | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.2% 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.