Last scanned:
This image is safe for production use. It does have 24 exposed vulnerabilities and 13 post-exploit-only findings, but the maximum exposed severity is 5.1 and no exposed or post-exploit findings reach severity 6.0 or higher. The provided top findings lists are empty, so no specific CVE IDs are available to assess further. The image also has strong trust signals, including a reliable publisher and digest pinning. No additional compensating controls are required by the supplied data.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-78667 | MEDIUM5.1 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78669 | LOW3.83 | golang.org/x/net v0.58.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78669 | LOW3.83 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-97031 | LOW3.83 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-35206 | LOW3.74 | helm.sh/helm/v3 v3.18.5 fixed in 3.20.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94448 | LOW3.11 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-97032 | LOW3.01 | golang.org/x/net v0.58.0 fixed in 0.60.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-97032 | LOW3.01 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-81870 | LOW2.8 | go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.43.0 fixed in 1.45.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-81870 | LOW2.8 | go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp v1.43.0 fixed in 1.45.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56857 | LOW2.8 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-32952 | LOW2.7 | github.com/Azure/go-ntlmssp v0.1.0 fixed in 0.1.1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-84784 | LOW2.7 | openssl 3.5.8-1.1.ph5 fixed in 3.5.9-0.1.ph5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-78663 | LOW2.7 | golang.org/x/net v0.58.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | LOW2.7 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33540 | LOW2.63 | github.com/distribution/distribution v2.8.2+incompatible No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-35172 | LOW2.29 | github.com/distribution/distribution v2.8.2+incompatible No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-63209 | LOW2.29 | github.com/klauspost/compress v1.18.4 fixed in 1.18.7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41888 | LOW1.99 | github.com/distribution/distribution v2.8.2+incompatible No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-56866 | LOW1.99 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-94439 | LOW1.99 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-72897 | LOW1.81 | openssl 3.5.8-1.1.ph5 fixed in 3.5.9-0.1.ph5 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-72897 | LOW1.81 | openssl-libs 3.5.8-1.1.ph5 fixed in 3.5.9-0.1.ph5 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-84784 | LOW1.62 | openssl-libs 3.5.8-1.1.ph5 fixed in 3.5.9-0.1.ph5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-56855 | LOW1.62 | golang.org/x/crypto v0.55.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-78662 | LOW1.62 | golang.org/x/crypto v0.55.0 fixed in 0.56.0 | 0.4% Theoretical Threat | Post-Exploit |
| BDSA-2026-35496 | NONE0 | openssl 3.5.8-1.1.ph5 fixed in 3.5.9-0.1.ph5 | — | Not Applicable |
| BDSA-2026-35496 | NONE0 | openssl-libs 3.5.8-1.1.ph5 fixed in 3.5.9-0.1.ph5 | — | Not Applicable |
| CVE-2025-24358 | NONE0 | github.com/gorilla/csrf v1.7.2 fixed in 1.7.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-47909 | NONE0 | github.com/gorilla/csrf v1.7.2 No fix yet | 0.2% 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.26.7 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.26.7 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.