CVE | Origin Package | Affected Images | severity | Exploitability | status | Detected | Last Update |
|---|---|---|---|---|---|---|---|
| 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-42506 | metacontroller | medium | - | Fixed | Jun 24, 2026 | Jun 30, 2026 | |
| CVE-2026-39824 | metacontroller-fips | low | - | Fixed | Jun 24, 2026 | Jun 30, 2026 | |
| CVE-2026-25681 | metacontroller | medium | - | Fixed | Jun 24, 2026 | Jun 30, 2026 | |
| CVE-2026-25680 | metacontroller | medium | - | Fixed | Jun 24, 2026 | Jun 30, 2026 | |
| CVE-2026-33814 | metacontroller | high | - | Fixed | Jun 24, 2026 | Jun 30, 2026 | |
| CVE-2026-27136 | metacontroller | medium | - | Fixed | Jun 24, 2026 | Jun 30, 2026 | |
| CVE-2026-42502 | metacontroller | medium | - | Fixed | Jun 24, 2026 | Jun 30, 2026 | |
| CVE-2026-25680 | metacontroller-fips | medium | - | Fixed | Jun 24, 2026 | Jun 30, 2026 | |
| CVE-2026-39821 | metacontroller | high | - | Fixed | Jun 24, 2026 | Jun 30, 2026 | |
| CVE-2026-27136 | metacontroller-fips | medium | - | Fixed | Jun 24, 2026 | Jun 30, 2026 | |
| CVE-2026-33814 | metacontroller-fips | high | - | Fixed | Jun 24, 2026 | Jun 30, 2026 | |
| CVE-2026-25681 | metacontroller-fips | medium | - | Fixed | Jun 24, 2026 | Jun 30, 2026 | |
| CVE-2026-42506 | metacontroller-fips | medium | - | Fixed | Jun 24, 2026 | Jun 30, 2026 | |
| CVE-2026-42502 | metacontroller-fips | medium | - | Fixed | Jun 24, 2026 | Jun 30, 2026 | |
| CVE-2026-39821 | metacontroller-fips | high | - | Fixed | Jun 24, 2026 | Jun 30, 2026 | |
| GHSA-vxr8-fq34-vvx9 | grist | +1 | low | - | Fixed | Jun 21, 2026 | Jun 30, 2026 |
| CVE-2026-24842 | grist | +1 | high | - | Fixed | Jun 21, 2026 | Jun 30, 2026 |
| GHSA-gvmj-g25r-r7wr | grist | +1 | low | - | Fixed | Jun 21, 2026 | Jun 30, 2026 |
| GHSA-x4vx-rjvf-j5p4 | grist | +1 | low | - | Fixed | Jun 21, 2026 | Jun 30, 2026 |
| GHSA-cmwh-pvxp-8882 | grist | +1 | medium | - | Fixed | Jun 21, 2026 | Jun 30, 2026 |
| CVE-2026-49458 | grist | +1 | unknown | - | Fixed | Jun 21, 2026 | Jun 30, 2026 |
| CVE-2026-23745 | grist | +1 | high | - | Fixed | Jun 21, 2026 | Jun 30, 2026 |
| CVE-2026-49978 | grist | +1 | unknown | - | Fixed | Jun 21, 2026 | Jun 30, 2026 |
| CVE-2026-55388 | grist | +1 | high | - | Fixed | Jun 21, 2026 | Jun 30, 2026 |
| CVE-2026-23950 | grist | +1 | medium | - | Fixed | Jun 21, 2026 | Jun 30, 2026 |
| CVE-2026-53655 | grist | +1 | medium | - | Fixed | Jun 21, 2026 | Jun 30, 2026 |
| CVE-2026-49459 | grist | +1 | unknown | - | Fixed | Jun 21, 2026 | Jun 30, 2026 |
| CVE-2026-49982 | grist | +1 | high | - | Fixed | Jun 21, 2026 | Jun 30, 2026 |
| CVE-2026-29786 | grist | +1 | high | - | Fixed | Jun 21, 2026 | Jun 30, 2026 |
| GHSA-9ggv-8w38-r7pm | grist | +1 | medium | - | Fixed | Jun 21, 2026 | Jun 30, 2026 |
| GHSA-76mc-f452-cxcm | grist | +1 | medium | - | Fixed | Jun 21, 2026 | Jun 30, 2026 |
| CVE-2026-26960 | grist | +1 | high | - | Fixed | Jun 21, 2026 | Jun 30, 2026 |
This page is currently not available for mobile devices. For the best experience, please visit us from your computer.