New vulnerabilities
Detected in the last 7 days Critical
Detected in the last 12 months10738 advisories
CVE | Origin Package | Affected Images | severity | Exploitability | status | Detected | Last Update |
|---|---|---|---|---|---|---|---|
| CVE-2022-26945 | cloudbeat-8.19 | - | critical | - | Unaffected | Jul 01, 2026 | Jul 03, 2026 |
| CVE-2026-42508 | cloud-query-db-0.12-fips | - | high | - | Pending upstream fix | Jul 01, 2026 | Jul 03, 2026 |
| CVE-2026-39832 | cloud-query-db-0.12-fips | - | high | - | Pending upstream fix | Jul 01, 2026 | Jul 03, 2026 |
| CVE-2026-39833 | cloud-query-db-0.12-fips | - | critical | - | Pending upstream fix | Jul 01, 2026 | Jul 03, 2026 |
| CVE-2026-39821 | cloud-query-db-0.12-fips | - | high | - | Pending upstream fix | Jul 01, 2026 | Jul 03, 2026 |
| CVE-2022-26945 | cloud-query-db-0.12 | - | critical | - | Unaffected | Jul 01, 2026 | Jul 03, 2026 |
| CVE-2026-39834 | cluster-api-fips-1.11 |  cluster-api-clusterctl-fips+2 | critical | - | Pending upstream fix | Jun 27, 2026 | Jul 03, 2026 |
| CVE-2026-39834 | cluster-api-fips-1.13 | cluster-api-clusterctl-fips +2 | critical | - | Pending upstream fix | Jun 27, 2026 | Jul 03, 2026 |
| CVE-2026-39831 | cluster-api-fips-1.13 | cluster-api-clusterctl-fips +2 | critical | - | Pending upstream fix | Jun 27, 2026 | Jul 03, 2026 |
| CVE-2026-39830 | cluster-api-fips-1.13 | cluster-api-clusterctl-fips +2 | high | - | Pending upstream fix | Jun 27, 2026 | Jul 03, 2026 |
| CVE-2026-46595 | cluster-api-fips-1.13 | cluster-api-clusterctl-fips +2 | high | - | Pending upstream fix | Jun 27, 2026 | Jul 03, 2026 |
| CVE-2026-39821 | knative-serving-fips-1.21 |  knative-serving-activator-fips+7 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 03, 2026 |
| CVE-2026-39821 | kubevirt-1.8-fips |  kubevirt-virt-api-fips+5 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 03, 2026 |
| CVE-2026-33186 | knative-serving-fips-1.21 | knative-serving-activator-fips +7 | critical | - | Pending upstream fix | Jun 24, 2026 | Jul 03, 2026 |
| CVE-2026-39821 | knative-serving-fips-1.22 | knative-serving-activator-fips +7 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 03, 2026 |
| CVE-2026-39821 | knative-serving-1.22 |  knative-serving-activator+7 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 03, 2026 |
| CVE-2026-46595 | knative-eventing-1.22 |  knative-eventing-channel-controller+7 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 03, 2026 |
| CVE-2026-39832 | knative-eventing-1.22 | knative-eventing-channel-controller +7 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 03, 2026 |
| CVE-2026-39833 | knative-eventing-1.22 | knative-eventing-channel-controller +7 | critical | - | Pending upstream fix | Jun 24, 2026 | Jul 03, 2026 |
| CVE-2026-42508 | knative-eventing-1.22 | knative-eventing-channel-controller +7 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 03, 2026 |
| CVE-2026-39834 | knative-eventing-1.22 | knative-eventing-channel-controller +7 | critical | - | Pending upstream fix | Jun 24, 2026 | Jul 03, 2026 |
| CVE-2026-39830 | knative-eventing-1.22 | knative-eventing-channel-controller +7 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 03, 2026 |
| CVE-2026-39832 | gitlab-runner-fips-19.1 |  gitlab-runner-fips+1 | high | - | Pending upstream fix | Jun 22, 2026 | Jul 03, 2026 |
| CVE-2026-39821 | knative-eventing-1.22 | knative-eventing-channel-controller +7 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 03, 2026 |
| CVE-2026-46595 | gitlab-runner-19.1 |  gitlab-runner+3 | high | - | Pending upstream fix | Jun 22, 2026 | Jul 03, 2026 |
| CVE-2026-42508 | gitlab-runner-19.1 | gitlab-runner +3 | high | - | Pending upstream fix | Jun 22, 2026 | Jul 03, 2026 |
| CVE-2026-39830 | gitlab-runner-19.1 | gitlab-runner +3 | high | - | Pending upstream fix | Jun 22, 2026 | Jul 03, 2026 |
| CVE-2026-39834 | gitlab-runner-19.1 | gitlab-runner +3 | critical | - | Pending upstream fix | Jun 22, 2026 | Jul 03, 2026 |
| CVE-2026-39831 | gitlab-runner-19.1 | gitlab-runner +3 | critical | - | Pending upstream fix | Jun 22, 2026 | Jul 03, 2026 |
| CVE-2026-39833 | gitlab-runner-19.1 | gitlab-runner +3 | critical | - | Pending upstream fix | Jun 22, 2026 | Jul 03, 2026 |
| CVE-2026-39821 | gitlab-runner-19.1 | gitlab-runner +3 | high | - | Pending upstream fix | Jun 22, 2026 | Jul 03, 2026 |
| CVE-2026-39832 | gitlab-runner-19.1 | gitlab-runner +3 | high | - | Pending upstream fix | Jun 22, 2026 | Jul 03, 2026 |
| CVE-2026-42508 | cluster-api-fips-1.11 | cluster-api-clusterctl-fips +2 | high | - | Pending upstream fix | Jun 25, 2026 | Jul 03, 2026 |
| CVE-2026-39832 | cluster-api-fips-1.11 | cluster-api-clusterctl-fips +2 | high | - | Pending upstream fix | Jun 25, 2026 | Jul 03, 2026 |
| CVE-2026-39833 | cluster-api-fips-1.13 | cluster-api-clusterctl-fips +2 | critical | - | Pending upstream fix | Jun 25, 2026 | Jul 03, 2026 |
| CVE-2026-42508 | cluster-api-fips-1.13 | cluster-api-clusterctl-fips +2 | high | - | Pending upstream fix | Jun 25, 2026 | Jul 03, 2026 |
| CVE-2026-39832 | cluster-api-fips-1.13 | cluster-api-clusterctl-fips +2 | high | - | Pending upstream fix | Jun 25, 2026 | Jul 03, 2026 |
| CVE-2026-50151 | tw | - | unknown | - | Fixed | Jul 02, 2026 | Jul 03, 2026 |
| CVE-2026-48978 | tw | - | unknown | - | Fixed | Jul 02, 2026 | Jul 03, 2026 |
| CVE-2026-50162 | tw | - | unknown | - | Fixed | Jul 02, 2026 | Jul 03, 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.