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-34182 | Critical | libssl3 | 3.6.2-r3 | ||
CVE-2026-5450 | Critical | glibc | 2.43-r7 | ||
CVE-2026-34182 | Critical | libcrypto3 | 3.6.2-r3 | ||
CVE-2026-42764 | High | libcrypto3 | 3.6.2-r3 | ||
CVE-2026-42587 | High | netty-codec-http | 4.1.132.Final | ||
CVE-2026-34180 | High | libssl3 | 3.6.2-r3 | ||
CVE-2026-42579 | High | netty-codec-dns | 4.1.132.Final | ||
CVE-2026-42579 | High | netty-codec-dns | 4.1.132.Final | ||
CVE-2026-50010 | High | netty-handler | 4.1.132.Final | ||
CVE-2026-34181 | High | libssl3 | 3.6.2-r3 | ||
CVE-2026-45445 | High | libssl3 | 3.6.2-r3 | ||
CVE-2026-45416 | High | netty-handler | 4.1.132.Final | ||
CVE-2026-42584 | High | netty-codec-http | 4.1.132.Final | ||
CVE-2026-50010 | High | netty-handler | 4.1.132.Final | ||
CVE-2026-42587 | High | netty-codec-http | 4.1.132.Final | ||
CVE-2026-42584 | High | netty-codec-http | 4.1.132.Final | ||
CVE-2026-0861 | High | glibc | 2.43-r7 | ||
CVE-2026-42583 | High | netty-codec | 4.1.132.Final | ||
CVE-2026-42583 | High | netty-codec | 4.1.132.Final | ||
CVE-2026-50010 | High | netty-handler | 4.1.132.Final | ||
CVE-2026-42765 | High | libcrypto3 | 3.6.2-r3 | ||
CVE-2026-42587 | High | netty-codec-http2 | 4.1.132.Final | ||
CVE-2026-34180 | High | libcrypto3 | 3.6.2-r3 | ||
CVE-2026-44249 | High | netty-handler | 4.1.132.Final | ||
CVE-2026-34183 | High | libssl3 | 3.6.2-r3 | ||
CVE-2026-45445 | High | libcrypto3 | 3.6.2-r3 | ||
CVE-2026-44249 | High | netty-handler | 4.1.132.Final | ||
CVE-2026-4046 | High | glibc | 2.43-r7 | ||
CVE-2026-5928 | High | glibc | 2.43-r7 | ||
CVE-2026-44249 | High | netty-handler | 4.1.132.Final | ||
CVE-2026-34183 | High | libcrypto3 | 3.6.2-r3 | ||
CVE-2026-42583 | High | netty-codec | 4.1.132.Final | ||
CVE-2026-7383 | High | libcrypto3 | 3.6.2-r3 | ||
CVE-2026-11822 | High | sqlite-libs | 3.51.1-r0 | ||
CVE-2026-9076 | High | libssl3 | 3.6.2-r3 | ||
CVE-2026-42764 | High | libssl3 | 3.6.2-r3 | ||
CVE-2026-45416 | High | netty-handler | 4.1.132.Final | ||
CVE-2026-45674 | High | netty-resolver-dns | 4.1.132.Final | ||
CVE-2026-47691 | High | netty-resolver-dns | 4.1.132.Final | ||
CVE-2026-45416 | High | netty-handler | 4.1.132.Final | ||
CVE-2026-42584 | High | netty-codec-http | 4.1.132.Final | ||
CVE-2026-45447 | High | libcrypto3 | 3.6.2-r3 | ||
CVE-2026-50010 | High | netty-handler | 4.1.132.Final | ||
CVE-2026-45416 | High | netty-handler | 4.1.132.Final | ||
CVE-2026-7383 | High | libssl3 | 3.6.2-r3 | ||
CVE-2026-9076 | High | libcrypto3 | 3.6.2-r3 | ||
CVE-2026-42765 | High | libssl3 | 3.6.2-r3 | ||
CVE-2026-42587 | High | netty-codec-http2 | 4.1.132.Final | ||
CVE-2026-42587 | High | netty-codec-http | 4.1.132.Final | ||
CVE-2026-42584 | High | netty-codec-http | 4.1.132.Final | ||
CVE-2026-47691 | High | netty-resolver-dns | 4.1.132.Final | ||
CVE-2026-44249 | High | netty-handler | 4.1.132.Final | ||
CVE-2026-42587 | High | netty-codec-http | 4.1.132.Final | ||
CVE-2026-42583 | High | netty-codec | 4.1.132.Final | ||
CVE-2026-4437 | High | glibc | 2.43-r7 | ||
CVE-2026-45674 | High | netty-resolver-dns | 4.1.132.Final | ||
CVE-2026-45447 | High | libssl3 | 3.6.2-r3 | ||
CVE-2026-11824 | High | sqlite-libs | 3.51.1-r0 | ||
CVE-2026-34181 | High | libcrypto3 | 3.6.2-r3 | ||
CVE-2026-5435 | High | glibc | 2.43-r7 | ||
CVE-2026-42767 | Medium | libssl3 | 3.6.2-r3 | ||
CVE-2026-48043 | Medium | netty-codec-http2 | 4.1.132.Final | ||
CVE-2026-42581 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-42766 | Medium | libcrypto3 | 3.6.2-r3 | ||
CVE-2026-42769 | Medium | libssl3 | 3.6.2-r3 | ||
CVE-2026-47244 | Medium | netty-codec-http2 | 4.1.132.Final | ||
CVE-2025-68161 | Medium | log4j-core | 2.25.0 | ||
CVE-2026-42580 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-50560 | Medium | netty-codec-http2 | 4.1.132.Final | ||
CVE-2025-48924 | Medium | commons-lang3 | 3.9 | ||
CVE-2026-42585 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-42581 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-42585 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-45446 | Medium | libcrypto3 | 3.6.2-r3 | ||
CVE-2026-50020 | Medium | netty-codec-http | 4.1.132.Final | ||
GHSA-72hv-8253-57qq | Medium | jackson-core | 2.15.0 | ||
CVE-2026-45446 | Medium | libssl3 | 3.6.2-r3 | ||
CVE-2026-34477 | Medium | log4j-core | 2.19.0 | ||
CVE-2026-50020 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-34480 | Medium | log4j-core | 2.25.0 | ||
CVE-2025-22227 | Medium | reactor-netty-http | 1.0.45 | ||
CVE-2026-35188 | Medium | libcrypto3 | 3.6.2-r3 | ||
CVE-2026-45673 | Medium | netty-resolver-dns | 4.1.132.Final | ||
CVE-2026-50020 | Medium | netty-codec-http | 4.1.132.Final | ||
GHSA-72hv-8253-57qq | Medium | jackson-core | 2.15.0 | ||
GHSA-72hv-8253-57qq | Medium | jackson-core | 2.17.2 | ||
CVE-2026-50020 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-47244 | Medium | netty-codec-http2 | 4.1.132.Final | ||
CVE-2026-50560 | Medium | netty-codec-http2 | 4.1.132.Final | ||
CVE-2026-5588 | Medium | bcpkix-jdk18on | 1.79 | ||
CVE-2026-42769 | Medium | libcrypto3 | 3.6.2-r3 | ||
GHSA-72hv-8253-57qq | Medium | jackson-core | 2.15.0 | ||
GHSA-72hv-8253-57qq | Medium | jackson-core | 2.15.0 | ||
GHSA-72hv-8253-57qq | Medium | jackson-core | 2.15.0 | ||
GHSA-72hv-8253-57qq | Medium | jackson-core | 2.15.0 | ||
CVE-2026-48043 | Medium | netty-codec-http2 | 4.1.132.Final | ||
CVE-2026-6238 | Medium | glibc | 2.43-r7 | ||
GHSA-72hv-8253-57qq | Medium | jackson-core | 2.15.0 | ||
CVE-2026-34479 | Medium | log4j-1.2-api | 2.19.0 | ||
CVE-2025-68161 | Medium | log4j-core | 2.19.0 | ||
CVE-2026-34479 | Medium | log4j-1.2-api | 2.19.0 | ||
CVE-2026-0636 | Medium | bcprov-jdk18on | 1.79 | ||
CVE-2026-42585 | Medium | netty-codec-http | 4.1.132.Final | ||
GHSA-72hv-8253-57qq | Medium | jackson-core | 2.15.0 | ||
CVE-2025-48924 | Medium | commons-lang3 | 3.9 | ||
GHSA-72hv-8253-57qq | Medium | jackson-core | 2.17.2 | ||
CVE-2026-42580 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-41417 | Medium | netty-codec-http | 4.1.132.Final | ||
GHSA-72hv-8253-57qq | Medium | jackson-core | 2.15.0 | ||
CVE-2026-34479 | Medium | log4j-1.2-api | 2.19.0 | ||
CVE-2026-45673 | Medium | netty-resolver-dns | 4.1.132.Final | ||
CVE-2026-42580 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-34480 | Medium | log4j-core | 2.19.0 | ||
CVE-2026-42766 | Medium | libssl3 | 3.6.2-r3 | ||
CVE-2026-42581 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-42585 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-42581 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-35188 | Medium | libssl3 | 3.6.2-r3 | ||
CVE-2026-41417 | Medium | netty-codec-http | 4.1.132.Final | ||
GHSA-72hv-8253-57qq | Medium | jackson-core | 2.15.0 | ||
CVE-2026-34477 | Medium | log4j-core | 2.25.0 | ||
CVE-2026-42767 | Medium | libcrypto3 | 3.6.2-r3 | ||
CVE-2026-4438 | Medium | glibc | 2.43-r7 | ||
CVE-2026-41417 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-42580 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-41417 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-34478 | Medium | log4j-core | 2.25.0 | ||
CVE-2026-42578 | Low | netty-handler-proxy | 4.1.132.Final | ||
CVE-2026-42768 | Low | libcrypto3 | 3.6.2-r3 | ||
CVE-2026-42770 | Low | libssl3 | 3.6.2-r3 | ||
CVE-2026-42768 | Low | libssl3 | 3.6.2-r3 | ||
CVE-2026-42770 | Low | libcrypto3 | 3.6.2-r3 |