New vulnerabilities
Detected in the last 7 days Critical
Detected in the last 12 months6765 advisories
CVE | Origin Package | Affected Images | severity | Exploitability | status | Detected | Last Update |
|---|---|---|---|---|---|---|---|
| CVE-2026-27143 | logto | - | critical | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2026-9277 | logto | - | unknown | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2025-68121 | logto | - | critical | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2026-46595 | gitlab-runner-fips-19.1 | - | critical | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2026-39830 | gitlab-runner-fips-19.1 | - | critical | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2026-39831 | gitlab-runner-fips-19.1 | - | critical | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2026-39834 | gitlab-runner-fips-19.1 | - | critical | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2026-39821 | gitlab-runner-fips-19.1 | - | critical | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2026-39832 | gitlab-runner-fips-19.1 | - | critical | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2026-42508 | gitlab-runner-fips-19.1 | - | critical | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2026-39833 | gitlab-runner-fips-19.1 | - | critical | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2026-46595 | gitlab-runner-19.1 | - | critical | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2026-39834 | gitlab-runner-19.1 |  gitlab-runner+3 | critical | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2026-39831 | gitlab-runner-19.1 | gitlab-runner +3 | critical | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2026-42508 | gitlab-runner-19.1 | gitlab-runner +3 | critical | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2026-39830 | gitlab-runner-19.1 | gitlab-runner +3 | critical | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2026-39832 | gitlab-runner-19.1 | gitlab-runner +3 | critical | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2026-39821 | gitlab-runner-19.1 | gitlab-runner +3 | critical | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2026-39833 | gitlab-runner-19.1 | gitlab-runner +3 | critical | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2021-44521 | apache-druid-fips | - | critical | - | Unaffected | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2026-39834 | trigger-dev |  trigger-dev | critical | - | Pending upstream fix | Jun 21, 2026 | Jun 28, 2026 |
| CVE-2022-23307 | apache-druid |  apache-druid+1 | high | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2024-47561 | apache-druid-fips |  apache-druid-fips | critical | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2019-20444 | apache-druid-fips | apache-druid-fips | critical | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2026-33186 | trigger-dev | trigger-dev | critical | - | Pending upstream fix | Jun 21, 2026 | Jun 28, 2026 |
| CVE-2024-47561 | apache-druid | apache-druid +1 | critical | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2019-20444 | apache-druid | apache-druid +1 | critical | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2026-39830 | trigger-dev | trigger-dev | critical | - | Pending upstream fix | Jun 21, 2026 | Jun 28, 2026 |
| CVE-2026-39831 | trigger-dev | trigger-dev | critical | - | Pending upstream fix | Jun 21, 2026 | Jun 28, 2026 |
| CVE-2022-23307 | apache-druid-fips | apache-druid-fips | high | - | Pending upstream fix | Jun 22, 2026 | Jun 28, 2026 |
| CVE-2026-46595 | trigger-dev | trigger-dev | critical | - | Pending upstream fix | Jun 21, 2026 | Jun 28, 2026 |
| CVE-2021-44521 | apache-druid | - | critical | - | Unaffected | Jun 22, 2026 | Jun 28, 2026 |
| GHSA-9qr9-h5gf-34mp | trigger-dev | trigger-dev | critical | - | Pending upstream fix | Jun 21, 2026 | Jun 28, 2026 |
| CVE-2023-46233 | trigger-dev | trigger-dev | critical | - | Pending upstream fix | Jun 21, 2026 | Jun 28, 2026 |
| CVE-2024-41110 | trigger-dev | trigger-dev | critical | - | Pending upstream fix | Jun 21, 2026 | Jun 28, 2026 |
| CVE-2026-9277 | trigger-dev | trigger-dev | unknown | - | Pending upstream fix | Jun 21, 2026 | Jun 28, 2026 |
| CVE-2024-21534 | trigger-dev | trigger-dev | critical | - | Pending upstream fix | Jun 21, 2026 | Jun 28, 2026 |
| CVE-2026-46601 | gitea-fips | - | high | - | Fixed | Jun 27, 2026 | Jun 28, 2026 |
| CVE-2026-46599 | gitea-fips | - | high | - | Fixed | Jun 25, 2026 | Jun 28, 2026 |
| GHSA-w5pp-99ch-qj29 | gitea-fips | - | medium | - | Fixed | Jun 25, 2026 | Jun 28, 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.