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-42584 | High | netty-codec-http | 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-42587 | High | netty-codec-http2 | 4.1.132.Final | ||
CVE-2026-42584 | High | netty-codec-http | 4.1.132.Final | ||
CVE-2026-42587 | High | netty-codec-http | 4.1.132.Final | ||
CVE-2026-42587 | High | netty-codec-http2 | 4.1.132.Final | ||
CVE-2026-42579 | High | netty-codec-dns | 4.1.132.Final | ||
CVE-2026-42584 | High | netty-codec-http | 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-42587 | High | netty-codec-http | 4.1.132.Final | ||
CVE-2026-42587 | High | netty-codec-http2 | 4.1.132.Final | ||
CVE-2026-42583 | High | netty-codec | 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-42583 | High | netty-codec | 4.1.132.Final | ||
CVE-2026-42579 | High | netty-codec-dns | 4.1.132.Final | ||
CVE-2026-42584 | High | netty-codec-http | 4.1.132.Final | ||
CVE-2026-42583 | High | netty-codec | 4.1.132.Final | ||
CVE-2026-42584 | High | netty-codec-http | 4.1.132.Final | ||
CVE-2026-42587 | High | netty-codec-http | 4.1.132.Final | ||
CVE-2026-42587 | High | netty-codec-http2 | 4.1.132.Final | ||
CVE-2026-42583 | High | netty-codec | 4.1.132.Final | ||
CVE-2026-41417 | Medium | netty-codec-http | 4.1.132.Final | ||
GHSA-72hv-8253-57qq | Medium | jackson-core | 2.19.2 | ||
CVE-2026-42580 | 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-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-34480 | Medium | log4j-core | 2.25.3 | ||
CVE-2025-12194 | Medium | bc-fips | 2.1.1 | ||
CVE-2026-42580 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-42580 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-34477 | Medium | log4j-core | 2.25.3 | ||
CVE-2025-22227 | Medium | reactor-netty-http | 1.0.45 | ||
CVE-2026-42580 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-42581 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-41417 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-42585 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-42585 | 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-42581 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-34478 | Medium | log4j-core | 2.25.3 | ||
CVE-2026-41417 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-41417 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-41417 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-42585 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-42580 | Medium | netty-codec-http | 4.1.132.Final | ||
GHSA-72hv-8253-57qq | Medium | jackson-core | 2.19.2 | ||
CVE-2026-42581 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2025-48924 | Medium | commons-lang3 | 3.14.0 | ||
CVE-2026-42585 | Medium | netty-codec-http | 4.1.132.Final | ||
CVE-2026-42578 | Low | netty-handler-proxy | 4.1.132.Final | ||
CVE-2026-42578 | Low | netty-handler-proxy | 4.1.132.Final | ||
CVE-2026-42578 | Low | netty-handler-proxy | 4.1.132.Final | ||
CVE-2026-42578 | Low | netty-handler-proxy | 4.1.132.Final |