Last scanned:
··This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker who supplies a malicious image or build context could exploit CVE-2026-17106 to write arbitrary files on the host as root, which could lead to host tampering or a broader compromise of the build infrastructure. The image runs as root by default and the flaw needs no special configuration, so the risk applies in standard deployments. Other findings in the scan are lower severity and matter only after the container is already compromised. Treat this image as a build component that needs strict isolation and a patched or updated release before production use.
Hardening plan for this image · 3 steps
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-17106 | HIGH7.8 | github.com/moby/go-archive v0.2.0 fixed in 0.3.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-97032 | MEDIUM5.9 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-32288 | MEDIUM5.5 | stdlib v1.25.7 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-10722 | MEDIUM5.5 | github.com/cilium/ebpf v0.17.3 fixed in 0.22.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-61801 | MEDIUM5.5 | github.com/moby/sys/user v0.4.0 fixed in 0.4.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27142 | MEDIUM5.4 | stdlib v1.25.7 fixed in 1.25.8, 1.26.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39823 | MEDIUM5.4 | stdlib v1.25.7 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39826 | MEDIUM5.4 | stdlib v1.25.7 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42505 | MEDIUM5.3 | stdlib v1.25.7 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42507 | MEDIUM5.3 | stdlib v1.25.7 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | MEDIUM5.3 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56862 | MEDIUM4.5 | stdlib v1.25.7 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78667 | MEDIUM4.5 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78669 | MEDIUM4.5 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-97031 | MEDIUM4.5 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78659 | MEDIUM4.5 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78660 | MEDIUM4.5 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-94440 | MEDIUM4.5 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-111943 | MEDIUM4.08 | stdlib v1.25.7 fixed in 1.26.10, 1.27.3 | 0.4% Theoretical Threat | Directly Exposed |
| GO-2026-5932 | MEDIUM4 | golang.org/x/crypto v0.57.0 No fix yet | — | Directly Exposed |
| CVE-2026-39824 | MEDIUM4 | golang.org/x/sys v0.35.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-39825 | LOW3.9 | stdlib v1.25.7 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56866 | LOW3.9 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-94439 | LOW3.9 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32282 | LOW3.84 | stdlib v1.25.7 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32289 | LOW3.66 | stdlib v1.25.7 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-94448 | LOW3.66 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97030 | LOW3.66 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56857 | LOW3.3 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-39821 | LOW2.95 | stdlib v1.25.7 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-56858 | LOW2.92 | stdlib v1.25.7 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-39822 | LOW2.81 | stdlib v1.25.7 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78669 | LOW2.7 | golang.org/x/net v0.59.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-78659 | LOW2.7 | golang.org/x/net v0.59.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-78660 | LOW2.7 | golang.org/x/net v0.59.0 fixed in 0.60.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-25679 | LOW2.7 | stdlib v1.25.7 fixed in 1.25.8, 1.26.1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-27145 | LOW2.7 | stdlib v1.25.7 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-32280 | LOW2.7 | stdlib v1.25.7 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-32281 | LOW2.7 | stdlib v1.25.7 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-32283 | LOW2.7 | stdlib v1.25.7 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-33811 | LOW2.7 | stdlib v1.25.7 fixed in 1.25.10, 1.26.3 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-33814 | LOW2.7 | stdlib v1.25.7 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-33818 | LOW2.7 | stdlib v1.25.7 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-39820 | LOW2.7 | stdlib v1.25.7 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-39836 | LOW2.7 | stdlib v1.25.7 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42499 | LOW2.7 | stdlib v1.25.7 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-42504 | LOW2.7 | stdlib v1.25.7 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-56853 | LOW2.7 | stdlib v1.25.7 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-56859 | LOW2.7 | stdlib v1.25.7 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-56860 | LOW2.7 | stdlib v1.25.7 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46600 | LOW2.7 | golang.org/x/net v0.55.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-78669 | LOW2.7 | golang.org/x/net v0.55.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-78659 | LOW2.7 | golang.org/x/net v0.55.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-78660 | LOW2.7 | golang.org/x/net v0.55.0 fixed in 0.60.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27139 | LOW2.5 | stdlib v1.25.7 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-97032 | LOW2.12 | golang.org/x/net v0.59.0 fixed in 0.60.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-97032 | LOW2.12 | golang.org/x/net v0.55.0 fixed in 0.60.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-78663 | LOW1.91 | golang.org/x/net v0.59.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-78663 | LOW1.91 | golang.org/x/net v0.55.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Post-Exploit |
Want to check another image? Run a full scan with the Docker Security Scanner.