Last scanned:
This image is acceptable for production, but remediating the identified vulnerabilities is recommended to reduce the attack surface. The exposed findings are denial-of-service flaws in the Go HTTP stack that could let a malicious client slow or stall the manager API on port 9500. The impact is availability, not data theft or code execution, and no finding is marked as known exploited. Note: CVE-2026-78669 only applies when HTTP/2 is served to clients, and CVE-2026-94440 only applies if a multipart upload endpoint is enabled. Updating the affected Go and golang.org/x/net components is the recommended remediation, and reviewing the root default user is also advisable.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-78669 | MEDIUM6 | golang.org/x/net v0.58.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78659 | MEDIUM6 | golang.org/x/net v0.58.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78667 | MEDIUM6 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78669 | MEDIUM6 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78659 | MEDIUM6 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-94440 | MEDIUM6 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97032 | MEDIUM5.9 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | MEDIUM5.3 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-97032 | MEDIUM4.72 | golang.org/x/net v0.58.0 fixed in 0.60.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| SUSE-SU-2026:4568-1 | MEDIUM4.5 | rpcbind 0.2.3-150000.5.12.1 fixed in 0.2.3-150000.5.17.1 | — | Directly Exposed |
| CVE-2026-78660 | MEDIUM4.5 | golang.org/x/net v0.58.0 fixed in 0.60.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-97031 | MEDIUM4.5 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78660 | MEDIUM4.5 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | MEDIUM4.24 | golang.org/x/net v0.58.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-111943 | MEDIUM4.08 | stdlib v1.26.8 fixed in 1.26.10, 1.27.3 | 0.3% Theoretical Threat | Directly Exposed |
| SUSE-SU-2026:4847-1 | MEDIUM4 | ca-certificates-mozilla 2.84-150200.44.1 fixed in 2.92-150200.50.2 | — | Directly Exposed |
| GO-2026-5932 | MEDIUM4 | golang.org/x/crypto v0.56.0 No fix yet | — | Directly Exposed |
| CVE-2026-56866 | LOW3.9 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-94439 | LOW3.9 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-94448 | LOW3.66 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97030 | LOW3.66 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56857 | LOW3.3 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| SUSE-SU-2026:4619-1 | LOW3.24 | libexpat1 2.7.1-150700.3.12.1 fixed in 2.8.5-150700.3.15.1 | — | Post-Exploit |
| SUSE-SU-2026:4819-1 | LOW2.7 | cifs-utils 6.15-150400.3.24.1 fixed in 6.15-150400.3.27.1 | — | Post-Exploit |
| SUSE-SU-2026:4656-1 | LOW2.7 | glibc 2.38-150600.14.58.1 fixed in 2.38-150600.14.61.1 | — | Post-Exploit |
| SUSE-SU-2026:4414-1 | LOW2.7 | libopenssl-3-fips-provider 3.5.0-150700.5.50.1 fixed in 3.5.0-150700.5.53.2 | — | Post-Exploit |
| SUSE-SU-2026:4414-1 | LOW2.7 | libopenssl3 3.5.0-150700.5.50.1 fixed in 3.5.0-150700.5.53.2 | — | Post-Exploit |
| SUSE-SU-2026:4754-1 | LOW2.7 | libpython3_6m1_0 3.6.15-150300.10.118.1 fixed in 3.6.15-150300.10.129.1 | — | Post-Exploit |
| SUSE-SU-2026:4836-1 | LOW2.7 | libsasl2-3 2.1.28-150600.7.14.1 fixed in 2.1.28-150600.7.17.1 | — | Post-Exploit |
| SUSE-SU-2026:4414-1 | LOW2.7 | openssl-3 3.5.0-150700.5.50.1 fixed in 3.5.0-150700.5.53.2 | — | Post-Exploit |
| SUSE-SU-2026:4754-1 | LOW2.7 | python3-base 3.6.15-150300.10.118.1 fixed in 3.6.15-150300.10.129.1 | — | Post-Exploit |
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.