New vulnerabilities
Detected in the last 7 days Critical
Detected in the last 12 months7713 advisories
CVE | Origin Package | Affected Images | severity | Exploitability | status | Detected | Last Update |
|---|---|---|---|---|---|---|---|
| CVE-2019-16869 | apache-druid | - | high | - | Under review | Jun 30, 2026 | Jun 30, 2026 |
| CVE-2019-16869 | apache-druid-fips | - | high | - | Under review | Jun 30, 2026 | Jun 30, 2026 |
| 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 |  fluentd-kubernetes-daemonset+1 | unknown | - | Fixed | Jun 27, 2026 | Jun 30, 2026 |
| CVE-2026-44025 | ruby3.4-fluentd-kubernetes-daemonset-1.19 | fluentd-kubernetes-daemonset +1 | unknown | - | Fixed | Jun 27, 2026 | Jun 30, 2026 |
| CVE-2026-44160 | ruby3.4-fluentd-kubernetes-daemonset-1.19 | fluentd-kubernetes-daemonset +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 | fluentd-kubernetes-daemonset +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 |
| GHSA-98x5-vq43-vc5p | litellm-1.84 | - | critical | - | Unaffected | Jun 27, 2026 | Jun 29, 2026 |
| CVE-2026-44024 | ruby4.0-fluentd-kubernetes-daemonset-1.16 | - | unknown | - | Pending upstream fix | Jun 27, 2026 | Jun 29, 2026 |
| CVE-2026-44024 | ruby3.4-fluentd-kubernetes-daemonset-1.18 | fluentd-kubernetes-daemonset +1 | unknown | - | Pending upstream fix | Jun 27, 2026 | Jun 29, 2026 |
| CVE-2026-44024 | ruby4.0-fluentd-kubernetes-daemonset-1.18 | - | unknown | - | Pending upstream fix | Jun 27, 2026 | Jun 29, 2026 |
| CVE-2026-44024 | ruby3.4-fluentd-kubernetes-daemonset-1.16 | fluentd-kubernetes-daemonset +1 | unknown | - | Pending upstream fix | Jun 27, 2026 | Jun 29, 2026 |
| CVE-2026-44024 | ruby3.3-fluentd-kubernetes-daemonset-1.18 | fluentd-kubernetes-daemonset +1 | unknown | - | Pending upstream fix | Jun 27, 2026 | Jun 29, 2026 |
| GHSA-98x5-vq43-vc5p | litellm-1.85 | - | critical | - | Unaffected | Jun 27, 2026 | Jun 29, 2026 |
| GHSA-98x5-vq43-vc5p | litellm-1.88 | - | critical | - | Unaffected | Jun 27, 2026 | Jun 29, 2026 |
| GHSA-98x5-vq43-vc5p | litellm-1.86 | - | critical | - | Unaffected | Jun 27, 2026 | Jun 29, 2026 |
| CVE-2026-44024 | ruby3.3-fluentd-kubernetes-daemonset-1.16 | fluentd-kubernetes-daemonset +1 | unknown | - | Pending upstream fix | Jun 27, 2026 | Jun 29, 2026 |
| CVE-2026-44024 | ruby3.2-fluentd-1.18 |  fluentd+1 | unknown | - | Pending upstream fix | Jun 27, 2026 | Jun 29, 2026 |
| CVE-2026-44024 | ruby3.2-fluentd-kubernetes-daemonset-1.16 | fluentd-kubernetes-daemonset +1 | unknown | - | Pending upstream fix | Jun 27, 2026 | Jun 29, 2026 |
| CVE-2026-44024 | ruby3.2-fluentd-kubernetes-daemonset-1.18 | fluentd-kubernetes-daemonset +1 | unknown | - | Pending upstream fix | Jun 27, 2026 | Jun 29, 2026 |
| GHSA-98x5-vq43-vc5p | litellm-1.82 | - | critical | - | Unaffected | Jun 27, 2026 | Jun 29, 2026 |
| GHSA-98x5-vq43-vc5p | litellm-1.81 | - | critical | - | Unaffected | Jun 27, 2026 | Jun 29, 2026 |
| CVE-2026-55200 | libssh2 |  postgresql-repmgr-advanced+1 | critical | - | Pending upstream fix | Jun 27, 2026 | Jun 29, 2026 |
| CVE-2026-46595 | cluster-api-fips-1.11 |  cluster-api-clusterctl-fips+2 | high | - | Pending upstream fix | Jun 27, 2026 | Jun 29, 2026 |
| CVE-2026-39831 | cluster-api-fips-1.11 | cluster-api-clusterctl-fips +2 | critical | - | Pending upstream fix | Jun 27, 2026 | Jun 29, 2026 |
| CVE-2026-39830 | cluster-api-fips-1.11 | cluster-api-clusterctl-fips +2 | high | - | Pending upstream fix | Jun 27, 2026 | Jun 29, 2026 |
| CVE-2026-48713 | cal.diy-6.2 | - | critical | - | Pending upstream fix | Jun 26, 2026 | Jun 29, 2026 |
| CVE-2026-48714 | grist |  grist+1 | critical | - | Pending upstream fix | Jun 26, 2026 | Jun 29, 2026 |
| CVE-2026-48713 | cal.diy-6.1 | - | critical | - | Pending upstream fix | Jun 26, 2026 | Jun 29, 2026 |
| CVE-2026-33186 | knative-net-kourier-1.21 |  knative-net-kourier | critical | - | Pending upstream fix | Jun 25, 2026 | Jun 29, 2026 |
| CVE-2026-39821 | knative-net-kourier-1.21 | knative-net-kourier | high | - | Pending upstream fix | Jun 25, 2026 | Jun 29, 2026 |
| CVE-2026-33186 | cluster-api-ipam-provider-in-cluster-fips |  cluster-api-ipam-provider-in-cluster-fips | critical | - | Pending upstream fix | Jun 25, 2026 | Jun 29, 2026 |
This page is available on desktop
This page is currently not available for mobile devices. For the best experience, please visit us from your computer.