Last scanned:
··This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker who can supply crafted OCI artifacts to the agent could overwrite files as root and possibly execute code, and crafted HTTP/2 traffic could tamper with responses the agent handles. Note: CVE-2026-85731 only applies when the agent is set up to unpack attacker-controlled artifacts with the unpack label. Not pulling untrusted artifacts with that label fully removes the CVE-2026-85731 path. The scan found 190 exposed findings, none known to be actively exploited, and the agent is a statically linked Go binary, which limits exposure to OS library flaws.
Hardening plan for this image · 4 steps
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-78660 | HIGH7.5 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-94440 | HIGH7.5 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-61726 | HIGH7.5 | stdlib v1.24.9 fixed in 1.24.12, 1.25.6 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-61729 | HIGH7.5 | stdlib v1.24.9 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61728 | HIGH7.5 | stdlib v1.24.9 fixed in 1.24.12, 1.25.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-78660 | HIGH7.5 | stdlib v1.24.9 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-94440 | HIGH7.5 | stdlib v1.24.9 fixed in 1.26.9, 1.27.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-85731 | HIGH7.04 | oras.land/oras-go/v2 v2.6.0 fixed in 2.6.2 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-44503 | HIGH7 | github.com/microsoft/kiota-http-go v1.4.4 fixed in 1.5.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-24051 | HIGH7 | go.opentelemetry.io/otel/sdk v1.38.0 fixed in 1.40.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39883 | HIGH7 | go.opentelemetry.io/otel/sdk v1.38.0 fixed in 1.43.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85747 | MEDIUM6.8 | github.com/docker/distribution v2.8.2+incompatible No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-111943 | MEDIUM6.8 | stdlib v1.24.13 fixed in 1.26.10, 1.27.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-111943 | MEDIUM6.8 | stdlib v1.24.9 fixed in 1.26.10, 1.27.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-35469 | MEDIUM6.5 | github.com/moby/spdystream v0.5.0 fixed in 0.5.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-39825 | MEDIUM6.5 | stdlib v1.24.13 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56866 | MEDIUM6.5 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-94439 | MEDIUM6.5 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61727 | MEDIUM6.5 | stdlib v1.24.9 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39825 | MEDIUM6.5 | stdlib v1.24.9 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56866 | MEDIUM6.5 | stdlib v1.24.9 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-94439 | MEDIUM6.5 | stdlib v1.24.9 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-32282 | MEDIUM6.4 | stdlib v1.24.13 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32282 | MEDIUM6.4 | stdlib v1.24.9 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| GHSA-gcjh-h69q-9w9g | MEDIUM6.3 | github.com/google/cel-go v0.26.0 fixed in 0.29.0 | — | Directly Exposed |
| CVE-2026-32289 | MEDIUM6.1 | stdlib v1.24.13 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-94448 | MEDIUM6.1 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97030 | MEDIUM6.1 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32289 | MEDIUM6.1 | stdlib v1.24.9 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-94448 | MEDIUM6.1 | stdlib v1.24.9 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97030 | MEDIUM6.1 | stdlib v1.24.9 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68121 | MEDIUM6 | stdlib v1.24.9 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-29181 | MEDIUM6 | go.opentelemetry.io/otel v1.38.0 fixed in 1.41.0 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-50151 | MEDIUM6 | oras.land/oras-go/v2 v2.6.0 fixed in 2.6.1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-25679 | MEDIUM6 | stdlib v1.24.13 fixed in 1.25.8, 1.26.1 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-27145 | MEDIUM6 | stdlib v1.24.13 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-32280 | MEDIUM6 | stdlib v1.24.13 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-32283 | MEDIUM6 | stdlib v1.24.13 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33811 | MEDIUM6 | stdlib v1.24.13 fixed in 1.25.10, 1.26.3 | 0.9% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33814 | MEDIUM6 | stdlib v1.24.13 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33818 | MEDIUM6 | stdlib v1.24.13 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78669 | MEDIUM6 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-25679 | MEDIUM6 | stdlib v1.24.9 fixed in 1.25.8, 1.26.1 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-27145 | MEDIUM6 | stdlib v1.24.9 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-32280 | MEDIUM6 | stdlib v1.24.9 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-32283 | MEDIUM6 | stdlib v1.24.9 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33811 | MEDIUM6 | stdlib v1.24.9 fixed in 1.25.10, 1.26.3 | 0.9% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33814 | MEDIUM6 | stdlib v1.24.9 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33818 | MEDIUM6 | stdlib v1.24.9 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78669 | MEDIUM6 | stdlib v1.24.9 fixed in 1.26.9, 1.27.2 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97032 | MEDIUM5.9 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-97032 | MEDIUM5.9 | stdlib v1.24.9 fixed in 1.26.9, 1.27.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-44939 | MEDIUM5.82 | github.com/rancher/rancher v2.13.3 fixed in 2.14.2, 2.13.6, 2.12.10, 2.11.14, 2.10.12, 0.0.0-20260617231817-2aa77eb283e7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-50163 | MEDIUM5.68 | oras.land/oras-go/v2 v2.6.0 fixed in 2.6.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| GHSA-vh4v-2xq2-g5cg | MEDIUM5.52 | oras.land/oras-go/v2 v2.6.0 fixed in 2.6.1 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-32288 | MEDIUM5.5 | stdlib v1.24.13 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32288 | MEDIUM5.5 | stdlib v1.24.9 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-33186 | MEDIUM5.46 | google.golang.org/grpc v1.78.0 fixed in 1.79.3 | 1.6% Low-Moderate Risk | Directly Exposed |
| SUSE-SU-2026:4619-1 | MEDIUM5.4 | libexpat1 2.7.1-150700.3.9.2 fixed in 2.8.5-150700.3.15.1 | — | Directly Exposed |
| CVE-2026-27142 | MEDIUM5.4 | stdlib v1.24.13 fixed in 1.25.8, 1.26.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39823 | MEDIUM5.4 | stdlib v1.24.13 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39826 | MEDIUM5.4 | stdlib v1.24.13 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27142 | MEDIUM5.4 | stdlib v1.24.9 fixed in 1.25.8, 1.26.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39823 | MEDIUM5.4 | stdlib v1.24.9 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39826 | MEDIUM5.4 | stdlib v1.24.9 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42505 | MEDIUM5.3 | stdlib v1.24.13 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42507 | MEDIUM5.3 | stdlib v1.24.13 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | MEDIUM5.3 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-61730 | MEDIUM5.3 | stdlib v1.24.9 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42505 | MEDIUM5.3 | stdlib v1.24.9 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42507 | MEDIUM5.3 | stdlib v1.24.9 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | MEDIUM5.3 | stdlib v1.24.9 fixed in 1.26.9, 1.27.2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-53488 | MEDIUM5.28 | github.com/containerd/containerd v1.7.28 fixed in 1.7.33 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41052 | MEDIUM5.28 | github.com/rancher/rancher v2.13.3 fixed in 2.14.2, 2.13.6, 2.12.10, 0.0.0-20260513182521-2800aaac25b5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41053 | MEDIUM5.28 | github.com/rancher/rancher v2.13.3 fixed in 2.14.2, 2.13.6, 0.0.0-20260519172014-d0c047bbc6d2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-39828 | MEDIUM5.28 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.4% Theoretical Threat | Directly Exposed |
| GHSA-hrxh-6v49-42gf | MEDIUM5.28 | google.golang.org/grpc v1.78.0 fixed in 1.82.1 | — | Directly Exposed |
| CVE-2026-39832 | MEDIUM5.22 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-25705 | MEDIUM5.1 | github.com/rancher/rancher v2.13.3 fixed in 2.14.1, 2.13.5, 2.12.9, 2.11.13 | 0.4% Theoretical Threat | Directly Exposed |
| SUSE-SU-2026:3030-1 | MEDIUM5 | glibc 2.38-150600.14.40.1 fixed in 2.38-150600.14.52.1 | — | Directly Exposed |
| SUSE-SU-2026:4250-1 | MEDIUM5 | glibc 2.38-150600.14.40.1 fixed in 2.38-150600.14.58.1 | — | Directly Exposed |
| SUSE-SU-2026:4055-1 | MEDIUM5 | libbz2-1 1.0.8-150400.1.122 fixed in 1.0.8-150400.3.4.1 | — | Directly Exposed |
| SUSE-SU-2026:0779-1 | MEDIUM5 | libssh-config 0.9.8-150600.11.6.1 fixed in 0.9.8-150600.11.9.1 | — | Directly Exposed |
| SUSE-SU-2026:1310-1 | MEDIUM5 | libssh-config 0.9.8-150600.11.6.1 fixed in 0.9.8-150600.11.12.1 | — | Directly Exposed |
| SUSE-SU-2026:3330-1 | MEDIUM5 | libssh-config 0.9.8-150600.11.6.1 fixed in 0.9.8-150600.11.15.1 | — | Directly Exposed |
| SUSE-SU-2026:0779-1 | MEDIUM5 | libssh4 0.9.8-150600.11.6.1 fixed in 0.9.8-150600.11.9.1 | — | Directly Exposed |
| SUSE-SU-2026:1310-1 | MEDIUM5 | libssh4 0.9.8-150600.11.6.1 fixed in 0.9.8-150600.11.12.1 | — | Directly Exposed |
| SUSE-SU-2026:3330-1 | MEDIUM5 | libssh4 0.9.8-150600.11.6.1 fixed in 0.9.8-150600.11.15.1 | — | Directly Exposed |
| SUSE-SU-2026:0783-1 | MEDIUM5 | libz1 1.2.13-150500.4.3.1 fixed in 1.2.13-150500.4.6.1 | — | Directly Exposed |
| CVE-2026-39821 | MEDIUM4.92 | golang.org/x/net v0.49.0 fixed in 0.55.0 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-39821 | MEDIUM4.92 | golang.org/x/net v0.38.0 fixed in 0.55.0 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33997 | MEDIUM4.86 | github.com/docker/docker v25.0.8+incompatible fixed in 29.3.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39831 | MEDIUM4.86 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25681 | MEDIUM4.86 | golang.org/x/net v0.49.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27136 | MEDIUM4.86 | golang.org/x/net v0.49.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25681 | MEDIUM4.86 | golang.org/x/net v0.38.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27136 | MEDIUM4.86 | golang.org/x/net v0.38.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46680 | MEDIUM4.68 | github.com/containerd/containerd v1.7.28 fixed in 1.7.32 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39822 | MEDIUM4.68 | stdlib v1.24.13 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39822 | MEDIUM4.68 | stdlib v1.24.9 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Directly Exposed |
| SUSE-SU-2026:1369-1 | MEDIUM4.5 | glibc 2.38-150600.14.40.1 fixed in 2.38-150600.14.46.1 | — | Directly Exposed |
| SUSE-SU-2026:4176-1 | MEDIUM4.5 | libacl1 2.2.52-4.3.1 fixed in 2.4.0-150000.4.6.1 | — | Directly Exposed |
| SUSE-SU-2026:4176-1 | MEDIUM4.5 | libattr1 2.4.47-2.19 fixed in 2.6.0-150000.4.3.1 | — | Directly Exposed |
| SUSE-SU-2026:1432-1 | MEDIUM4.5 | libcap2 2.63-150400.3.3.1 fixed in 2.63-150400.3.6.1 | — | Directly Exposed |
| SUSE-SU-2026:1352-1 | MEDIUM4.5 | libexpat1 2.7.1-150700.3.9.2 fixed in 2.7.1-150700.3.12.1 | — | Directly Exposed |
| SUSE-SU-2026:4275-1 | MEDIUM4.5 | libjq1 1.6-150000.3.9.1 fixed in 1.7.1-150000.3.25.1 | — | Directly Exposed |
| SUSE-SU-2026:2051-1 | MEDIUM4.5 | liblzma5 5.4.1-150600.3.3.1 fixed in 5.4.1-150600.3.6.1 | — | Directly Exposed |
| SUSE-SU-2026:1074-1 | MEDIUM4.5 | libnghttp2-14 1.64.0-150700.1.5 fixed in 1.64.0-150700.3.3.1 | — | Directly Exposed |
| SUSE-SU-2026:1375-1 | MEDIUM4.5 | libopenssl3 3.2.3-150700.5.24.1 fixed in 3.2.3-150700.5.31.1 | — | Directly Exposed |
| SUSE-SU-2026:3097-1 | MEDIUM4.5 | libxml2-2 2.12.10-150700.4.11.1 fixed in 2.12.10-150700.4.14.1 | — | Directly Exposed |
| CVE-2026-32952 | MEDIUM4.5 | github.com/Azure/go-ntlmssp v0.0.0-20200615164410-66371956d46c fixed in 0.1.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34986 | MEDIUM4.5 | github.com/go-jose/go-jose/v3 v3.0.4 fixed in 3.0.5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63209 | MEDIUM4.5 | github.com/klauspost/compress v1.18.0 fixed in 1.18.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33487 | MEDIUM4.5 | github.com/russellhaering/goxmldsig v1.4.0 fixed in 1.6.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39829 | MEDIUM4.5 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-39830 | MEDIUM4.5 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-39835 | MEDIUM4.5 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46597 | MEDIUM4.5 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM4.5 | golang.org/x/net v0.49.0 fixed in 0.53.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-46600 | MEDIUM4.5 | golang.org/x/net v0.49.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78669 | MEDIUM4.5 | golang.org/x/net v0.49.0 fixed in 0.60.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-78659 | MEDIUM4.5 | golang.org/x/net v0.49.0 fixed in 0.60.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-78660 | MEDIUM4.5 | golang.org/x/net v0.49.0 fixed in 0.60.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56851 | MEDIUM4.5 | golang.org/x/text v0.33.0 fixed in 0.41.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56852 | MEDIUM4.5 | golang.org/x/text v0.33.0 fixed in 0.39.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-84304 | MEDIUM4.5 | google.golang.org/grpc v1.78.0 fixed in 1.83.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-84445 | MEDIUM4.5 | google.golang.org/grpc v1.78.0 fixed in 1.82.2, 1.83.2, 1.84.0-dev.0.20260825144003-d5a41119e0e3, 1.85.0-dev.0.20260825072537-93e31b48545e | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM4.5 | golang.org/x/net v0.38.0 fixed in 0.53.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-46600 | MEDIUM4.5 | golang.org/x/net v0.38.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78669 | MEDIUM4.5 | golang.org/x/net v0.38.0 fixed in 0.60.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-78659 | MEDIUM4.5 | golang.org/x/net v0.38.0 fixed in 0.60.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-78660 | MEDIUM4.5 | golang.org/x/net v0.38.0 fixed in 0.60.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56851 | MEDIUM4.5 | golang.org/x/text v0.23.0 fixed in 0.41.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56852 | MEDIUM4.5 | golang.org/x/text v0.23.0 fixed in 0.39.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42508 | MEDIUM4.44 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 6.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-41567 | MEDIUM4.32 | github.com/docker/docker v25.0.8+incompatible No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42306 | MEDIUM4.32 | github.com/docker/docker v25.0.8+incompatible No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46595 | MEDIUM4.26 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-50162 | MEDIUM4.24 | oras.land/oras-go/v2 v2.6.0 fixed in 2.6.1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56854 | MEDIUM4.08 | golang.org/x/crypto v0.47.0 fixed in 0.55.0 | 0.4% Theoretical Threat | Directly Exposed |
| SUSE-SU-2026:4847-1 | MEDIUM4 | ca-certificates-mozilla-prebuilt 2.74-150200.41.2 fixed in 2.92-150200.50.3 | — | Directly Exposed |
| SUSE-SU-2026:3444-1 | MEDIUM4 | libopenssl3 3.2.3-150700.5.24.1 fixed in 3.2.3-150700.5.40.1 | — | Directly Exposed |
| CVE-2026-39824 | MEDIUM4 | golang.org/x/sys v0.40.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-39824 | MEDIUM4 | golang.org/x/sys v0.31.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-25621 | LOW3.98 | github.com/containerd/containerd v1.7.28 fixed in 1.7.29 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39827 | LOW3.9 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39834 | LOW3.9 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-25680 | LOW3.9 | golang.org/x/net v0.49.0 fixed in 0.55.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25680 | LOW3.9 | golang.org/x/net v0.38.0 fixed in 0.55.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-84303 | LOW3.78 | google.golang.org/grpc v1.78.0 fixed in 1.83.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85732 | LOW3.76 | oras.land/oras-go/v2 v2.6.0 fixed in 2.6.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42502 | LOW3.66 | golang.org/x/net v0.49.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42502 | LOW3.66 | golang.org/x/net v0.38.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41568 | LOW3.6 | github.com/docker/docker v25.0.8+incompatible No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-97032 | LOW3.54 | golang.org/x/net v0.49.0 fixed in 0.60.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-97032 | LOW3.54 | golang.org/x/net v0.38.0 fixed in 0.60.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-47262 | LOW3.3 | github.com/containerd/containerd v1.7.28 fixed in 1.7.33 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53495 | LOW3.3 | github.com/containerd/containerd v1.7.28 fixed in 1.7.35 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39833 | LOW3.3 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-81870 | LOW3.3 | go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.34.0 fixed in 1.45.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-81870 | LOW3.3 | go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.34.0 fixed in 1.45.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-81870 | LOW3.3 | go.opentelemetry.io/otel/sdk v1.38.0 fixed in 1.45.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56857 | LOW3.3 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56857 | LOW3.3 | stdlib v1.24.9 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42506 | LOW3.24 | golang.org/x/net v0.49.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42506 | LOW3.24 | golang.org/x/net v0.38.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53493 | LOW3.18 | github.com/containerd/containerd v1.7.28 fixed in 1.7.36 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46598 | LOW3.18 | golang.org/x/crypto v0.47.0 fixed in 0.52.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56855 | LOW3.18 | golang.org/x/crypto v0.47.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78662 | LOW3.18 | golang.org/x/crypto v0.47.0 fixed in 0.56.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | LOW3.18 | golang.org/x/net v0.49.0 fixed in 0.60.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-47911 | LOW3.18 | golang.org/x/net v0.38.0 fixed in 0.45.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-58190 | LOW3.18 | golang.org/x/net v0.38.0 fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | LOW3.18 | golang.org/x/net v0.38.0 fixed in 0.60.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-56865 | LOW3.17 | golang.org/x/mod v0.32.0 fixed in 0.40.0 | 0.1% Theoretical Threat | Post-Exploit |
| SUSE-SU-2026:2283-1 | LOW3 | jq 1.6-150000.3.9.1 fixed in 1.6-150000.3.15.1 | — | Directly Exposed |
| SUSE-SU-2026:2983-1 | LOW3 | jq 1.6-150000.3.9.1 fixed in 1.6-150000.3.20.1 | — | Directly Exposed |
| SUSE-SU-2026:3798-1 | LOW3 | libcurl4 8.14.1-150700.7.11.1 fixed in 8.14.1-150700.7.23.1 | — | Directly Exposed |
| SUSE-SU-2026:4048-1 | LOW3 | libcurl4 8.14.1-150700.7.11.1 fixed in 8.14.1-150700.7.26.1 | — | Directly Exposed |
| SUSE-SU-2026:2283-1 | LOW3 | libjq1 1.6-150000.3.9.1 fixed in 1.6-150000.3.15.1 | — | Directly Exposed |
| SUSE-SU-2026:2983-1 | LOW3 | libjq1 1.6-150000.3.9.1 fixed in 1.6-150000.3.20.1 | — | Directly Exposed |
| SUSE-SU-2026:1510-1 | LOW3 | libncurses6 6.1-150000.5.30.1 fixed in 6.1-150000.5.33.1 | — | Post-Exploit |
| SUSE-SU-2026:4029-1 | LOW3 | libnghttp2-14 1.64.0-150700.1.5 fixed in 1.64.0-150700.3.6.1 | — | Directly Exposed |
| SUSE-SU-2026:1941-1 | LOW3 | sed 4.9-150600.1.4 fixed in 4.9-150600.3.3.1 | — | Post-Exploit |
| CVE-2026-39821 | LOW2.95 | stdlib v1.24.13 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-39821 | LOW2.95 | stdlib v1.24.9 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-56864 | LOW2.92 | golang.org/x/mod v0.32.0 fixed in 0.40.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-56858 | LOW2.92 | stdlib v1.24.13 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-56858 | LOW2.92 | stdlib v1.24.9 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-64329 | LOW2.8 | github.com/containerd/containerd v1.7.28 fixed in 1.7.29 | 0.2% Theoretical Threat | Directly Exposed |
| SUSE-SU-2026:4176-1 | LOW2.7 | acl 2.2.52-4.3.1 fixed in 2.4.0-150000.4.6.1 | — | Post-Exploit |
| SUSE-SU-2026:1351-1 | LOW2.7 | bind-utils 9.20.18-150700.3.15.1 fixed in 9.20.21-150700.3.18.1 | — | Post-Exploit |
| SUSE-SU-2026:2673-1 | LOW2.7 | bind-utils 9.20.18-150700.3.15.1 fixed in 9.20.23-150700.3.25.1 | — | Post-Exploit |
| SUSE-SU-2026:3426-1 | LOW2.7 | bind-utils 9.20.18-150700.3.15.1 fixed in 9.20.26-150700.3.29.1 | — | Post-Exploit |
| SUSE-SU-2026:4285-1 | LOW2.7 | bind-utils 9.20.18-150700.3.15.1 fixed in 9.20.29-150700.3.32.2 | — | Post-Exploit |
| SUSE-SU-2026:2231-1 | LOW2.7 | glibc 2.38-150600.14.40.1 fixed in 2.38-150600.14.49.1 | — | Post-Exploit |
| SUSE-SU-2026:4656-1 | LOW2.7 | glibc 2.38-150600.14.40.1 fixed in 2.38-150600.14.61.1 | — | Post-Exploit |
| SUSE-SU-2026:4275-1 | LOW2.7 | jq 1.6-150000.3.9.1 fixed in 1.7.1-150000.3.25.1 | — | Post-Exploit |
| SUSE-SU-2026:2848-1 | LOW2.7 | krb5 1.20.1-150600.11.14.1 fixed in 1.20.1-150600.11.19.1 | — | Post-Exploit |
| SUSE-SU-2026:0903-1 | LOW2.7 | libcurl4 8.14.1-150700.7.11.1 fixed in 8.14.1-150700.7.14.1 | — | Post-Exploit |
| SUSE-SU-2026:2925-1 | LOW2.7 | libcurl4 8.14.1-150700.7.11.1 fixed in 8.14.1-150700.7.20.1 | — | Post-Exploit |
| SUSE-SU-2026:2648-1 | LOW2.7 | libopenssl3 3.2.3-150700.5.24.1 fixed in 3.2.3-150700.5.36.1 | — | Post-Exploit |
| SUSE-SU-2026:3835-1 | LOW2.7 | libopenssl3 3.2.3-150700.5.24.1 fixed in 3.5.0-150700.5.45.2 | — | Post-Exploit |
| SUSE-SU-2026:4039-1 | LOW2.7 | libopenssl3 3.2.3-150700.5.24.1 fixed in 3.5.0-150700.5.50.1 | — | Post-Exploit |
| SUSE-SU-2026:4414-1 | LOW2.7 | libopenssl3 3.2.3-150700.5.24.1 fixed in 3.5.0-150700.5.53.2 | — | Post-Exploit |
| SUSE-SU-2026:4241-1 | LOW2.7 | libpcre2-8-0 10.42-150600.1.26 fixed in 10.42-150600.3.3.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:2051-1 | LOW2.7 | xz 5.4.1-150600.3.3.1 fixed in 5.4.1-150600.3.6.1 | — | Post-Exploit |
| CVE-2026-32281 | LOW2.7 | stdlib v1.24.13 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-39820 | LOW2.7 | stdlib v1.24.13 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-39836 | LOW2.7 | stdlib v1.24.13 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42499 | LOW2.7 | stdlib v1.24.13 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-42504 | LOW2.7 | stdlib v1.24.13 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-56853 | LOW2.7 | stdlib v1.24.13 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-56859 | LOW2.7 | stdlib v1.24.13 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-56860 | LOW2.7 | stdlib v1.24.13 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-56862 | LOW2.7 | stdlib v1.24.13 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-78667 | LOW2.7 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-97031 | LOW2.7 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-78659 | LOW2.7 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-32281 | LOW2.7 | stdlib v1.24.9 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-39820 | LOW2.7 | stdlib v1.24.9 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-39836 | LOW2.7 | stdlib v1.24.9 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42499 | LOW2.7 | stdlib v1.24.9 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-42504 | LOW2.7 | stdlib v1.24.9 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-56853 | LOW2.7 | stdlib v1.24.9 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-56859 | LOW2.7 | stdlib v1.24.9 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-56860 | LOW2.7 | stdlib v1.24.9 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-56862 | LOW2.7 | stdlib v1.24.9 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-78667 | LOW2.7 | stdlib v1.24.9 fixed in 1.26.9, 1.27.2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-97031 | LOW2.7 | stdlib v1.24.9 fixed in 1.26.9, 1.27.2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-78659 | LOW2.7 | stdlib v1.24.9 fixed in 1.26.9, 1.27.2 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-54410 | LOW2.65 | github.com/docker/docker v25.0.8+incompatible fixed in 25.0.13, 28.0.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27139 | LOW2.5 | stdlib v1.24.13 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27139 | LOW2.5 | stdlib v1.24.9 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48978 | LOW2.48 | oras.land/oras-go/v2 v2.6.0 fixed in 2.6.1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| GO-2026-5932 | LOW2.4 | golang.org/x/crypto v0.47.0 No fix yet | — | Directly Exposed |
| CVE-2026-95838 | LOW1.98 | github.com/containerd/containerd v1.7.28 fixed in 1.7.35 | 0.2% Theoretical Threat | Directly Exposed |
| SUSE-SU-2026:1418-1 | LOW1.5 | iproute2 6.4-150600.7.9.1 fixed in 6.4-150600.7.12.1 | — | Post-Exploit |
| SUSE-SU-2026:0931-1 | LOW1.5 | jq 1.6-150000.3.9.1 fixed in 1.6-150000.3.12.1 | — | Directly Exposed |
| SUSE-SU-2026:0931-1 | LOW1.5 | libjq1 1.6-150000.3.9.1 fixed in 1.6-150000.3.12.1 | — | Directly Exposed |
| SUSE-SU-2026:1510-1 | NONE0 | terminfo-base 6.1-150000.5.30.1 fixed in 6.1-150000.5.33.1 | — | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.