Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker with pod creation permissions could exploit CVE-2026-50195 to execute arbitrary code via a malicious checkpoint image, or use CVE-2026-53492 to bypass security controls via CDI device injection. Disabling CRI checkpoint import and CDI, if not needed, fully eliminates these vulnerabilities. Note that these vulnerabilities require non-default features (CRI checkpoint and CDI) to be enabled.
Hardening plan for this image · 3 steps
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-50195 | MEDIUM6.74 | github.com/containerd/containerd/v2 v2.3.1-k3s2 fixed in 2.1.9, 2.2.5, 2.3.2 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53492 | MEDIUM6.53 | github.com/containerd/containerd/v2 v2.3.1-k3s2 fixed in 2.1.9, 2.2.5, 2.3.2 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42508 | MEDIUM6.29 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42306 | MEDIUM6.12 | github.com/docker/docker v25.0.15-0.20260325154711-d2dbc0547253+incompatible No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46595 | MEDIUM6.03 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53488 | MEDIUM5.98 | github.com/containerd/containerd/v2 v2.3.1-k3s2 fixed in 2.0.10, 2.1.9, 2.2.5, 2.3.2 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53489 | MEDIUM5.52 | github.com/containerd/containerd/v2 v2.3.1-k3s2 fixed in 2.1.9, 2.2.5, 2.3.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25680 | MEDIUM5.52 | golang.org/x/net v0.52.0 fixed in 0.55.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39827 | MEDIUM5.52 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39834 | MEDIUM5.52 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25680 | MEDIUM5.52 | golang.org/x/net v0.43.0 fixed in 0.55.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46680 | MEDIUM5.3 | github.com/containerd/containerd/v2 v2.3.1-k3s2 fixed in 2.0.9, 2.2.4, 2.3.1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42502 | MEDIUM5.18 | golang.org/x/net v0.52.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42502 | MEDIUM5.18 | golang.org/x/net v0.43.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-47262 | MEDIUM4.67 | github.com/containerd/containerd/v2 v2.3.1-k3s2 fixed in 2.0.10, 2.1.9, 2.2.5, 2.3.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39833 | MEDIUM4.67 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42506 | MEDIUM4.59 | golang.org/x/net v0.52.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42506 | MEDIUM4.59 | golang.org/x/net v0.43.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42505 | MEDIUM4.5 | stdlib v1.26.4 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46598 | MEDIUM4.5 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-47911 | MEDIUM4.5 | golang.org/x/net v0.43.0 fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58190 | MEDIUM4.5 | golang.org/x/net v0.43.0 fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-41568 | LOW3.31 | github.com/docker/docker v25.0.15-0.20260325154711-d2dbc0547253+incompatible No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34040 | LOW3.23 | github.com/docker/docker v25.0.15-0.20260325154711-d2dbc0547253+incompatible fixed in 29.3.1 | 10.1% High Exploitation Risk | Post-Exploit |
| CVE-2026-41579 | LOW3.06 | github.com/opencontainers/runc v1.4.2 fixed in 1.3.6, 1.4.3, 1.5.0-rc.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39828 | LOW2.69 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-39832 | LOW2.66 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-39821 | LOW2.51 | golang.org/x/net v0.52.0 fixed in 0.55.0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-39821 | LOW2.51 | golang.org/x/net v0.43.0 fixed in 0.55.0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-25681 | LOW2.48 | golang.org/x/net v0.52.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27136 | LOW2.48 | golang.org/x/net v0.52.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-33997 | LOW2.48 | github.com/docker/docker v25.0.15-0.20260325154711-d2dbc0547253+incompatible fixed in 29.3.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-39831 | LOW2.48 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-25681 | LOW2.48 | golang.org/x/net v0.43.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27136 | LOW2.48 | golang.org/x/net v0.43.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-39822 | LOW2.39 | stdlib v1.26.4 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-33814 | LOW2.29 | golang.org/x/net v0.52.0 fixed in 0.53.0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-41567 | LOW2.29 | github.com/docker/docker v25.0.15-0.20260325154711-d2dbc0547253+incompatible No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-40898 | LOW2.29 | github.com/quic-go/quic-go v0.59.0 fixed in 0.59.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-39829 | LOW2.29 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-39830 | LOW2.29 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-39835 | LOW2.29 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46597 | LOW2.29 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-33814 | LOW2.29 | golang.org/x/net v0.43.0 fixed in 0.53.0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-46600 | NONE0 | golang.org/x/net v0.52.0 fixed in 0.56.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39824 | NONE0 | golang.org/x/sys v0.43.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56852 | NONE0 | golang.org/x/text v0.35.0 fixed in 0.39.0 | 0.4% Theoretical Threat | Not Applicable |
| GHSA-hrxh-6v49-42gf | NONE0 | google.golang.org/grpc v1.80.0 fixed in 1.82.1 | — | Not Applicable |
| GHSA-gcjh-h69q-9w9g | NONE0 | github.com/google/cel-go v0.26.1 fixed in 0.29.0 | — | Not Applicable |
| CVE-2026-57497 | NONE0 | github.com/quic-go/webtransport-go v0.10.0 fixed in 0.11.1 | — | Not Applicable |
| GO-2026-5932 | NONE0 | golang.org/x/crypto v0.47.0 No fix yet | — | Not Applicable |
| CVE-2026-46600 | NONE0 | golang.org/x/net v0.55.0 fixed in 0.56.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39824 | NONE0 | golang.org/x/sys v0.40.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56852 | NONE0 | golang.org/x/text v0.37.0 fixed in 0.39.0 | 0.4% Theoretical Threat | Not Applicable |
| GHSA-hrxh-6v49-42gf | NONE0 | google.golang.org/grpc v1.79.3 fixed in 1.82.1 | — | Not Applicable |
| CVE-2026-46600 | NONE0 | golang.org/x/net v0.43.0 fixed in 0.56.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39824 | NONE0 | golang.org/x/sys v0.38.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.