Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker able to reach Traefik's HTTP/2 entrypoints could exploit CVE-2026-78669 to exhaust CPU and degrade or disrupt proxy availability for every backend service behind it. CVE-2026-78667 is conditional rather than default: it only applies when file-serving endpoints such as the dashboard's static assets are exposed, and disabling the dashboard and any such static file endpoints would fully eliminate that exposure. Note that the HTTP/2 denial-of-service finding affects both the bundled Go standard library and golang.org/x/net, so remediating only one of the two packages leaves the risk in place.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-78669 | HIGH7.5 | golang.org/x/net v0.59.0 fixed in 0.60.0 | — | Directly ExposedContext importance: HIGH |
| CVE-2026-78669 | HIGH7.5 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | — | Directly ExposedContext importance: HIGH |
| CVE-2026-78667 | MEDIUM6 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97032 | MEDIUM5.9 | golang.org/x/net v0.59.0 fixed in 0.60.0 | — | Directly ExposedContext importance: HIGH |
| CVE-2026-97032 | MEDIUM5.9 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | — | Directly ExposedContext importance: HIGH |
| CVE-2026-56866 | MEDIUM5.2 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-94448 | MEDIUM4.88 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97031 | MEDIUM4.5 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | — | Directly Exposed |
| CVE-2026-78663 | MEDIUM4.24 | golang.org/x/net v0.59.0 fixed in 0.60.0 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78663 | MEDIUM4.24 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-94439 | LOW3.9 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | — | Directly Exposed |
| CVE-2026-56857 | LOW3.3 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | — | Directly Exposed |
| CVE-2026-85091 | NONE0 | zlib 1.3.2-r0 fixed in 1.3.2-r1 | 0.6% 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 | — | Not Applicable |
| CVE-2026-78660 | NONE0 | golang.org/x/net v0.59.0 fixed in 0.60.0 | — | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | — | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | — | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | — | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | — | 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.