packaged by Chainguard
Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.
Expand | CVE ID | Severity | Package | Version | Last detected |
|---|---|---|---|---|---|
CVE-2026-39831 | Critical | golang.org/x/crypto | v0.36.0 | ||
CVE-2025-68121 | Critical | stdlib | go1.25.3 | ||
CVE-2026-39834 | Critical | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-33186 | Critical | google.golang.org/grpc | v1.72.1 | ||
CVE-2026-39833 | Critical | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-31789 | Critical | libcrypto3 | 3.6.0-r0 | ||
CVE-2025-15467 | Critical | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-33186 | Critical | google.golang.org/grpc | v1.72.1 | ||
CVE-2026-39831 | Critical | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-39833 | Critical | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-39833 | Critical | golang.org/x/crypto | v0.36.0 | ||
CVE-2025-68121 | Critical | stdlib | go1.25.3 | ||
CVE-2026-39833 | Critical | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-5450 | Critical | glibc | 2.42-r2 | ||
CVE-2026-39831 | Critical | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-39831 | Critical | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-39831 | Critical | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-34182 | Critical | libcrypto3 | 3.6.0-r0 | ||
CVE-2025-68121 | Critical | stdlib | go1.25.3 | ||
CVE-2026-39834 | Critical | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-33186 | Critical | google.golang.org/grpc | v1.72.1 | ||
CVE-2026-39834 | Critical | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-39834 | Critical | golang.org/x/crypto | v0.36.0 | ||
CVE-2025-68121 | Critical | stdlib | go1.25.3 | ||
CVE-2025-68121 | Critical | stdlib | go1.25.3 | ||
CVE-2026-39834 | Critical | golang.org/x/crypto | v0.36.0 | ||
CVE-2025-68121 | Critical | stdlib | go1.25.3 | ||
CVE-2026-39833 | Critical | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-33186 | Critical | google.golang.org/grpc | v1.72.1 | ||
CVE-2026-33186 | Critical | google.golang.org/grpc | v1.72.1 | ||
CVE-2025-61729 | High | stdlib | go1.25.3 | ||
CVE-2025-61729 | High | stdlib | go1.25.3 | ||
CVE-2026-27145 | High | stdlib | go1.25.3 | ||
CVE-2026-42504 | High | stdlib | go1.25.3 | ||
CVE-2026-46597 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2025-61726 | High | stdlib | go1.25.3 | ||
CVE-2026-7383 | High | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-42499 | High | stdlib | go1.25.3 | ||
CVE-2026-32281 | High | stdlib | go1.25.3 | ||
CVE-2026-35469 | High | github.com/moby/spdystream | v0.5.0 | ||
CVE-2026-32280 | High | stdlib | go1.25.3 | ||
CVE-2026-39883 | High | go.opentelemetry.io/otel/sdk | v1.34.0 | ||
CVE-2026-33814 | High | golang.org/x/net | v0.38.0 | ||
CVE-2026-25679 | High | stdlib | go1.25.3 | ||
CVE-2026-39830 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-39828 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-39828 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2025-69420 | High | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-39836 | High | stdlib | go1.25.3 | ||
CVE-2026-39832 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-39836 | High | stdlib | go1.25.3 | ||
CVE-2026-39835 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2025-47913 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-39835 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-42765 | High | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-39829 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-39835 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-5928 | High | glibc | 2.42-r2 | ||
CVE-2026-24051 | High | go.opentelemetry.io/otel/sdk | v1.34.0 | ||
CVE-2026-33814 | High | golang.org/x/net | v0.38.0 | ||
CVE-2026-33811 | High | stdlib | go1.25.3 | ||
CVE-2026-42499 | High | stdlib | go1.25.3 | ||
CVE-2026-33814 | High | stdlib | go1.25.3 | ||
CVE-2026-32281 | High | stdlib | go1.25.3 | ||
CVE-2026-28386 | High | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-33811 | High | stdlib | go1.25.3 | ||
CVE-2026-39820 | High | stdlib | go1.25.3 | ||
CVE-2026-33814 | High | stdlib | go1.25.3 | ||
CVE-2026-32280 | High | stdlib | go1.25.3 | ||
CVE-2026-39828 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-4437 | High | glibc | 2.42-r2 | ||
CVE-2026-32283 | High | stdlib | go1.25.3 | ||
CVE-2026-5435 | High | glibc | 2.42-r2 | ||
CVE-2026-32283 | High | stdlib | go1.25.3 | ||
CVE-2026-0861 | High | glibc | 2.42-r2 | ||
CVE-2026-27145 | High | stdlib | go1.25.3 | ||
CVE-2025-15281 | High | glibc | 2.42-r2 | ||
CVE-2026-24051 | High | go.opentelemetry.io/otel/sdk | v1.34.0 | ||
CVE-2026-27145 | High | stdlib | go1.25.3 | ||
CVE-2026-42499 | High | stdlib | go1.25.3 | ||
CVE-2026-42504 | High | stdlib | go1.25.3 | ||
CVE-2026-39821 | High | golang.org/x/net | v0.38.0 | ||
CVE-2026-28390 | High | libcrypto3 | 3.6.0-r0 | ||
CVE-2025-61729 | High | stdlib | go1.25.3 | ||
CVE-2026-46597 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-35469 | High | github.com/moby/spdystream | v0.5.0 | ||
CVE-2025-61726 | High | stdlib | go1.25.3 | ||
CVE-2026-4046 | High | glibc | 2.42-r2 | ||
CVE-2025-61726 | High | stdlib | go1.25.3 | ||
CVE-2025-69421 | High | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-39883 | High | go.opentelemetry.io/otel/sdk | v1.34.0 | ||
CVE-2026-35469 | High | github.com/moby/spdystream | v0.5.0 | ||
CVE-2026-45445 | High | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-33814 | High | golang.org/x/net | v0.38.0 | ||
CVE-2026-32281 | High | stdlib | go1.25.3 | ||
CVE-2025-61726 | High | stdlib | go1.25.3 | ||
CVE-2026-35469 | High | github.com/moby/spdystream | v0.5.0 | ||
CVE-2026-39836 | High | stdlib | go1.25.3 | ||
CVE-2026-24051 | High | go.opentelemetry.io/otel/sdk | v1.34.0 | ||
CVE-2026-0915 | High | glibc | 2.42-r2 | ||
CVE-2026-39832 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-39820 | High | stdlib | go1.25.3 | ||
CVE-2026-33814 | High | golang.org/x/net | v0.38.0 | ||
CVE-2026-32280 | High | stdlib | go1.25.3 | ||
CVE-2026-32283 | High | stdlib | go1.25.3 | ||
CVE-2026-46595 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-39832 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-33814 | High | stdlib | go1.25.3 | ||
CVE-2026-33811 | High | stdlib | go1.25.3 | ||
CVE-2026-25679 | High | stdlib | go1.25.3 | ||
CVE-2026-42508 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-39832 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-27145 | High | stdlib | go1.25.3 | ||
CVE-2026-39828 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-32283 | High | stdlib | go1.25.3 | ||
CVE-2026-39835 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-46597 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-27145 | High | stdlib | go1.25.3 | ||
CVE-2026-45447 | High | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-42499 | High | stdlib | go1.25.3 | ||
CVE-2026-33811 | High | stdlib | go1.25.3 | ||
CVE-2026-42499 | High | stdlib | go1.25.3 | ||
CVE-2026-33814 | High | stdlib | go1.25.3 | ||
CVE-2026-42764 | High | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-24051 | High | go.opentelemetry.io/otel/sdk | v1.34.0 | ||
CVE-2025-52881 | High | github.com/opencontainers/selinux | v1.11.1 | ||
CVE-2026-39821 | High | golang.org/x/net | v0.38.0 | ||
CVE-2026-28388 | High | libcrypto3 | 3.6.0-r0 | ||
CVE-2025-61726 | High | stdlib | go1.25.3 | ||
CVE-2026-39836 | High | stdlib | go1.25.3 | ||
CVE-2025-52881 | High | github.com/opencontainers/selinux | v1.11.1 | ||
CVE-2025-61729 | High | stdlib | go1.25.3 | ||
CVE-2026-46597 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-42504 | High | stdlib | go1.25.3 | ||
CVE-2026-39821 | High | golang.org/x/net | v0.38.0 | ||
CVE-2026-46597 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2025-47913 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-39829 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-28389 | High | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-32280 | High | stdlib | go1.25.3 | ||
CVE-2026-39829 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-32281 | High | stdlib | go1.25.3 | ||
CVE-2026-39883 | High | go.opentelemetry.io/otel/sdk | v1.34.0 | ||
CVE-2026-33811 | High | stdlib | go1.25.3 | ||
CVE-2026-33814 | High | stdlib | go1.25.3 | ||
CVE-2026-32280 | High | stdlib | go1.25.3 | ||
CVE-2026-34180 | High | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-32281 | High | stdlib | go1.25.3 | ||
CVE-2026-39830 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-39820 | High | stdlib | go1.25.3 | ||
CVE-2026-33814 | High | golang.org/x/net | v0.38.0 | ||
CVE-2026-25679 | High | stdlib | go1.25.3 | ||
CVE-2026-39830 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-46595 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-33814 | High | golang.org/x/net | v0.38.0 | ||
CVE-2026-32283 | High | stdlib | go1.25.3 | ||
CVE-2026-39830 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-42508 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-39828 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2025-47913 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-39836 | High | stdlib | go1.25.3 | ||
CVE-2025-61729 | High | stdlib | go1.25.3 | ||
CVE-2026-25679 | High | stdlib | go1.25.3 | ||
CVE-2025-47913 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-42504 | High | stdlib | go1.25.3 | ||
CVE-2026-39829 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-39835 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-42499 | High | stdlib | go1.25.3 | ||
CVE-2026-42504 | High | stdlib | go1.25.3 | ||
CVE-2025-61726 | High | stdlib | go1.25.3 | ||
CVE-2025-61729 | High | stdlib | go1.25.3 | ||
CVE-2026-39821 | High | golang.org/x/net | v0.38.0 | ||
CVE-2026-39820 | High | stdlib | go1.25.3 | ||
CVE-2026-39821 | High | golang.org/x/net | v0.38.0 | ||
CVE-2026-24051 | High | go.opentelemetry.io/otel/sdk | v1.34.0 | ||
CVE-2026-39883 | High | go.opentelemetry.io/otel/sdk | v1.34.0 | ||
CVE-2026-34183 | High | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-27145 | High | stdlib | go1.25.3 | ||
CVE-2025-52881 | High | github.com/opencontainers/selinux | v1.11.1 | ||
CVE-2026-32283 | High | stdlib | go1.25.3 | ||
CVE-2026-39821 | High | golang.org/x/net | v0.38.0 | ||
CVE-2026-39830 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-42508 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-46595 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-32280 | High | stdlib | go1.25.3 | ||
CVE-2026-42508 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-46595 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-39832 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-28387 | High | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-32281 | High | stdlib | go1.25.3 | ||
CVE-2026-34181 | High | libcrypto3 | 3.6.0-r0 | ||
CVE-2025-47913 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-39836 | High | stdlib | go1.25.3 | ||
CVE-2026-39820 | High | stdlib | go1.25.3 | ||
CVE-2026-39829 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-39883 | High | go.opentelemetry.io/otel/sdk | v1.34.0 | ||
CVE-2026-31790 | High | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-42508 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2025-69419 | High | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-9076 | High | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-33811 | High | stdlib | go1.25.3 | ||
CVE-2026-39820 | High | stdlib | go1.25.3 | ||
CVE-2026-33814 | High | stdlib | go1.25.3 | ||
CVE-2026-25679 | High | stdlib | go1.25.3 | ||
CVE-2026-46595 | High | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-25679 | High | stdlib | go1.25.3 | ||
CVE-2026-42504 | High | stdlib | go1.25.3 | ||
CVE-2025-47914 | Medium | golang.org/x/crypto | v0.36.0 | ||
CVE-2025-61727 | Medium | stdlib | go1.25.3 | ||
CVE-2026-39827 | Medium | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-42506 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2025-61728 | Medium | stdlib | go1.25.3 | ||
CVE-2026-39825 | Medium | stdlib | go1.25.3 | ||
CVE-2025-13281 | Medium | k8s.io/kubernetes | v1.34.1+dirty | ||
CVE-2026-46598 | Medium | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-42502 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-4438 | Medium | glibc | 2.42-r2 | ||
CVE-2025-58190 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-39826 | Medium | stdlib | go1.25.3 | ||
CVE-2026-46598 | Medium | golang.org/x/crypto | v0.36.0 | ||
CVE-2025-61730 | Medium | stdlib | go1.25.3 | ||
CVE-2025-69418 | Medium | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-27142 | Medium | stdlib | go1.25.3 | ||
CVE-2026-32282 | Medium | stdlib | go1.25.3 | ||
CVE-2026-46598 | Medium | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-42769 | Medium | libcrypto3 | 3.6.0-r0 | ||
CVE-2023-4039 | Medium | libgcc | 15.2.0-r2 | ||
CVE-2025-47914 | Medium | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-27142 | Medium | stdlib | go1.25.3 | ||
CVE-2026-39827 | Medium | golang.org/x/crypto | v0.36.0 | ||
CVE-2025-47914 | Medium | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-32289 | Medium | stdlib | go1.25.3 | ||
CVE-2025-61730 | Medium | stdlib | go1.25.3 | ||
CVE-2026-39827 | Medium | golang.org/x/crypto | v0.36.0 | ||
CVE-2025-13281 | Medium | k8s.io/kubernetes | v1.34.1+dirty | ||
CVE-2026-42507 | Medium | stdlib | go1.25.3 | ||
CVE-2026-39823 | Medium | stdlib | go1.25.3 | ||
CVE-2026-25680 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-42502 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-25681 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-42507 | Medium | stdlib | go1.25.3 | ||
CVE-2026-25680 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-32288 | Medium | stdlib | go1.25.3 | ||
CVE-2025-11187 | Medium | libcrypto3 | 3.6.0-r0 | ||
CVE-2025-15469 | Medium | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-32288 | Medium | stdlib | go1.25.3 | ||
CVE-2025-61728 | Medium | stdlib | go1.25.3 | ||
CVE-2025-58181 | Medium | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-39825 | Medium | stdlib | go1.25.3 | ||
CVE-2025-61727 | Medium | stdlib | go1.25.3 | ||
CVE-2026-27136 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-39826 | Medium | stdlib | go1.25.3 | ||
CVE-2026-35188 | Medium | libcrypto3 | 3.6.0-r0 | ||
CVE-2025-47911 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-39826 | Medium | stdlib | go1.25.3 | ||
CVE-2026-39825 | Medium | stdlib | go1.25.3 | ||
CVE-2025-61727 | Medium | stdlib | go1.25.3 | ||
CVE-2025-58190 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-27142 | Medium | stdlib | go1.25.3 | ||
CVE-2026-32282 | Medium | stdlib | go1.25.3 | ||
CVE-2025-58190 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2025-13281 | Medium | k8s.io/kubernetes | v1.34.1+dirty | ||
CVE-2026-32289 | Medium | stdlib | go1.25.3 | ||
CVE-2025-61730 | Medium | stdlib | go1.25.3 | ||
CVE-2026-42506 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-32289 | Medium | stdlib | go1.25.3 | ||
CVE-2026-42506 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-32282 | Medium | stdlib | go1.25.3 | ||
CVE-2026-22795 | Medium | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-42507 | Medium | stdlib | go1.25.3 | ||
CVE-2026-32282 | Medium | stdlib | go1.25.3 | ||
CVE-2026-32289 | Medium | stdlib | go1.25.3 | ||
CVE-2025-61727 | Medium | stdlib | go1.25.3 | ||
CVE-2025-15468 | Medium | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-42766 | Medium | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-39826 | Medium | stdlib | go1.25.3 | ||
CVE-2025-13281 | Medium | k8s.io/kubernetes | v1.34.1+dirty | ||
CVE-2026-39823 | Medium | stdlib | go1.25.3 | ||
CVE-2026-25680 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-42502 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2025-58190 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-39825 | Medium | stdlib | go1.25.3 | ||
CVE-2026-32288 | Medium | stdlib | go1.25.3 | ||
CVE-2026-39825 | Medium | stdlib | go1.25.3 | ||
CVE-2026-32288 | Medium | stdlib | go1.25.3 | ||
CVE-2025-61730 | Medium | stdlib | go1.25.3 | ||
CVE-2026-42506 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-42502 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-25681 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-39826 | Medium | stdlib | go1.25.3 | ||
CVE-2026-27142 | Medium | stdlib | go1.25.3 | ||
CVE-2026-46598 | Medium | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-25681 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2025-47914 | Medium | golang.org/x/crypto | v0.36.0 | ||
CVE-2025-61727 | Medium | stdlib | go1.25.3 | ||
CVE-2026-39827 | Medium | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-45446 | Medium | libcrypto3 | 3.6.0-r0 | ||
CVE-2025-68160 | Medium | libcrypto3 | 3.6.0-r0 | ||
CVE-2025-47911 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-6238 | Medium | glibc | 2.42-r2 | ||
CVE-2026-27171 | Medium | zlib | 1.3.1-r51 | ||
CVE-2025-61728 | Medium | stdlib | go1.25.3 | ||
CVE-2026-32289 | Medium | stdlib | go1.25.3 | ||
CVE-2026-27136 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2025-13281 | Medium | k8s.io/kubernetes | v1.34.1+dirty | ||
CVE-2026-27136 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2025-47911 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-42507 | Medium | stdlib | go1.25.3 | ||
CVE-2026-32282 | Medium | stdlib | go1.25.3 | ||
CVE-2026-32288 | Medium | stdlib | go1.25.3 | ||
CVE-2025-61730 | Medium | stdlib | go1.25.3 | ||
CVE-2026-42502 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-27142 | Medium | stdlib | go1.25.3 | ||
CVE-2026-42502 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-42506 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-42767 | Medium | libcrypto3 | 3.6.0-r0 | ||
CVE-2025-61728 | Medium | stdlib | go1.25.3 | ||
CVE-2026-39823 | Medium | stdlib | go1.25.3 | ||
CVE-2026-42507 | Medium | stdlib | go1.25.3 | ||
CVE-2026-39823 | Medium | stdlib | go1.25.3 | ||
CVE-2026-32282 | Medium | stdlib | go1.25.3 | ||
CVE-2026-27136 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-46598 | Medium | golang.org/x/crypto | v0.36.0 | ||
CVE-2026-27136 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2025-47914 | Medium | golang.org/x/crypto | v0.36.0 | ||
CVE-2025-61728 | Medium | stdlib | go1.25.3 | ||
CVE-2025-47911 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-32289 | Medium | stdlib | go1.25.3 | ||
CVE-2026-39827 | Medium | golang.org/x/crypto | v0.36.0 | ||
CVE-2025-58181 | Medium | golang.org/x/crypto | v0.36.0 | ||
CVE-2025-47911 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2025-58181 | Medium | golang.org/x/crypto | v0.36.0 | ||
CVE-2025-61727 | Medium | stdlib | go1.25.3 | ||
CVE-2025-58181 | Medium | golang.org/x/crypto | v0.36.0 | ||
CVE-2025-58190 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-25681 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-39826 | Medium | stdlib | go1.25.3 | ||
CVE-2026-27142 | Medium | stdlib | go1.25.3 | ||
CVE-2026-25681 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-39825 | Medium | stdlib | go1.25.3 | ||
CVE-2026-25680 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2025-61730 | Medium | stdlib | go1.25.3 | ||
CVE-2025-47911 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-2673 | Medium | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-42507 | Medium | stdlib | go1.25.3 | ||
CVE-2026-27136 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2023-4039 | Medium | libstdc++ | 15.2.0-r2 | ||
CVE-2026-25680 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-22796 | Medium | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-32288 | Medium | stdlib | go1.25.3 | ||
CVE-2026-25680 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2025-66199 | Medium | libcrypto3 | 3.6.0-r0 | ||
CVE-2025-13281 | Medium | k8s.io/kubernetes | v1.34.1+dirty | ||
CVE-2026-39823 | Medium | stdlib | go1.25.3 | ||
CVE-2025-58181 | Medium | golang.org/x/crypto | v0.36.0 | ||
CVE-2025-58190 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-39823 | Medium | stdlib | go1.25.3 | ||
CVE-2026-42506 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2026-25681 | Medium | golang.org/x/net | v0.38.0 | ||
CVE-2025-61728 | Medium | stdlib | go1.25.3 | ||
CVE-2026-27139 | Low | stdlib | go1.25.3 | ||
CVE-2026-27139 | Low | stdlib | go1.25.3 | ||
CVE-2026-27139 | Low | stdlib | go1.25.3 | ||
CVE-2026-39824 | Low | golang.org/x/sys | v0.31.0 | ||
CVE-2026-39824 | Low | golang.org/x/sys | v0.31.0 | ||
CVE-2026-27139 | Low | stdlib | go1.25.3 | ||
CVE-2026-42770 | Low | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-42768 | Low | libcrypto3 | 3.6.0-r0 | ||
CVE-2026-27139 | Low | stdlib | go1.25.3 | ||
CVE-2026-39824 | Low | golang.org/x/sys | v0.31.0 | ||
CVE-2026-39824 | Low | golang.org/x/sys | v0.31.0 | ||
CVE-2026-27139 | Low | stdlib | go1.25.3 | ||
CVE-2026-39824 | Low | golang.org/x/sys | v0.31.0 | ||
CVE-2026-39824 | Low | golang.org/x/sys | v0.31.0 |