Last scanned:
This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker could exploit CVE-2026-33186 to bypass gRPC authorization and gain unauthorized access to sensitive cluster operations, or use CVE-2025-61726 to cause denial of service. Upgrading gRPC-Go to v1.79.3 and Go stdlib to newer versions would eliminate the top vulnerabilities. Note: CVE-2026-32241 only applies if the Flannel Extension backend is enabled, which is not the default in k3s.
Hardening plan for this image · 3 steps
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-33186 | CRITICAL9.1 | google.golang.org/grpc v1.73.0 fixed in 1.79.3 | 1.6% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-33186 | CRITICAL9.1 | google.golang.org/grpc v1.72.1 fixed in 1.79.3 | 1.6% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2025-61726 | HIGH7.5 | stdlib v1.24.6 fixed in 1.24.12, 1.25.6 | 1.9% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-32241 | HIGH7.04 | github.com/flannel-io/flannel v0.27.0 fixed in 0.28.2 | 2.7% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2025-68121 | MEDIUM6.8 | stdlib v1.24.6 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-61729 | MEDIUM6.38 | stdlib v1.24.6 fixed in 1.24.11, 1.25.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25679 | MEDIUM6.38 | stdlib v1.24.6 fixed in 1.25.8, 1.26.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-27145 | MEDIUM6.38 | stdlib v1.24.6 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32280 | MEDIUM6.38 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32281 | MEDIUM6.38 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32283 | MEDIUM6.38 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33811 | MEDIUM6.38 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39820 | MEDIUM6.38 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39836 | MEDIUM6.38 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42499 | MEDIUM6.38 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42504 | MEDIUM6.38 | stdlib v1.24.6 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | golang.org/x/net v0.38.0 fixed in 0.53.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-32285 | MEDIUM6.38 | github.com/buger/jsonparser v1.1.1 fixed in 1.1.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-41567 | MEDIUM6.38 | github.com/docker/docker v25.0.8+incompatible No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68156 | MEDIUM6.38 | github.com/expr-lang/expr v1.17.5 fixed in 1.17.7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34986 | MEDIUM6.38 | github.com/go-jose/go-jose/v4 v4.0.5 fixed in 4.1.4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-27889 | MEDIUM6.38 | github.com/nats-io/nats-server/v2 v2.11.6 fixed in 2.11.14, 2.12.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-29785 | MEDIUM6.38 | github.com/nats-io/nats-server/v2 v2.11.6 fixed in 2.11.14, 2.12.5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-33216 | MEDIUM6.38 | github.com/nats-io/nats-server/v2 v2.11.6 fixed in 2.11.15, 2.12.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33218 | MEDIUM6.38 | github.com/nats-io/nats-server/v2 v2.11.6 fixed in 2.11.15, 2.12.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-27571 | MEDIUM6.38 | github.com/nats-io/nats-server/v2 v2.11.6 fixed in 2.11.12, 2.12.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33219 | MEDIUM6.38 | github.com/nats-io/nats-server/v2 v2.11.6 fixed in 2.11.15, 2.12.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40898 | MEDIUM6.38 | github.com/quic-go/quic-go v0.50.1 fixed in 0.59.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-21434 | MEDIUM6.38 | github.com/quic-go/webtransport-go v0.8.1-0.20241018022711-4ac2c9250e66 fixed in 0.10.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-21435 | MEDIUM6.38 | github.com/quic-go/webtransport-go v0.8.1-0.20241018022711-4ac2c9250e66 fixed in 0.10.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-29181 | MEDIUM6.38 | go.opentelemetry.io/otel v1.37.0 fixed in 1.41.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-39829 | MEDIUM6.38 | golang.org/x/crypto v0.36.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-39830 | MEDIUM6.38 | golang.org/x/crypto v0.36.0 fixed in 0.52.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-39835 | MEDIUM6.38 | golang.org/x/crypto v0.36.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46597 | MEDIUM6.38 | golang.org/x/crypto v0.36.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | golang.org/x/net v0.35.0 fixed in 0.53.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42508 | MEDIUM6.29 | golang.org/x/crypto v0.36.0 fixed in 0.52.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42306 | MEDIUM6.12 | github.com/docker/docker v25.0.8+incompatible No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46595 | MEDIUM6.03 | golang.org/x/crypto v0.36.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-39883 | MEDIUM5.95 | go.opentelemetry.io/otel/sdk v1.37.0 fixed in 1.43.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39821 | MEDIUM5.58 | golang.org/x/net v0.38.0 fixed in 0.55.0 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-39821 | MEDIUM5.58 | golang.org/x/net v0.35.0 fixed in 0.55.0 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-61727 | MEDIUM5.52 | stdlib v1.24.6 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39825 | MEDIUM5.52 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25680 | MEDIUM5.52 | golang.org/x/net v0.38.0 fixed in 0.55.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35469 | MEDIUM5.52 | github.com/moby/spdystream v0.5.0 fixed in 0.5.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-33217 | MEDIUM5.52 | github.com/nats-io/nats-server/v2 v2.11.6 fixed in 2.11.15, 2.12.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-33215 | MEDIUM5.52 | github.com/nats-io/nats-server/v2 v2.11.6 fixed in 2.11.15, 2.12.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39827 | MEDIUM5.52 | golang.org/x/crypto v0.36.0 fixed in 0.52.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39834 | MEDIUM5.52 | golang.org/x/crypto v0.36.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-22872 | MEDIUM5.52 | golang.org/x/net v0.35.0 fixed in 0.38.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25680 | MEDIUM5.52 | golang.org/x/net v0.35.0 fixed in 0.55.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32282 | MEDIUM5.44 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-33249 | MEDIUM5.44 | github.com/nats-io/nats-server/v2 v2.11.6 fixed in 2.11.15, 2.12.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32289 | MEDIUM5.18 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42502 | MEDIUM5.18 | golang.org/x/net v0.38.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42502 | MEDIUM5.18 | golang.org/x/net v0.35.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-58183 | MEDIUM5.1 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-26014 | MEDIUM5.02 | github.com/pion/dtls/v2 v2.2.12 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-26014 | MEDIUM5.02 | github.com/pion/dtls/v3 v3.0.4 fixed in 3.1.1, 3.0.11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32288 | MEDIUM4.67 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39833 | MEDIUM4.67 | golang.org/x/crypto v0.36.0 fixed in 0.52.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27142 | MEDIUM4.59 | stdlib v1.24.6 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39823 | MEDIUM4.59 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39826 | MEDIUM4.59 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42506 | MEDIUM4.59 | golang.org/x/net v0.38.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33223 | MEDIUM4.59 | github.com/nats-io/nats-server/v2 v2.11.6 fixed in 2.11.15, 2.12.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33246 | MEDIUM4.59 | github.com/nats-io/nats-server/v2 v2.11.6 fixed in 2.11.15, 2.12.6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42506 | MEDIUM4.59 | golang.org/x/net v0.35.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-47912 | MEDIUM4.5 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58185 | MEDIUM4.5 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58187 | MEDIUM4.5 | stdlib v1.24.6 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58188 | MEDIUM4.5 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58189 | MEDIUM4.5 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61723 | MEDIUM4.5 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61724 | MEDIUM4.5 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61725 | MEDIUM4.5 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61730 | MEDIUM4.5 | stdlib v1.24.6 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42505 | MEDIUM4.5 | stdlib v1.24.6 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42507 | MEDIUM4.5 | stdlib v1.24.6 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58186 | MEDIUM4.5 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-47911 | MEDIUM4.5 | golang.org/x/net v0.38.0 fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58190 | MEDIUM4.5 | golang.org/x/net v0.38.0 fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33247 | MEDIUM4.5 | github.com/nats-io/nats-server/v2 v2.11.6 fixed in 2.11.15, 2.12.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-59530 | MEDIUM4.5 | github.com/quic-go/quic-go v0.50.1 fixed in 0.49.1, 0.54.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-64702 | MEDIUM4.5 | github.com/quic-go/quic-go v0.50.1 fixed in 0.57.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-47914 | MEDIUM4.5 | golang.org/x/crypto v0.36.0 fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58181 | MEDIUM4.5 | golang.org/x/crypto v0.36.0 fixed in 0.45.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46598 | MEDIUM4.5 | golang.org/x/crypto v0.36.0 fixed in 0.52.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-47911 | MEDIUM4.5 | golang.org/x/net v0.35.0 fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58190 | MEDIUM4.5 | golang.org/x/net v0.35.0 fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-54410 | MEDIUM4.42 | github.com/docker/docker v25.0.8+incompatible fixed in 25.0.13, 28.0.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33222 | MEDIUM4.17 | github.com/nats-io/nats-server/v2 v2.11.6 fixed in 2.11.15, 2.12.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-33248 | MEDIUM4.08 | github.com/nats-io/nats-server/v2 v2.11.6 fixed in 2.11.15, 2.12.6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-31133 | LOW3.98 | github.com/opencontainers/runc v1.3.1 fixed in 1.2.8, 1.3.3, 1.4.0-rc.3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-52565 | LOW3.82 | github.com/opencontainers/runc v1.3.1 fixed in 1.2.8, 1.3.3, 1.4.0-rc.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-52881 | LOW3.82 | github.com/opencontainers/runc v1.3.1 fixed in 1.2.8, 1.3.3, 1.4.0-rc.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-22870 | LOW3.74 | golang.org/x/net v0.35.0 fixed in 0.36.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41568 | LOW3.31 | github.com/docker/docker v25.0.8+incompatible No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34040 | LOW3.23 | github.com/docker/docker v25.0.8+incompatible fixed in 29.3.1 | 10.1% High Exploitation Risk | Post-Exploit |
| CVE-2026-26958 | LOW3.15 | filippo.io/edwards25519 v1.1.0 fixed in 1.1.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-67499 | LOW3.06 | github.com/containernetworking/plugins v1.7.1 fixed in 1.9.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-41889 | LOW3 | github.com/jackc/pgx/v5 v5.7.5 fixed in 5.9.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-39828 | LOW2.69 | golang.org/x/crypto v0.36.0 fixed in 0.52.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-39832 | LOW2.66 | golang.org/x/crypto v0.36.0 fixed in 0.52.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-33815 | LOW2.54 | github.com/jackc/pgx/v5 v5.7.5 fixed in 5.9.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-33816 | LOW2.54 | github.com/jackc/pgx/v5 v5.7.5 fixed in 5.9.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-25681 | LOW2.48 | golang.org/x/net v0.38.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27136 | LOW2.48 | golang.org/x/net v0.38.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-33997 | LOW2.48 | github.com/docker/docker v25.0.8+incompatible fixed in 29.3.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-39831 | LOW2.48 | golang.org/x/crypto v0.36.0 fixed in 0.52.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-25681 | LOW2.48 | golang.org/x/net v0.35.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27136 | LOW2.48 | golang.org/x/net v0.35.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-15558 | LOW2.45 | github.com/docker/cli v28.3.2+incompatible fixed in 29.2.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-39822 | LOW2.39 | stdlib v1.24.6 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-61728 | LOW2.29 | stdlib v1.24.6 fixed in 1.24.12, 1.25.6 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-52881 | LOW2.29 | github.com/opencontainers/selinux v1.11.1 fixed in 1.13.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-47913 | LOW2.29 | golang.org/x/crypto v0.36.0 fixed in 0.43.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-27139 | LOW2.12 | stdlib v1.24.6 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41579 | LOW1.84 | github.com/opencontainers/runc v1.3.1 fixed in 1.3.6, 1.4.3, 1.5.0-rc.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46600 | NONE0 | golang.org/x/net v0.38.0 fixed in 0.56.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39824 | NONE0 | golang.org/x/sys v0.34.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56852 | NONE0 | golang.org/x/text v0.23.0 fixed in 0.39.0 | 0.4% Theoretical Threat | Not Applicable |
| GHSA-hrxh-6v49-42gf | NONE0 | google.golang.org/grpc v1.73.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-35480 | NONE0 | github.com/ipld/go-ipld-prime v0.21.0 fixed in 0.22.0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42328 | NONE0 | github.com/ipld/go-ipld-prime v0.21.0 fixed in 0.23.0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-49140 | NONE0 | github.com/pion/interceptor v0.1.37 fixed in 0.1.39 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-21438 | NONE0 | github.com/quic-go/webtransport-go v0.8.1-0.20241018022711-4ac2c9250e66 fixed in 0.10.0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-57497 | NONE0 | github.com/quic-go/webtransport-go v0.8.1-0.20241018022711-4ac2c9250e66 fixed in 0.11.1 | — | Not Applicable |
| CVE-2026-24051 | NONE0 | go.opentelemetry.io/otel/sdk v1.37.0 fixed in 1.40.0 | 0.2% Theoretical Threat | Not Applicable |
| GO-2026-5932 | NONE0 | golang.org/x/crypto v0.36.0 No fix yet | — | Not Applicable |
| CVE-2026-39824 | NONE0 | golang.org/x/sys v0.31.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56852 | NONE0 | golang.org/x/text v0.28.0 fixed in 0.39.0 | 0.4% Theoretical Threat | Not Applicable |
| GHSA-hrxh-6v49-42gf | NONE0 | google.golang.org/grpc v1.72.1 fixed in 1.82.1 | — | Not Applicable |
| CVE-2026-46600 | NONE0 | golang.org/x/net v0.35.0 fixed in 0.56.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39824 | NONE0 | golang.org/x/sys v0.30.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.