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-6100 | Critical | python-3.13 | 3.13.14-r0 | ||
CVE-2026-8376 | Critical | perl | 5.42.2-r3 | ||
CVE-2026-5450 | Critical | glibc | 2.43-r8 | ||
CVE-2026-48712 | High | protobufjs | 8.2.0 | ||
CVE-2026-48712 | High | protobufjs | 8.2.0 | ||
CVE-2026-9669 | High | python-3.13 | 3.13.14-r0 | ||
GHSA-p6gq-j5cr-w38f | High | nodemailer | 8.0.11 | ||
CVE-2026-48712 | High | protobufjs | 8.2.0 | ||
CVE-2026-0861 | High | glibc | 2.43-r8 | ||
CVE-2026-5928 | High | glibc | 2.43-r8 | ||
CVE-2026-48712 | High | protobufjs | 8.2.0 | ||
CVE-2026-12151 | High | undici | 6.26.0 | ||
CVE-2026-3298 | High | python-3.13 | 3.13.14-r0 | ||
CVE-2026-4046 | High | glibc | 2.43-r8 | ||
CVE-2026-48712 | High | protobufjs | 8.2.0 | ||
CVE-2026-12151 | High | undici | 6.26.0 | ||
CVE-2026-48712 | High | protobufjs | 8.2.0 | ||
CVE-2026-48712 | High | protobufjs | 8.2.0 | ||
CVE-2026-48712 | High | protobufjs | 8.2.0 | ||
CVE-2026-4786 | High | python-3.13 | 3.13.14-r0 | ||
CVE-2026-5435 | High | glibc | 2.43-r8 | ||
CVE-2026-48712 | High | protobufjs | 8.2.0 | ||
CVE-2026-48712 | High | protobufjs | 7.5.8 | ||
CVE-2026-48712 | High | protobufjs | 8.2.0 | ||
CVE-2026-4437 | High | glibc | 2.43-r8 | ||
CVE-2026-54285 | Medium | @opentelemetry/core | 2.7.1 | ||
CVE-2026-49458 | Medium | dompurify | 3.4.0 | ||
CVE-2026-49459 | Medium | dompurify | 3.4.0 | ||
CVE-2026-54269 | Medium | protobufjs | 8.2.0 | ||
CVE-2026-54269 | Medium | protobufjs | 8.2.0 | ||
CVE-2026-54285 | Medium | @opentelemetry/core | 2.7.1 | ||
CVE-2026-4438 | Medium | glibc | 2.43-r8 | ||
CVE-2026-54285 | Medium | @opentelemetry/core | 2.7.1 | ||
CVE-2026-54285 | Medium | @opentelemetry/core | 2.7.1 | ||
CVE-2026-54269 | Medium | protobufjs | 8.2.0 | ||
CVE-2026-54285 | Medium | @opentelemetry/core | 2.7.1 | ||
CVE-2026-54285 | Medium | @opentelemetry/core | 2.7.1 | ||
CVE-2026-54270 | Medium | protobufjs | 8.2.0 | ||
CVE-2026-54285 | Medium | @opentelemetry/core | 2.7.1 | ||
CVE-2026-1502 | Medium | python-3.13 | 3.13.14-r0 | ||
CVE-2026-12003 | Medium | python-3.13 | 3.13.14-r0 | ||
CVE-2026-54285 | Medium | @opentelemetry/core | 2.7.1 | ||
CVE-2026-54285 | Medium | @opentelemetry/core | 2.7.1 | ||
CVE-2026-54269 | Medium | protobufjs | 8.2.0 | ||
CVE-2026-54285 | Medium | @opentelemetry/core | 2.7.1 | ||
CVE-2026-54285 | Medium | @opentelemetry/core | 2.7.1 | ||
CVE-2026-54270 | Medium | protobufjs | 8.2.0 | ||
CVE-2026-41907 | Medium | uuid | 10.0.0 | ||
CVE-2026-54285 | Medium | @opentelemetry/core | 2.7.1 | ||
CVE-2026-54285 | Medium | @opentelemetry/core | 2.7.1 | ||
CVE-2026-54269 | Medium | protobufjs | 8.2.0 | ||
CVE-2026-54270 | Medium | protobufjs | 8.2.0 | ||
CVE-2026-54285 | Medium | @opentelemetry/core | 2.7.1 | ||
CVE-2026-54285 | Medium | @opentelemetry/core | 2.7.1 | ||
CVE-2026-54270 | Medium | protobufjs | 8.2.0 | ||
CVE-2026-9679 | Medium | undici | 6.26.0 | ||
CVE-2026-54270 | Medium | protobufjs | 8.2.0 | ||
CVE-2026-54269 | Medium | protobufjs | 8.2.0 | ||
CVE-2026-54285 | Medium | @opentelemetry/core | 2.7.1 | ||
CVE-2026-41907 | Medium | uuid | 9.0.1 | ||
CVE-2026-6238 | Medium | glibc | 2.43-r8 | ||
CVE-2026-54269 | Medium | protobufjs | 8.2.0 | ||
CVE-2025-15367 | Medium | python-3.13 | 3.13.14-r0 | ||
CVE-2026-54285 | Medium | @opentelemetry/core | 2.7.1 | ||
CVE-2026-54285 | Medium | @opentelemetry/core | 2.7.1 | ||
CVE-2026-54285 | Medium | @opentelemetry/core | 2.7.1 | ||
GHSA-cmwh-pvxp-8882 | Medium | dompurify | 3.4.0 | ||
CVE-2026-54270 | Medium | protobufjs | 8.2.0 | ||
CVE-2026-54269 | Medium | protobufjs | 8.2.0 | ||
CVE-2026-54285 | Medium | @opentelemetry/core | 2.2.0 | ||
CVE-2026-54285 | Medium | @opentelemetry/core | 2.7.1 | ||
CVE-2026-54285 | Medium | @opentelemetry/core | 2.7.1 | ||
CVE-2026-54269 | Medium | protobufjs | 8.2.0 | ||
CVE-2025-15366 | Medium | python-3.13 | 3.13.14-r0 | ||
CVE-2026-54285 | Medium | @opentelemetry/core | 2.7.1 | ||
CVE-2026-49978 | Medium | dompurify | 3.4.0 | ||
CVE-2026-54269 | Medium | protobufjs | 7.5.8 | ||
CVE-2026-54270 | Medium | protobufjs | 8.2.0 | ||
CVE-2026-54270 | Medium | protobufjs | 8.2.0 | ||
CVE-2026-54270 | Medium | protobufjs | 8.2.0 | ||
CVE-2026-9679 | Medium | undici | 6.26.0 | ||
CVE-2026-6019 | Medium | python-3.13 | 3.13.14-r0 | ||
GHSA-76mc-f452-cxcm | Medium | dompurify | 3.4.0 | ||
CVE-2026-54270 | Medium | protobufjs | 8.2.0 | ||
CVE-2026-54269 | Medium | protobufjs | 8.2.0 | ||
CVE-2026-54285 | Medium | @opentelemetry/core | 2.7.1 | ||
CVE-2026-53655 | Medium | tar | 7.5.11 | ||
GHSA-vxr8-fq34-vvx9 | Low | dompurify | 3.4.0 | ||
GHSA-x4vx-rjvf-j5p4 | Low | dompurify | 3.4.0 | ||
CVE-2026-11525 | Low | undici | 6.26.0 | ||
CVE-2026-6733 | Low | undici | 6.26.0 | ||
GHSA-gvmj-g25r-r7wr | Low | dompurify | 3.4.0 | ||
CVE-2026-11525 | Low | undici | 6.26.0 | ||
CVE-2026-6733 | Low | undici | 6.26.0 |