New vulnerabilities
Detected in the last 7 days Critical
Detected in the last 12 months7921 advisories
CVE | Origin Package | Affected Images | severity | Exploitability | status | Detected | Last Update |
|---|---|---|---|---|---|---|---|
| CVE-2026-54513 | strimzi-kafka-operator-0.50 |  strimzi-kafka+1 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54512 | strimzi-kafka-operator-fips-0.50 |  strimzi-kafka-fips | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | strimzi-kafka-operator-fips-0.45 | strimzi-kafka-fips +1 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54512 | strimzi-kafka-operator-0.50 | strimzi-kafka +1 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54512 | strimzi-kafka-operator-fips-0.45 | strimzi-kafka-fips +1 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | strimzi-kafka-operator-fips-0.50 | strimzi-kafka-fips | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-29181 | spicedb-operator-fips |  spicedb-operator-fips | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | strimzi-kafka-bridge-fips |  strimzi-kafka-bridge-fips | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54512 | strimzi-kafka-bridge-fips | strimzi-kafka-bridge-fips | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-24051 | spicedb-operator-fips | - | high | - | Unaffected | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-39883 | spicedb-operator-fips | - | high | - | Unaffected | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-39883 | spicedb-operator | - | high | - | Unaffected | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-29181 | spicedb-operator |  spicedb-operator | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-24051 | spicedb-operator | - | high | - | Unaffected | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2023-2680 | qemu | - | high | - | Unaffected | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54512 | solr-10 |  solr | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | solr-10 | solr | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | mongodb-search-fips |  mongodb-search-fips | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54512 | mongodb-search-fips | mongodb-search-fips | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54512 | neo4j-2026.05 |  neo4j+1 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | neo4j-2026.05 | neo4j +1 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | logstash-9.4 |  logstash | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54512 | logstash-9.4 | logstash | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2025-31133 | kubevirt-1.8-fips |  kubevirt-virt-api-fips+5 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-33814 | kubevirt-1.8-fips | kubevirt-virt-api-fips +5 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2025-52565 | kubevirt-1.8-fips | kubevirt-virt-api-fips +5 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2025-52881 | kubevirt-1.8-fips | kubevirt-virt-api-fips +5 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2025-31133 | kubevirt-1.8 |  kubevirt-virt-api+5 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2025-52565 | kubevirt-1.8 | kubevirt-virt-api +5 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2025-52881 | kubevirt-1.8 | kubevirt-virt-api +5 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | kafka-4.2-fips |  kafka-advanced-fips+1 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54512 | kafka-4.2 |  kafka+4 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | kafka-4.2 | kafka +4 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | kafka-4.3-fips |  debezium-connect-fips+1 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | kafka-4.3 |  debezium-connect+4 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54512 | kafka-4.2-fips | kafka-advanced-fips +1 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54512 | kafka-4.3-fips | debezium-connect-fips +1 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54512 | kafka-4.3 | debezium-connect +4 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | kafka-4.1-fips | kafka-advanced-fips +1 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54512 | kafka-4.1-fips | kafka-advanced-fips +1 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 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.