Last scanned:
This image is acceptable for production, but remediating the identified vulnerabilities is recommended to reduce the attack surface. The main practical risk is remote CPU exhaustion and service unavailability through crafted HTTP/2 SETTINGS frames or HTTP Range headers, tracked as CVE-2026-78669 and CVE-2026-78667. These DoS issues are applicable where the affected HTTP/2/gRPC or file-serving paths are reachable; restricting untrusted HTTP/2/gRPC access would fully eliminate the CVE-2026-78669 remote exposure. The remaining post-exploit findings are low severity, with no severity >= 6.0, so they do not raise the verdict beyond NEEDS_ATTENTION.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-78669 | MEDIUM6.38 | golang.org/x/net v0.58.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-78667 | MEDIUM6.38 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-78669 | MEDIUM6.38 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-63073 | MEDIUM5.9 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56866 | MEDIUM5.52 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-94439 | MEDIUM5.52 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-94448 | MEDIUM5.18 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-97031 | MEDIUM5.1 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97032 | MEDIUM5.02 | golang.org/x/net v0.58.0 fixed in 0.60.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-97032 | MEDIUM5.02 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56855 | MEDIUM4.5 | golang.org/x/crypto v0.55.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78662 | MEDIUM4.5 | golang.org/x/crypto v0.55.0 fixed in 0.56.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | MEDIUM4.5 | golang.org/x/net v0.58.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | MEDIUM4.5 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.15 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.15 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56857 | LOW2.8 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | LOW2.7 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63076 | LOW2.7 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-14457 | LOW2.7 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-18798 | LOW2.7 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63076 | LOW2.7 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-14457 | LOW2.7 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-14456 | LOW2.29 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-63072 | LOW2.29 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-54874 | LOW2.29 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63074 | LOW2.29 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63075 | LOW2.29 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-14456 | LOW2.29 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-63072 | LOW2.29 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-54874 | LOW2.29 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63074 | LOW2.29 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63075 | LOW2.29 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.8% Theoretical Threat | Post-Exploit |
| 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.55.0 No fix yet | — | Not Applicable |
| CVE-2026-78659 | NONE0 | golang.org/x/net v0.58.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | golang.org/x/net v0.58.0 fixed in 0.60.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.27.1 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.