CVE | Origin Package | Affected Images | severity | Exploitability | status | Detected | Last Update |
|---|---|---|---|---|---|---|---|
| CVE-2026-42508 | linkerd2-fips-25.11 | - | critical | - | Pending upstream fix | Jun 25, 2026 | Jun 28, 2026 |
| CVE-2026-46595 | linkerd2-fips-25.11 | - | critical | - | Pending upstream fix | Jun 25, 2026 | Jun 28, 2026 |
| CVE-2026-33186 | linkerd2-fips-25.11 | - | critical | - | Pending upstream fix | Jun 25, 2026 | Jun 28, 2026 |
| CVE-2026-39832 | linkerd2-fips-25.11 | - | critical | - | Pending upstream fix | Jun 25, 2026 | Jun 28, 2026 |
| CVE-2026-39834 | linkerd2-fips-25.11 | - | critical | - | Pending upstream fix | Jun 25, 2026 | Jun 28, 2026 |
| CVE-2026-39830 | linkerd2-fips-25.11 | - | critical | - | Pending upstream fix | Jun 25, 2026 | Jun 28, 2026 |
| CVE-2026-39833 | linkerd2-fips-25.11 | - | critical | - | Pending upstream fix | Jun 25, 2026 | Jun 28, 2026 |
| CVE-2026-39821 | linkerd2-fips-25.11 | - | critical | - | Pending upstream fix | Jun 25, 2026 | Jun 28, 2026 |
| CVE-2026-42508 | knative-serving-fips-1.22 | - | critical | - | Unaffected | Jun 24, 2026 | Jun 28, 2026 |
| CVE-2026-33186 | vsphere-csi-syncer-fips-3.5 | - | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 |
| CVE-2026-39831 | knative-serving-fips-1.22 | - | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 |
| CVE-2026-46595 | knative-serving-fips-1.22 | - | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 |
| CVE-2026-39821 | vsphere-csi-syncer-fips-3.5 | - | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 |
| CVE-2026-39834 | knative-serving-fips-1.22 | - | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 |
| CVE-2026-33186 | vsphere-csi-syncer-3.5 | - | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 |
| CVE-2026-39830 | knative-serving-fips-1.22 | - | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 |
| CVE-2026-39821 | vsphere-csi-syncer-3.5 | - | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 |
| CVE-2026-39833 | knative-serving-fips-1.22 | - | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 |
| CVE-2026-39832 | knative-serving-fips-1.22 | - | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 |
| CVE-2026-39821 | knative-serving-fips-1.22 | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 | |
| CVE-2026-39821 | knative-serving-fips-1.21 | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 | |
| CVE-2026-33186 | knative-serving-fips-1.21 | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 | |
| CVE-2026-39821 | knative-serving-1.21 | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 | |
| CVE-2026-46595 | knative-serving-1.22 | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 | |
| CVE-2026-39834 | knative-serving-1.22 | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 | |
| CVE-2026-39830 | knative-serving-1.22 | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 | |
| CVE-2026-39821 | knative-serving-1.22 | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 | |
| CVE-2026-46595 | knative-serving-1.21 | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 | |
| CVE-2026-39831 | knative-serving-1.22 | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 | |
| CVE-2026-42508 | knative-serving-1.22 | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 | |
| CVE-2026-39833 | knative-serving-1.22 | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 | |
| CVE-2026-33186 | knative-serving-1.21 | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 | |
| CVE-2026-39832 | knative-serving-1.22 | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 | |
| CVE-2026-39832 | knative-serving-1.21 | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 | |
| CVE-2026-39833 | knative-serving-1.21 | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 | |
| CVE-2026-39834 | knative-serving-1.21 | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 | |
| CVE-2026-39831 | knative-serving-1.21 | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 | |
| CVE-2026-39830 | knative-serving-1.21 | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 | |
| CVE-2026-42508 | knative-serving-1.21 | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 | |
| CVE-2026-39821 | knative-eventing-1.22 | +7 | critical | - | Pending upstream fix | Jun 24, 2026 | Jun 28, 2026 |
This page is currently not available for mobile devices. For the best experience, please visit us from your computer.