New vulnerabilities
Detected in the last 7 days Critical
Detected in the last 12 months8674 advisories
CVE | Origin Package | Affected Images | severity | Exploitability | status | Detected | Last Update |
|---|---|---|---|---|---|---|---|
| CVE-2026-46597 | docker-scout-1.22 |  scout-cli | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-39829 | docker-scout-1.22 | scout-cli | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-53488 | docker-scout-1.22 | scout-cli | critical | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-41567 | docker-scout-1.22 | scout-cli | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-34040 | docker-scout-1.22 | scout-cli | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2025-15558 | docker-scout-1.22 | - | high | - | Unaffected | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-42306 | docker-scout-1.22 | scout-cli | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-44973 | docker-scout-1.22 | scout-cli | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-53492 | docker-scout-1.22 | scout-cli | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-46680 | docker-scout-1.22 | scout-cli | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-53489 | docker-scout-1.22 | scout-cli | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-39883 | docker-scout-1.22 | - | high | - | Unaffected | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-42504 | docker-scout-1.22 | scout-cli | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-29181 | docker-scout-1.22 | scout-cli | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-45022 | docker-scout-1.22 | scout-cli | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-33814 | docker-scout-1.22 | scout-cli | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-4660 | docker-scout-1.22 | scout-cli | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54512 | cassandra-4.1 |  cassandra+1 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | cube-1.4 |  cube | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | cube-1.6 | cube | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54512 | celeborn | - | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54512 | cube-1.4 | cube | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54512 | cube-1.6 | cube | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | cassandra-5.0 | cassandra +1 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | cassandra-4.1 | cassandra +1 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | celeborn | - | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | cassandra-reaper |  cassandra-reaper+1 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54512 | cassandra-5.0 | cassandra +1 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54512 | cassandra-4.0 | cassandra +1 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54512 | cassandra-reaper | cassandra-reaper +1 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | cassandra-4.0 | cassandra +1 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | apache-tika-3.1 |  apache-tika | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54512 | apache-tika-3.3 | apache-tika | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | apache-tika-3.3 | apache-tika | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | apicurio-registry-fips |  apicurio-registry-fips | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | apache-tika-3.2 | apache-tika | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54512 | apache-tika-3.2 | apache-tika | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | apicurio-registry |  apicurio-registry+2 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54512 | apicurio-registry | apicurio-registry +2 | high | - | Pending upstream fix | Jun 24, 2026 | Jul 02, 2026 |
| CVE-2026-54513 | apache-polaris |  apache-polaris | 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.