New vulnerabilities
Detected in the last 7 days Critical
Detected in the last 12 months7713 advisories
CVE | Origin Package | Affected Images | severity | Exploitability | status | Detected | Last Update |
|---|---|---|---|---|---|---|---|
| CVE-2026-50009 | datahub-upgrade-fips | - | medium | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-45674 | datahub-upgrade-fips | - | critical | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-41731 | datahub-upgrade | - | high | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-54512 | datahub-upgrade | - | high | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-47244 | datahub-upgrade-fips | - | medium | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-50020 | datahub-upgrade | - | medium | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-48006 | datahub-upgrade-fips | - | high | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-41726 | datahub-upgrade-fips | - | medium | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-44250 | datahub-upgrade-fips | - | high | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-44892 | datahub-upgrade | - | high | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-54515 | datahub-upgrade | - | medium | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-50011 | datahub-upgrade-fips | - | high | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-54513 | datahub-upgrade-fips | - | high | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-45205 | datahub-upgrade-fips | - | medium | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-44249 | datahub-upgrade-fips | - | high | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-48059 | datahub-upgrade | - | high | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-44890 | datahub-upgrade | - | high | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-44892 | datahub-upgrade-fips | - | high | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-44894 | datahub-upgrade | - | high | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-50560 | datahub-upgrade-fips | - | medium | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-44249 | datahub-upgrade | - | high | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-47691 | datahub-upgrade-fips | - | critical | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-54518 | datahub-upgrade | - | medium | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-48748 | datahub-upgrade-fips | - | high | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-48059 | datahub-upgrade-fips | - | high | - | Under review | Jun 28, 2026 | Jun 28, 2026 |
| CVE-2026-44161 | ruby3.2-fluentd-1.17 | - | unknown | - | Fix not planned | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-44160 | ruby3.2-fluentd-1.17 | - | unknown | - | Fix not planned | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-44025 | ruby3.2-fluentd-1.17 | - | unknown | - | Fix not planned | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-44024 | ruby3.2-fluentd-1.17 | - | unknown | - | Fix not planned | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-44025 | ruby3.2-fluentd-1.16 |  fluentd+1 | unknown | - | Fix not planned | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-44160 | ruby3.2-fluentd-1.16 | fluentd +1 | unknown | - | Fix not planned | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-44161 | ruby3.2-fluentd-1.16 | fluentd +1 | unknown | - | Fix not planned | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-44024 | ruby3.2-fluentd-1.16 | fluentd +1 | unknown | - | Fix not planned | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-48801 | kibana-9 |  kibana+1 | unknown | - | Fix not planned | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-48801 | kibana-8.18 | kibana +3 | unknown | - | Fix not planned | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-48801 | kibana-8 | kibana +1 | unknown | - | Fix not planned | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-48801 | kibana-7 | kibana +3 | unknown | - | Fix not planned | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-55204 | haproxy-3.1 |  haproxy+1 | high | - | Fix not planned | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-55203 | haproxy-3.1 | haproxy +1 | critical | - | Fix not planned | Jun 27, 2026 | Jun 27, 2026 |
| CVE-2026-55203 | haproxy-2.4 | haproxy +1 | critical | - | Fix not planned | Jun 27, 2026 | Jun 27, 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.