CVE | Origin Package | Affected Images | severity | Exploitability | status | Detected | Last Update |
|---|---|---|---|---|---|---|---|
| CVE-2026-42579 | apicurio-registry-fips | - | critical | - | Pending upstream fix | Jun 23, 2026 | Jul 02, 2026 |
| CVE-2026-42198 | apicurio-registry-fips | - | high | - | Pending upstream fix | Jun 23, 2026 | Jul 02, 2026 |
| CVE-2026-42583 | apicurio-registry-fips | - | high | - | Pending upstream fix | Jun 23, 2026 | Jul 02, 2026 |
| CVE-2026-29062 | apicurio-registry-fips | - | high | - | Pending upstream fix | Jun 23, 2026 | Jul 02, 2026 |
| CVE-2026-42587 | apicurio-registry-fips | - | high | - | Pending upstream fix | Jun 23, 2026 | Jul 02, 2026 |
| GHSA-2m67-wjpj-xhg9 | apicurio-registry-fips | - | high | - | Pending upstream fix | Jun 23, 2026 | Jul 02, 2026 |
| CVE-2026-47691 | apicurio-registry-fips | - | critical | - | Pending upstream fix | Jun 23, 2026 | Jul 02, 2026 |
| CVE-2026-44893 | apicurio-registry-fips | - | high | - | Pending upstream fix | Jun 23, 2026 | Jul 02, 2026 |
| CVE-2026-44249 | apicurio-registry-fips | - | high | - | Pending upstream fix | Jun 23, 2026 | Jul 02, 2026 |
| CVE-2026-50010 | apicurio-registry-fips | - | high | - | Pending upstream fix | Jun 23, 2026 | Jul 02, 2026 |
| CVE-2026-45674 | apicurio-registry-fips | - | critical | - | Pending upstream fix | Jun 23, 2026 | Jul 02, 2026 |
| CVE-2026-42584 | apicurio-registry-fips | - | critical | - | Pending upstream fix | Jun 23, 2026 | Jul 02, 2026 |
| CVE-2026-48526 | apache-superset-6.1 | - | high | - | Pending upstream fix | Jun 23, 2026 | Jul 02, 2026 |
| CVE-2026-41178 | cluster-autoscaler-fips-1.33 | - | medium | - | Fix not planned | Jul 01, 2026 | Jul 02, 2026 |
| CVE-2026-39882 | cluster-autoscaler-fips-1.33 | - | medium | - | Fix not planned | Jul 01, 2026 | Jul 02, 2026 |
| CVE-2026-24049 | apache-superset-6.1 | - | medium | - | Unaffected | Jun 23, 2026 | Jul 02, 2026 |
| CVE-2026-25087 | apache-superset-6.1 | - | high | - | Unaffected | Jun 23, 2026 | Jul 02, 2026 |
| CVE-2026-23949 | apache-superset-6.1 | high | - | Pending upstream fix | Jun 23, 2026 | Jul 02, 2026 | |
| CVE-2026-41205 | apache-superset-6.1 | high | - | Pending upstream fix | Jun 23, 2026 | Jul 02, 2026 | |
| GHSA-537c-gmf6-5ccf | apache-superset-6.1 | high | - | Pending upstream fix | Jun 23, 2026 | Jul 02, 2026 | |
| CVE-2026-14095 | chromium | - | critical | - | Fixed | Jul 02, 2026 | Jul 02, 2026 |
| CVE-2026-14093 | chromium | - | critical | - | Fixed | Jul 02, 2026 | Jul 02, 2026 |
| CVE-2026-14071 | chromium | - | medium | - | Fixed | Jul 02, 2026 | Jul 02, 2026 |
| CVE-2026-14061 | chromium | - | medium | - | Fixed | Jul 02, 2026 | Jul 02, 2026 |
| CVE-2026-14148 | chromium | - | medium | - | Fixed | Jul 02, 2026 | Jul 02, 2026 |
| CVE-2026-13877 | chromium | - | medium | - | Fixed | Jul 02, 2026 | Jul 02, 2026 |
| CVE-2026-13873 | chromium | - | medium | - | Fixed | Jul 02, 2026 | Jul 02, 2026 |
| CVE-2026-14063 | chromium | - | medium | - | Fixed | Jul 02, 2026 | Jul 02, 2026 |
| CVE-2026-13881 | chromium | - | medium | - | Fixed | Jul 02, 2026 | Jul 02, 2026 |
| CVE-2026-14154 | chromium | - | medium | - | Fixed | Jul 02, 2026 | Jul 02, 2026 |
| CVE-2026-13777 | chromium | - | high | - | Fixed | Jul 02, 2026 | Jul 02, 2026 |
| CVE-2026-13824 | chromium | - | high | - | Fixed | Jul 02, 2026 | Jul 02, 2026 |
| CVE-2026-14108 | chromium | - | high | - | Fixed | Jul 02, 2026 | Jul 02, 2026 |
| CVE-2026-13801 | chromium | - | high | - | Fixed | Jul 02, 2026 | Jul 02, 2026 |
| CVE-2026-14049 | chromium | - | medium | - | Fixed | Jul 02, 2026 | Jul 02, 2026 |
| CVE-2026-13827 | chromium | - | high | - | Fixed | Jul 02, 2026 | Jul 02, 2026 |
| CVE-2026-13975 | chromium | - | medium | - | Fixed | Jul 02, 2026 | Jul 02, 2026 |
| CVE-2026-13992 | chromium | - | medium | - | Fixed | Jul 02, 2026 | Jul 02, 2026 |
| CVE-2026-13828 | chromium | - | medium | - | Fixed | Jul 02, 2026 | Jul 02, 2026 |
| CVE-2026-13821 | chromium | - | high | - | Fixed | Jul 02, 2026 | Jul 02, 2026 |
This page is currently not available for mobile devices. For the best experience, please visit us from your computer.