CVE | Origin Package | Affected Images | severity | Exploitability | status | Detected | Last Update |
|---|---|---|---|---|---|---|---|
| CVE-2026-27136 | blob-csi-fips-1.26 | - | medium | - | Fixed | Jun 28, 2026 | Jul 03, 2026 |
| CVE-2026-39832 | blob-csi-1.26 | high | - | Fixed | Jun 28, 2026 | Jul 03, 2026 | |
| CVE-2026-39834 | blob-csi-fips-1.27 | critical | - | Fixed | Jun 28, 2026 | Jul 03, 2026 | |
| CVE-2026-39827 | blob-csi-fips-1.26 | - | medium | - | Fixed | Jun 28, 2026 | Jul 03, 2026 |
| CVE-2026-25680 | blob-csi-fips-1.27 | - | medium | - | Fixed | Jun 28, 2026 | Jul 03, 2026 |
| CVE-2026-39830 | blob-csi-1.26 | high | - | Fixed | Jun 28, 2026 | Jul 03, 2026 | |
| CVE-2026-42506 | blob-csi-1.26 | - | medium | - | Fixed | Jun 28, 2026 | Jul 03, 2026 |
| CVE-2026-39821 | blob-csi-fips-1.27 | high | - | Fixed | Jun 28, 2026 | Jul 03, 2026 | |
| CVE-2026-33814 | blob-csi-fips-1.26 | - | high | - | Fixed | Jun 28, 2026 | Jul 03, 2026 |
| CVE-2026-42508 | blob-csi-1.27 | high | - | Fixed | Jun 28, 2026 | Jul 03, 2026 | |
| CVE-2026-46597 | blob-csi-1.26 | - | high | - | Fixed | Jun 28, 2026 | Jul 03, 2026 |
| CVE-2026-39831 | blob-csi-fips-1.26 | critical | - | Fixed | Jun 28, 2026 | Jul 03, 2026 | |
| CVE-2026-46598 | blob-csi-fips-1.27 | - | medium | - | Fixed | Jun 28, 2026 | Jul 03, 2026 |
| CVE-2026-39830 | blob-csi-1.27 | high | - | Fixed | Jun 28, 2026 | Jul 03, 2026 | |
| CVE-2026-46595 | blob-csi-1.27 | high | - | Fixed | Jun 28, 2026 | Jul 03, 2026 | |
| CVE-2026-39835 | blob-csi-fips-1.26 | - | high | - | Fixed | Jun 28, 2026 | Jul 03, 2026 |
| CVE-2026-39832 | blob-csi-1.27 | high | - | Fixed | Jun 28, 2026 | Jul 03, 2026 | |
| CVE-2026-46595 | blob-csi-fips-1.26 | high | - | Fixed | Jun 28, 2026 | Jul 03, 2026 | |
| CVE-2026-39821 | blob-csi-1.26 | high | - | Fixed | Jun 28, 2026 | Jul 03, 2026 | |
| CVE-2026-33814 | blob-csi-fips-1.27 | - | high | - | Fixed | Jun 28, 2026 | Jul 03, 2026 |
| CVE-2026-42508 | blob-csi-fips-1.27 | high | - | Fixed | Jun 28, 2026 | Jul 03, 2026 | |
| CVE-2026-39827 | blob-csi-1.27 | - | medium | - | Fixed | Jun 28, 2026 | Jul 03, 2026 |
| CVE-2026-46598 | blob-csi-1.27 | - | medium | - | Fixed | Jun 28, 2026 | Jul 03, 2026 |
| CVE-2026-39828 | blob-csi-fips-1.27 | - | high | - | Fixed | Jun 28, 2026 | Jul 03, 2026 |
| CVE-2026-39830 | blob-csi-fips-1.26 | high | - | Fixed | Jun 28, 2026 | Jul 03, 2026 | |
| CVE-2026-39835 | blob-csi-1.26 | - | high | - | Fixed | Jun 28, 2026 | Jul 03, 2026 |
| CVE-2026-46598 | blob-csi-1.26 | - | medium | - | Fixed | Jun 28, 2026 | Jul 03, 2026 |
| CVE-2026-39833 | blob-csi-fips-1.27 | critical | - | Fixed | Jun 28, 2026 | Jul 03, 2026 | |
| CVE-2026-39832 | blob-csi-fips-1.26 | high | - | Fixed | Jun 28, 2026 | Jul 03, 2026 | |
| CVE-2026-39830 | blob-csi-fips-1.27 | high | - | Fixed | Jun 28, 2026 | Jul 03, 2026 | |
| CVE-2026-46598 | blob-csi-fips-1.26 | - | medium | - | Fixed | Jun 28, 2026 | Jul 03, 2026 |
| CVE-2026-9828 | apache-nifi-registry | - | low | - | Fixed | Jul 03, 2026 | Jul 03, 2026 |
| CVE-2026-9828 | apache-nifi | - | low | - | Fixed | Jul 03, 2026 | Jul 03, 2026 |
| CVE-2026-40914 | apache-activemq-artemis | - | medium | - | Fixed | Jul 03, 2026 | Jul 03, 2026 |
| CVE-2022-26945 | paketo-buildpacks-dotnet-publish | - | critical | - | Unaffected | Jul 01, 2026 | Jul 03, 2026 |
| CVE-2022-26945 | paketo-buildpacks-dotnet-execute | - | critical | - | Unaffected | Jul 01, 2026 | Jul 03, 2026 |
| CVE-2022-26945 | paketo-buildpacks-go-dist | - | critical | - | Unaffected | Jul 01, 2026 | Jul 03, 2026 |
| CVE-2022-26945 | paketo-buildpacks-go-mod-vendor | - | critical | - | Unaffected | Jul 01, 2026 | Jul 03, 2026 |
| CVE-2025-14813 | opensearch-2 | +1 | critical | - | Pending upstream fix | Jul 01, 2026 | Jul 03, 2026 |
| CVE-2026-44249 | debezium-connect-3.6 | - | high | - | Under review | Jul 03, 2026 | Jul 03, 2026 |
This page is currently not available for mobile devices. For the best experience, please visit us from your computer.