CVE | Origin Package | Affected Images | severity | Exploitability | status | Detected | Last Update |
|---|---|---|---|---|---|---|---|
| CVE-2026-33555 | haproxy-3.2 | - | medium | - | Under review | Jun 30, 2026 | Jun 30, 2026 |
| CVE-2026-33555 | haproxy-2.6 | - | medium | - | Under review | Jun 30, 2026 | Jun 30, 2026 |
| CVE-2026-33555 | haproxy-3.0 | - | medium | - | Under review | Jun 30, 2026 | Jun 30, 2026 |
| CVE-2026-33555 | haproxy-2.8 | - | medium | - | Under review | Jun 30, 2026 | Jun 30, 2026 |
| CVE-2026-44024 | ruby3.4-fluentd-kubernetes-daemonset-1.19 | +1 | unknown | - | Fixed | Jun 27, 2026 | Jun 30, 2026 |
| CVE-2026-44025 | ruby3.4-fluentd-kubernetes-daemonset-1.19 | +1 | unknown | - | Fixed | Jun 27, 2026 | Jun 30, 2026 |
| CVE-2026-44160 | ruby3.4-fluentd-kubernetes-daemonset-1.19 | +1 | unknown | - | Fixed | Jun 27, 2026 | Jun 30, 2026 |
| CVE-2026-44025 | ruby4.0-fluentd-kubernetes-daemonset-1.19 | - | unknown | - | Fixed | Jun 27, 2026 | Jun 30, 2026 |
| CVE-2026-44161 | ruby3.4-fluentd-kubernetes-daemonset-1.19 | +1 | unknown | - | Fixed | Jun 27, 2026 | Jun 30, 2026 |
| CVE-2026-44024 | ruby4.0-fluentd-kubernetes-daemonset-1.19 | - | unknown | - | Fixed | Jun 27, 2026 | Jun 30, 2026 |
| CVE-2026-44160 | ruby4.0-fluentd-kubernetes-daemonset-1.19 | - | unknown | - | Fixed | Jun 27, 2026 | Jun 30, 2026 |
| CVE-2026-44161 | ruby4.0-fluentd-kubernetes-daemonset-1.19 | - | unknown | - | Fixed | Jun 27, 2026 | Jun 30, 2026 |
| CVE-2026-2303 | kubescape-ksserver | - | medium | - | Under review | Jun 30, 2026 | Jun 30, 2026 |
| CVE-2026-39834 | knative-kafka-broker-controller-fips-1.22 | critical | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-39831 | knative-kafka-broker-controller-fips-1.22 | critical | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-39830 | knative-kafka-broker-controller-fips-1.22 | high | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-39832 | knative-kafka-broker-controller-fips-1.22 | high | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-46595 | knative-kafka-broker-controller-fips-1.22 | high | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-39833 | knative-kafka-broker-controller-fips-1.22 | critical | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-42508 | knative-kafka-broker-controller-fips-1.22 | high | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-39831 | knative-kafka-broker-controller-fips-1.21 | critical | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-39821 | knative-kafka-broker-controller-fips-1.22 | high | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-39834 | knative-kafka-broker-controller-fips-1.21 | critical | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-46595 | knative-kafka-broker-controller-fips-1.21 | high | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-39832 | knative-kafka-broker-controller-fips-1.21 | high | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-39830 | knative-kafka-broker-controller-fips-1.21 | high | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-39833 | knative-kafka-broker-controller-fips-1.21 | critical | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-39821 | knative-kafka-broker-controller-fips-1.21 | high | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-42508 | knative-kafka-broker-controller-fips-1.21 | high | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-39834 | knative-kafka-broker-controller-1.22 | critical | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-46595 | knative-kafka-broker-controller-1.22 | high | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-39831 | knative-kafka-broker-controller-1.22 | critical | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-39830 | knative-kafka-broker-controller-1.22 | high | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-39832 | knative-kafka-broker-controller-1.22 | high | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-39821 | knative-kafka-broker-controller-1.22 | high | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-42508 | knative-kafka-broker-controller-1.22 | high | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-39834 | knative-kafka-broker-controller-1.21 | critical | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-39833 | knative-kafka-broker-controller-1.22 | critical | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-46595 | knative-kafka-broker-controller-1.21 | high | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 | |
| CVE-2026-39831 | knative-kafka-broker-controller-1.21 | critical | - | Pending upstream fix | Jun 28, 2026 | Jun 29, 2026 |
This page is currently not available for mobile devices. For the best experience, please visit us from your computer.