Last scanned:
This image is acceptable for production, but remediating the identified vulnerabilities is recommended to reduce the attack surface. The main exposed issue is CVE-2026-78669, an HTTP/2 SETTINGS-frame denial-of-service flaw that can let remote clients exhaust CPU in Traefik's HTTPS handling and cause an outage. No exposed CVE reaches the ge7 band (exposed_count_ge7 is 0), and the post-exploit findings are low severity (post_max_severity 1.87). The issue applies without special configuration per the provided analysis, and no full compensating control is specified in the inputs. Because the image is an official, digest-pinned Docker image, the overall production posture remains acceptable with remediation recommended.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-78669 | MEDIUM6.38 | golang.org/x/net v0.59.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-78669 | MEDIUM6.38 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-78667 | MEDIUM5.1 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97031 | MEDIUM5.1 | stdlib v1.26.8 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.59.0 fixed in 0.60.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-97032 | MEDIUM5.02 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-56866 | MEDIUM4.42 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-94439 | MEDIUM4.42 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78663 | LOW3.6 | golang.org/x/net v0.59.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78663 | LOW3.6 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56857 | LOW2.8 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-94448 | LOW1.87 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.2% 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.57.0 No fix yet | — | Not Applicable |
| CVE-2026-78659 | NONE0 | golang.org/x/net v0.59.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | golang.org/x/net v0.59.0 fixed in 0.60.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.26.8 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.