knative-eventing-fips-channel-dispatcherpackaged by Chainguard
packaged by Chainguard
Last changed
Request a free trial
Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.
Tag:
Severity:All
Expand | CVE ID | Severity | Package | Version | Last detected |
|---|---|---|---|---|---|
CVE-2026-63073 | Critical | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-39833 | Critical | golang.org/x/crypto | v0.45.0 | ||
CVE-2026-39832 | Critical | golang.org/x/crypto | v0.45.0 | ||
CVE-2026-46595 | Critical | golang.org/x/crypto | v0.45.0 | ||
CVE-2026-39830 | Critical | golang.org/x/crypto | v0.45.0 | ||
CVE-2025-68121 | Critical | stdlib | go1.25.4 | ||
CVE-2026-42508 | Critical | golang.org/x/crypto | v0.45.0 | ||
CVE-2026-5450 | Critical | glibc | 2.42-r4 | ||
CVE-2026-78663 | Critical | stdlib | go1.25.4 | ||
CVE-2026-56857 | Critical | stdlib | go1.25.4 | ||
CVE-2026-39834 | Critical | golang.org/x/crypto | v0.45.0 | ||
CVE-2025-15467 | Critical | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-33186 | Critical | google.golang.org/grpc | v1.75.0 | ||
CVE-2026-39831 | Critical | golang.org/x/crypto | v0.45.0 | ||
CVE-2026-31789 | Critical | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-34182 | Critical | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-78663 | Critical | golang.org/x/net | v0.47.0 | ||
CVE-2026-75803 | Critical | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-39821 | High | stdlib | go1.25.4 | ||
CVE-2026-94439 | High | stdlib | go1.25.4 | ||
CVE-2026-63076 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-42764 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-39821 | High | golang.org/x/net | v0.47.0 | ||
CVE-2026-84782 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2025-61726 | High | stdlib | go1.25.4 | ||
CVE-2026-19499 | High | glibc | 2.42-r4 | ||
CVE-2026-39883 | High | go.opentelemetry.io/otel/sdk | v1.37.0 | ||
CVE-2026-78659 | High | golang.org/x/net | v0.47.0 | ||
CVE-2026-54873 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-32281 | High | stdlib | go1.25.4 | ||
CVE-2026-72897 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-24051 | High | go.opentelemetry.io/otel/sdk | v1.37.0 | ||
CVE-2026-28389 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-0915 | High | glibc | 2.42-r4 | ||
CVE-2026-56852 | High | golang.org/x/text | v0.31.0 | ||
CVE-2026-78662 | High | golang.org/x/crypto | v0.45.0 | ||
CVE-2026-63072 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-39829 | High | golang.org/x/crypto | v0.45.0 | ||
CVE-2026-78660 | High | stdlib | go1.25.4 | ||
CVE-2026-25679 | High | stdlib | go1.25.4 | ||
CVE-2025-69420 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-78667 | High | stdlib | go1.25.4 | ||
CVE-2026-56851 | High | golang.org/x/text | v0.31.0 | ||
GHSA-hrxh-6v49-42gf | High | google.golang.org/grpc | v1.75.0 | ||
CVE-2026-14456 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-84445 | High | google.golang.org/grpc | v1.75.0 | ||
CVE-2026-78669 | High | stdlib | go1.25.4 | ||
CVE-2026-42765 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-33818 | High | stdlib | go1.25.4 | ||
CVE-2026-34180 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-33814 | High | stdlib | go1.25.4 | ||
CVE-2026-32283 | High | stdlib | go1.25.4 | ||
CVE-2025-15281 | High | glibc | 2.42-r4 | ||
CVE-2026-28390 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-56859 | High | stdlib | go1.25.4 | ||
CVE-2026-46600 | High | golang.org/x/net | v0.47.0 | ||
CVE-2026-0861 | High | glibc | 2.42-r4 | ||
CVE-2026-97031 | High | stdlib | go1.25.4 | ||
CVE-2026-4437 | High | glibc | 2.42-r4 | ||
CVE-2026-33814 | High | golang.org/x/net | v0.47.0 | ||
CVE-2026-9076 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-84304 | High | google.golang.org/grpc | v1.75.0 | ||
CVE-2025-69421 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-39820 | High | stdlib | go1.25.4 | ||
CVE-2026-34986 | High | github.com/go-jose/go-jose/v3 | v3.0.4 | ||
CVE-2025-69419 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-56853 | High | stdlib | go1.25.4 | ||
CVE-2026-78669 | High | golang.org/x/net | v0.47.0 | ||
CVE-2026-56855 | High | golang.org/x/crypto | v0.45.0 | ||
CVE-2026-42499 | High | stdlib | go1.25.4 | ||
CVE-2026-78660 | High | golang.org/x/net | v0.47.0 | ||
CVE-2026-45447 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-29181 | High | go.opentelemetry.io/otel | v1.37.0 | ||
CVE-2026-54876 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-5928 | High | glibc | 2.42-r4 | ||
CVE-2026-54874 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-39836 | High | stdlib | go1.25.4 | ||
CVE-2025-61729 | High | stdlib | go1.25.4 | ||
CVE-2026-56854 | High | golang.org/x/crypto | v0.45.0 | ||
CVE-2026-4046 | High | glibc | 2.42-r4 | ||
CVE-2026-33811 | High | stdlib | go1.25.4 | ||
CVE-2026-42504 | High | stdlib | go1.25.4 | ||
CVE-2026-28388 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-46597 | High | golang.org/x/crypto | v0.45.0 | ||
CVE-2025-61729 | High | knative-eventing-1.19-channel-dispatcher-compat | 1.19.8-r1 | ||
CVE-2026-5435 | High | glibc | 2.42-r4 | ||
CVE-2026-56866 | High | stdlib | go1.25.4 | ||
CVE-2026-34181 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-34183 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-28386 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-18798 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-14457 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-78659 | High | stdlib | go1.25.4 | ||
CVE-2026-56862 | High | stdlib | go1.25.4 | ||
CVE-2026-94440 | High | stdlib | go1.25.4 | ||
CVE-2026-84784 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-63075 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-28387 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-7383 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-32280 | High | stdlib | go1.25.4 | ||
CVE-2026-27145 | High | stdlib | go1.25.4 | ||
CVE-2026-39822 | High | stdlib | go1.25.4 | ||
CVE-2026-31790 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-45445 | High | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-32289 | Medium | stdlib | go1.25.4 | ||
CVE-2026-35189 | Medium | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-42769 | Medium | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-75805 | Medium | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-75806 | Medium | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-27142 | Medium | stdlib | go1.25.4 | ||
CVE-2026-56860 | Medium | stdlib | go1.25.4 | ||
CVE-2026-80489 | Medium | glibc | 2.42-r4 | ||
CVE-2026-4438 | Medium | glibc | 2.42-r4 | ||
CVE-2026-77117 | Medium | glibc | 2.42-r4 | ||
CVE-2026-42506 | Medium | golang.org/x/net | v0.47.0 | ||
CVE-2026-6238 | Medium | glibc | 2.42-r4 | ||
CVE-2026-39825 | Medium | stdlib | go1.25.4 | ||
CVE-2026-42507 | Medium | stdlib | go1.25.4 | ||
CVE-2026-32282 | Medium | stdlib | go1.25.4 | ||
CVE-2026-22796 | Medium | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-42505 | Medium | stdlib | go1.25.4 | ||
CVE-2026-56858 | Medium | stdlib | go1.25.4 | ||
CVE-2026-46598 | Medium | golang.org/x/crypto | v0.45.0 | ||
CVE-2026-42502 | Medium | golang.org/x/net | v0.47.0 | ||
CVE-2026-2673 | Medium | libcrypto3 | 3.6.0-r4 | ||
CVE-2025-66199 | Medium | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-39835 | Medium | golang.org/x/crypto | v0.45.0 | ||
CVE-2026-6791 | Medium | glibc | 2.42-r4 | ||
CVE-2026-18374 | Medium | glibc | 2.42-r4 | ||
CVE-2026-86805 | Medium | glibc | 2.42-r4 | ||
CVE-2026-25681 | Medium | golang.org/x/net | v0.47.0 | ||
CVE-2026-39828 | Medium | golang.org/x/crypto | v0.45.0 | ||
CVE-2025-15468 | Medium | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-39823 | Medium | stdlib | go1.25.4 | ||
CVE-2026-32288 | Medium | stdlib | go1.25.4 | ||
CVE-2026-22795 | Medium | libcrypto3 | 3.6.0-r4 | ||
CVE-2025-68160 | Medium | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-39827 | Medium | golang.org/x/crypto | v0.45.0 | ||
CVE-2026-39882 | Medium | go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp | v1.37.0 | ||
CVE-2025-15469 | Medium | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-39826 | Medium | stdlib | go1.25.4 | ||
CVE-2026-19542 | Medium | glibc | 2.42-r4 | ||
CVE-2026-25680 | Medium | golang.org/x/net | v0.47.0 | ||
CVE-2025-11187 | Medium | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-42767 | Medium | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-75804 | Medium | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-35188 | Medium | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-84303 | Medium | google.golang.org/grpc | v1.75.0 | ||
CVE-2026-42772 | Medium | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-42766 | Medium | libcrypto3 | 3.6.0-r4 | ||
CVE-2025-61730 | Medium | stdlib | go1.25.4 | ||
CVE-2026-27136 | Medium | golang.org/x/net | v0.47.0 | ||
CVE-2026-89092 | Medium | glibc | 2.42-r4 | ||
CVE-2026-63074 | Medium | libcrypto3 | 3.6.0-r4 | ||
CVE-2025-69418 | Medium | libcrypto3 | 3.6.0-r4 | ||
CVE-2025-61728 | Medium | stdlib | go1.25.4 | ||
CVE-2026-8674 | Medium | glibc | 2.42-r4 | ||
CVE-2025-61727 | Medium | stdlib | go1.25.4 | ||
CVE-2026-45446 | Medium | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-39882 | Medium | go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp | v1.37.0 | ||
CVE-2026-35191 | Low | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-97399 | Low | glibc | 2.42-r4 | ||
CVE-2026-81870 | Low | go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp | v1.37.0 | ||
CVE-2026-81870 | Low | go.opentelemetry.io/otel/sdk | v1.37.0 | ||
CVE-2026-6368 | Low | glibc | 2.42-r4 | ||
CVE-2026-77696 | Low | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-42768 | Low | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-95818 | Low | glibc | 2.42-r4 | ||
CVE-2026-81870 | Low | go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc | v1.37.0 | ||
CVE-2026-81870 | Low | go.opentelemetry.io/otel/exporters/otlp/otlptrace | v1.37.0 | ||
CVE-2026-27139 | Low | stdlib | go1.25.4 | ||
CVE-2026-42770 | Low | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-54872 | Low | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-39824 | Low | golang.org/x/sys | v0.38.0 | ||
CVE-2026-54875 | Low | libcrypto3 | 3.6.0-r4 | ||
CVE-2026-94448 | Unknown | stdlib | go1.25.4 | ||
CVE-2026-97032 | Unknown | stdlib | go1.25.4 | ||
CVE-2026-97030 | Unknown | stdlib | go1.25.4 | ||
GO-2025-4155 | Unknown | knative-eventing-1.19-channel-dispatcher-compat | 1.19.8-r1 | ||
GO-2026-5932 | Unknown | golang.org/x/crypto | v0.45.0 | ||
CVE-2026-97032 | Unknown | golang.org/x/net | v0.47.0 | ||
GHSA-7c64-f9jr-v9h2 | Unknown | knative-eventing-1.19-channel-dispatcher-compat | 1.19.8-r1 |
Last updated:
The trusted source for open source
Talk to an expertProduct
Customers
© 2026 Chainguard, Inc. All Rights Reserved.
Chainguard® and the Chainguard logo are registered trademarks of Chainguard, Inc. in the United States and/or other countries.
The other respective trademarks mentioned on this page are owned by the respective companies and use of them does not imply any affiliation or endorsement.
Chainguard® and the Chainguard logo are registered trademarks of Chainguard, Inc. in the United States and/or other countries.
The other respective trademarks mentioned on this page are owned by the respective companies and use of them does not imply any affiliation or endorsement.