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-56817 | High | netty-codec-xml | 4.1.135.Final | ||
CVE-2026-59901 | High | netty-codec | 4.1.135.Final | ||
CVE-2026-59901 | High | netty-codec | 4.1.135.Final | ||
CVE-2026-56822 | High | netty-handler-ssl-ocsp | 4.1.135.Final | ||
CVE-2026-55833 | High | netty-codec-http | 4.1.135.Final | ||
CVE-2026-56817 | High | netty-codec-xml | 4.1.135.Final | ||
CVE-2026-55833 | High | netty-codec-http | 4.1.135.Final | ||
CVE-2026-56820 | High | netty-handler-ssl-ocsp | 4.1.135.Final | ||
CVE-2026-59901 | High | netty-codec | 4.1.135.Final | ||
CVE-2026-55851 | High | netty-codec-haproxy | 4.1.135.Final | ||
CVE-2026-55831 | High | netty-codec-http | 4.1.135.Final | ||
CVE-2026-56745 | High | netty-codec-http | 4.1.135.Final | ||
CVE-2026-59901 | High | netty-codec | 4.1.135.Final | ||
CVE-2026-56822 | High | netty-handler-ssl-ocsp | 4.1.135.Final | ||
CVE-2026-55851 | High | netty-codec-haproxy | 4.1.135.Final | ||
CVE-2026-56745 | High | netty-codec-http | 4.1.135.Final | ||
CVE-2026-56821 | High | netty-handler-ssl-ocsp | 4.1.135.Final | ||
CVE-2026-55831 | High | netty-codec-http | 4.1.135.Final | ||
CVE-2026-56817 | High | netty-codec-xml | 4.1.135.Final | ||
CVE-2026-56745 | High | netty-codec-http | 4.1.135.Final | ||
CVE-2026-56820 | High | netty-handler-ssl-ocsp | 4.1.135.Final | ||
CVE-2026-56821 | High | netty-handler-ssl-ocsp | 4.1.135.Final | ||
CVE-2026-59901 | High | netty-codec | 4.1.135.Final | ||
CVE-2026-55831 | High | netty-codec-http | 4.1.135.Final | ||
CVE-2026-55833 | High | netty-codec-http | 4.1.135.Final | ||
CVE-2026-54512 | High | jackson-databind | 2.19.2 | ||
CVE-2026-56820 | High | netty-handler-ssl-ocsp | 4.1.135.Final | ||
CVE-2026-56820 | High | netty-handler-ssl-ocsp | 4.1.135.Final | ||
CVE-2026-56821 | High | netty-handler-ssl-ocsp | 4.1.135.Final | ||
CVE-2026-55833 | High | netty-codec-http | 4.1.135.Final | ||
CVE-2026-59901 | High | netty-codec | 4.1.135.Final | ||
CVE-2026-55831 | High | netty-codec-http | 4.1.135.Final | ||
CVE-2026-55831 | High | netty-codec-http | 4.1.135.Final | ||
CVE-2026-56745 | High | netty-codec-http | 4.1.135.Final | ||
CVE-2026-56821 | High | netty-handler-ssl-ocsp | 4.1.135.Final | ||
CVE-2026-55831 | High | netty-codec-http | 4.1.135.Final | ||
CVE-2026-56745 | High | netty-codec-http | 4.1.135.Final | ||
CVE-2026-56741 | High | jline-remote-telnet | 3.9.0 | ||
CVE-2026-54513 | High | jackson-databind | 2.19.2 | ||
CVE-2026-55851 | High | netty-codec-haproxy | 4.1.135.Final | ||
CVE-2026-56745 | High | netty-codec-http | 4.1.135.Final | ||
CVE-2026-56820 | High | netty-handler-ssl-ocsp | 4.1.135.Final | ||
CVE-2026-59901 | High | netty-codec | 4.1.135.Final | ||
GHSA-r7wm-3cxj-wff9 | High | jackson-core | 2.19.2 | ||
CVE-2026-55831 | High | netty-codec-http | 4.1.135.Final | ||
CVE-2026-55833 | High | netty-codec-http | 4.1.135.Final | ||
CVE-2026-55831 | High | netty-codec-http | 4.1.135.Final | ||
CVE-2026-54512 | High | jackson-databind | 2.19.2 | ||
CVE-2026-56822 | High | netty-handler-ssl-ocsp | 4.1.135.Final | ||
CVE-2026-55833 | High | netty-codec-http | 4.1.135.Final | ||
CVE-2026-56817 | High | netty-codec-xml | 4.1.135.Final | ||
CVE-2026-55851 | High | netty-codec-haproxy | 4.1.135.Final | ||
CVE-2026-59901 | High | netty-codec | 4.1.135.Final | ||
CVE-2026-55833 | High | netty-codec-http | 4.1.135.Final | ||
CVE-2026-55851 | High | netty-codec-haproxy | 4.1.135.Final | ||
CVE-2026-56745 | High | netty-codec-http | 4.1.135.Final | ||
CVE-2026-56740 | High | jline-remote-telnet | 3.9.0 | ||
CVE-2026-56822 | High | netty-handler-ssl-ocsp | 4.1.135.Final | ||
GHSA-r7wm-3cxj-wff9 | High | jackson-core | 2.19.2 | ||
CVE-2026-59901 | High | netty-codec | 4.1.135.Final | ||
CVE-2026-56821 | High | netty-handler-ssl-ocsp | 4.1.135.Final | ||
CVE-2026-54513 | High | jackson-databind | 2.19.2 | ||
CVE-2026-56817 | High | netty-codec-xml | 4.1.135.Final | ||
CVE-2026-56745 | High | netty-codec-http | 4.1.135.Final | ||
CVE-2026-56822 | High | netty-handler-ssl-ocsp | 4.1.135.Final | ||
CVE-2026-55833 | High | netty-codec-http | 4.1.135.Final | ||
CVE-2026-54514 | Medium | jackson-databind | 2.19.2 | ||
CVE-2026-59898 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-59899 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-54515 | Medium | jackson-databind | 2.21.4 | ||
CVE-2026-59900 | Medium | netty-codec-http2 | 4.1.135.Final | ||
CVE-2026-54515 | Medium | jackson-databind | 2.21.4 | ||
CVE-2026-54515 | Medium | jackson-databind | 2.21.4 | ||
CVE-2026-59898 | Medium | netty-codec-http | 4.1.135.Final | ||
GHSA-mhm7-754m-9p8w | Medium | jackson-databind | 2.21.4 | ||
CVE-2026-59899 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-56746 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-59889 | Medium | jackson-databind | 2.21.4 | ||
CVE-2026-58055 | Medium | libnghttp2-14 | 1.69.0-r0 | ||
CVE-2026-59921 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-54515 | Medium | jackson-databind | 2.21.4 | ||
CVE-2026-59919 | Medium | netty-codec-haproxy | 4.1.135.Final | ||
CVE-2026-56746 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-54515 | Medium | jackson-databind | 2.21.4 | ||
CVE-2026-59921 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-56746 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-54515 | Medium | jackson-databind | 2.21.4 | ||
CVE-2026-59900 | Medium | netty-codec-http2 | 4.1.135.Final | ||
CVE-2026-59889 | Medium | jackson-databind | 2.21.4 | ||
CVE-2026-59899 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-59899 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-59900 | Medium | netty-codec-http2 | 4.1.135.Final | ||
CVE-2026-59889 | Medium | jackson-databind | 2.21.4 | ||
CVE-2026-54515 | Medium | jackson-databind | 2.19.2 | ||
CVE-2026-59919 | Medium | netty-codec-haproxy | 4.1.135.Final | ||
CVE-2026-59921 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-59899 | Medium | netty-codec-http | 4.1.135.Final | ||
GHSA-mhm7-754m-9p8w | Medium | jackson-databind | 2.21.4 | ||
CVE-2026-54515 | Medium | jackson-databind | 2.21.4 | ||
CVE-2026-56746 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-59921 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-59899 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-54515 | Medium | jackson-databind | 2.21.4 | ||
CVE-2026-54514 | Medium | jackson-databind | 2.19.2 | ||
CVE-2026-59921 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-56746 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-59921 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-54515 | Medium | jackson-databind | 2.21.4 | ||
CVE-2025-12194 | Medium | bc-fips | 2.1.1 | ||
CVE-2026-59919 | Medium | netty-codec-haproxy | 4.1.135.Final | ||
CVE-2026-59889 | Medium | jackson-databind | 2.21.4 | ||
GHSA-mhm7-754m-9p8w | Medium | jackson-databind | 2.21.4 | ||
CVE-2026-59898 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-59899 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-59889 | Medium | jackson-databind | 2.21.4 | ||
CVE-2026-59888 | Medium | jackson-databind | 2.19.2 | ||
CVE-2026-59898 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-59900 | Medium | netty-codec-http2 | 4.1.135.Final | ||
CVE-2026-56746 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-59889 | Medium | jackson-databind | 2.21.4 | ||
CVE-2026-59899 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-59900 | Medium | netty-codec-http2 | 4.1.135.Final | ||
CVE-2026-54515 | Medium | jackson-databind | 2.19.2 | ||
GHSA-mhm7-754m-9p8w | Medium | jackson-databind | 2.21.4 | ||
CVE-2026-59921 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-59889 | Medium | jackson-databind | 2.21.4 | ||
GHSA-mhm7-754m-9p8w | Medium | jackson-databind | 2.21.4 | ||
CVE-2026-59889 | Medium | jackson-databind | 2.21.4 | ||
CVE-2026-59889 | Medium | jackson-databind | 2.21.4 | ||
GHSA-mhm7-754m-9p8w | Medium | jackson-databind | 2.21.4 | ||
CVE-2026-59921 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-59900 | Medium | netty-codec-http2 | 4.1.135.Final | ||
GHSA-mhm7-754m-9p8w | Medium | jackson-databind | 2.21.4 | ||
CVE-2026-59919 | Medium | netty-codec-haproxy | 4.1.135.Final | ||
CVE-2026-59898 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-59898 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-59900 | Medium | netty-codec-http2 | 4.1.135.Final | ||
CVE-2026-59898 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-59900 | Medium | netty-codec-http2 | 4.1.135.Final | ||
CVE-2026-59888 | Medium | jackson-databind | 2.19.2 | ||
GHSA-mhm7-754m-9p8w | Medium | jackson-databind | 2.21.4 | ||
CVE-2026-59919 | Medium | netty-codec-haproxy | 4.1.135.Final | ||
CVE-2026-59898 | Medium | netty-codec-http | 4.1.135.Final | ||
CVE-2026-56746 | Medium | netty-codec-http | 4.1.135.Final | ||
GHSA-mhm7-754m-9p8w | Medium | jackson-databind | 2.21.4 | ||
CVE-2026-56746 | Medium | netty-codec-http | 4.1.135.Final |