CVE | Origin Package | Affected Images | severity | Exploitability | status | Detected | Last Update |
|---|---|---|---|---|---|---|---|
| CVE-2026-48930 | nodejs-24 | +17 | critical | - | Fixed | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-48618 | nodejs-22 | +11 | medium | - | Fixed | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-48933 | nodejs-24 | +17 | high | - | Fixed | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-48928 | nodejs-26 | +2 | medium | - | Fixed | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-48936 | nodejs-26 | +2 | low | - | Fixed | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-48935 | nodejs-22 | +11 | low | - | Fixed | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-48935 | nodejs-26 | +2 | low | - | Fixed | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-48928 | nodejs-24 | +17 | medium | - | Fixed | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-48619 | nodejs-22 | +11 | high | - | Fixed | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-48928 | nodejs-22 | +11 | medium | - | Fixed | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-48934 | nodejs-26 | +2 | medium | - | Fixed | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-48615 | nodejs-22 | +11 | high | - | Fixed | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-48930 | nodejs-26 | +2 | critical | - | Fixed | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-48935 | nodejs-24 | +17 | low | - | Fixed | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-48619 | nodejs-24 | +17 | high | - | Fixed | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-48758 | litellm-1.83 | unknown | - | Fixed | Jun 27, 2026 | Jun 27, 2026 | |
| CVE-2026-25680 | knative-net-istio-1.22 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39824 | knative-net-istio-fips-1.21 | - | low | - | Fixed | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-25681 | knative-net-kourier-fips-1.21 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-25681 | knative-net-istio-1.22 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-27136 | knative-net-kourier-fips-1.21 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-25680 | knative-net-kourier-fips-1.21 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39824 | knative-net-istio-fips-1.22 | - | low | - | Fixed | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-42502 | knative-net-istio-1.22 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-33814 | knative-net-kourier-fips-1.21 | - | high | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39821 | knative-net-kourier-fips-1.21 | - | high | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-33186 | knative-net-kourier-fips-1.21 | - | critical | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-42506 | knative-net-kourier-fips-1.21 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-25680 | knative-net-istio-fips-1.22 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-27136 | knative-net-istio-fips-1.22 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-42506 | knative-net-istio-fips-1.22 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39821 | knative-net-istio-1.22 | - | high | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-42506 | knative-net-istio-1.22 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39821 | knative-net-istio-fips-1.22 | - | high | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39824 | knative-net-istio-1.22 | - | low | - | Fixed | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-42502 | knative-net-kourier-fips-1.21 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39824 | knative-net-kourier-fips-1.21 | - | low | - | Fixed | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-27136 | knative-net-istio-1.22 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-42502 | knative-net-istio-fips-1.22 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39824 | knative-net-istio-1.21 | - | low | - | Fixed | Jun 27, 2026 | Jun 27, 2026 |
This page is currently not available for mobile devices. For the best experience, please visit us from your computer.