CVE | Origin Package | Affected Images | severity | Exploitability | status | Detected | Last Update |
|---|---|---|---|---|---|---|---|
| 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-39834 | linkerd2-2.19 | - | critical | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39831 | linkerd2-26.5 | - | critical | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39828 | linkerd2-fips-2.19 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39835 | linkerd2-fips-26.5 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39830 | linkerd2-fips-2.19 | - | critical | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39830 | linkerd2-2.19 | - | critical | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39834 | linkerd2-26.5 | - | critical | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39828 | linkerd2-26.5 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-46595 | linkerd2-26.5 | - | critical | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-46595 | linkerd2-25.11 | - | critical | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39827 | linkerd2-fips-2.19 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39829 | linkerd2-26.5 | - | high | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39828 | linkerd2-25.11 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39834 | linkerd2-fips-2.19 | - | critical | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39824 | linkerd2-26.5 | - | low | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39827 | linkerd2-25.11 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-46597 | linkerd2-fips-2.19 | - | high | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39830 | linkerd2-26.5 | - | critical | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-46597 | linkerd2-25.11 | - | high | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39824 | linkerd2-25.11 | - | low | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39824 | linkerd2-2.19 | - | low | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39829 | linkerd2-2.19 | - | high | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39827 | linkerd2-26.5 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39828 | linkerd2-fips-26.5 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39835 | linkerd2-2.19 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39835 | linkerd2-fips-2.19 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39835 | linkerd2-26.5 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39831 | linkerd2-fips-26.5 | - | critical | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-46595 | linkerd2-fips-2.19 | - | critical | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39828 | linkerd2-2.19 | - | medium | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-46595 | linkerd2-2.19 | - | critical | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39831 | linkerd2-2.19 | - | critical | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-46597 | linkerd2-fips-26.5 | - | high | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39829 | linkerd2-fips-2.19 | - | high | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
| CVE-2026-39831 | linkerd2-25.11 | - | critical | - | Fixed | Jun 25, 2026 | Jun 27, 2026 |
This page is currently not available for mobile devices. For the best experience, please visit us from your computer.