Last scanned:
This base/runtime image ships critical vulnerabilities that any image built on it would inherit; they must be remediated before the final image goes to production. An attacker could achieve remote code execution via Go stdlib flaws (CVE-2023-24540) or cause denial of service via OpenSSL (CVE-2022-0778) and HTTP/2 mishandling. Additionally, if an attacker gains local access, privilege escalation to root is possible via glibc (CVE-2023-4911). These vulnerabilities pose severe risk and require immediate patching before any deployment. Note: this is a general-purpose base/runtime image — many findings live in components that an application built on top may never load, so actual exploitability depends on the final image. For an accurate risk picture, re-scan the final application image with context.
Hardening plan for this image · 3 steps
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2023-24540 | CRITICAL9.8 | stdlib v1.16.7b7 fixed in 1.19.9, 1.20.4 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-24790 | CRITICAL9.8 | stdlib v1.16.7b7 fixed in 1.21.11, 1.22.4 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0778 | CRITICAL9.75 | openssl-libs 1:1.1.1k-4.el8 fixed in 1:1.1.1k-6.el8_5 | 70.6% Actively Exploited | Directly Exposed |
| CVE-2018-25032 | CRITICAL9.75 | zlib 1.2.11-17.el8 fixed in 1.2.11-18.el8_5 | 50.8% Actively Exploited | Directly Exposed |
| CVE-2023-45288 | CRITICAL9.75 | golang.org/x/net v0.0.0-20210927181540-4e4d966f7476 fixed in 0.23.0 | 92.0% Actively Exploited | Directly Exposed |
| CVE-2023-45288 | CRITICAL9.75 | stdlib v1.16.7b7 fixed in 1.21.9, 1.22.2 | 92.0% Actively Exploited | Directly Exposed |
| CVE-2023-0286 | CRITICAL9.62 | openssl-libs 1:1.1.1k-4.el8 fixed in 1:1.1.1k-9.el8_7 | 59.5% Actively Exploited | Directly Exposed |
| CVE-2021-3712 | CRITICAL9.62 | openssl-libs 1:1.1.1k-4.el8 fixed in 1:1.1.1k-5.el8_5 | 50.4% Actively Exploited | Directly Exposed |
| CVE-2022-1292 | CRITICAL9.49 | openssl-libs 1:1.1.1k-4.el8 fixed in 1:1.1.1k-7.el8_6 | 82.6% Actively Exploited | Directly Exposed |
| CVE-2022-2068 | CRITICAL9.49 | openssl-libs 1:1.1.1k-4.el8 fixed in 1:1.1.1k-7.el8_6 | 95.8% Actively Exploited | Directly Exposed |
| CVE-2022-1586 | CRITICAL9.1 | pcre2 10.32-2.el8 fixed in 10.32-3.el8_6 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1996 | CRITICAL9.1 | github.com/emicklei/go-restful v2.11.2-0.20200112161605-a7c079c43d51+incompatible fixed in 2.16.0 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33186 | CRITICAL9.1 | google.golang.org/grpc v1.27.1 fixed in 1.79.3 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23806 | CRITICAL9.1 | stdlib v1.16.7b7 fixed in 1.16.14, 1.17.7 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1271 | HIGH8.8 | xz-libs 5.2.4-3.el8 fixed in 5.2.4-4.el8_6 | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3955 | HIGH8.8 | k8s.io/kubernetes v1.21.0 fixed in 1.28.1, 1.27.5, 1.26.8, 1.25.13, 1.24.17 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5528 | HIGH8.8 | k8s.io/kubernetes v1.21.0 fixed in 1.28.4, 1.27.8, 1.26.11, 1.25.16 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-4450 | HIGH8.62 | openssl-libs 1:1.1.1k-4.el8 fixed in 1:1.1.1k-9.el8_7 | 20.4% High Exploitation Risk | Directly Exposed |
| CVE-2025-68121 | HIGH8.5 | stdlib v1.16.7b7 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-2650 | HIGH8.45 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 75.1% Actively Exploited | Directly Exposed |
| CVE-2023-37920 | HIGH8.33 | ca-certificates 2021.2.50-80.0.el8_4 fixed in 2024.2.69_v8.0.303-80.0.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | HIGH8.33 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45337 | HIGH8.2 | golang.org/x/crypto v0.0.0-20210921155107-089bfa567519 fixed in 0.31.0 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | HIGH8.1 | openssl-libs 1:1.1.1k-4.el8 fixed in 1:1.1.1k-16.el8_6 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-25741 | HIGH8.1 | k8s.io/kubernetes v1.21.0 fixed in 1.19.15, 1.20.11, 1.21.5, 1.22.2 | 8.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-10220 | HIGH8.1 | k8s.io/kubernetes v1.21.0 fixed in 1.28.12, 1.29.7, 1.30.3 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-37434 | HIGH8 | zlib 1.2.11-17.el8 fixed in 1.2.11-19.el8_6 | 15.5% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2024-2961 | HIGH8 | glibc 2.28-164.el8 fixed in 2.28-251.el8_10.1 | 88.3% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2024-2961 | HIGH8 | glibc-common 2.28-164.el8 fixed in 2.28-251.el8_10.1 | 88.3% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2024-2961 | HIGH8 | glibc-langpack-en 2.28-164.el8 fixed in 2.28-251.el8_10.1 | 88.3% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2024-2961 | HIGH8 | glibc-minimal-langpack 2.28-164.el8 fixed in 2.28-251.el8_10.1 | 88.3% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2020-11023 | HIGH7.93 | libgcc 8.5.0-4.el8_5 fixed in 8.5.0-23.el8_10 | 83.8% Actively Exploited | Directly Exposed |
| CVE-2023-26604 | HIGH7.8 | systemd-libs 239-51.el8 fixed in 239-74.el8_8.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-15114 | HIGH7.7 | go.etcd.io/etcd v0.5.0-alpha.5.0.20201125193152-8a03d2e9614b fixed in 3.4.10, 3.3.23 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-48795 | HIGH7.67 | golang.org/x/crypto v0.0.0-20210921155107-089bfa567519 fixed in 0.17.0 | 93.3% Actively Exploited | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | glibc 2.28-164.el8 fixed in 2.28-251.el8_10.2 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | glibc-common 2.28-164.el8 fixed in 2.28-251.el8_10.2 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | glibc-langpack-en 2.28-164.el8 fixed in 2.28-251.el8_10.2 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | glibc-minimal-langpack 2.28-164.el8 fixed in 2.28-251.el8_10.2 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20657 | HIGH7.5 | libgcc 8.5.0-4.el8_5 No fix yet | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-4899 | HIGH7.5 | libzstd 1.4.4-1.el8 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0215 | HIGH7.5 | openssl-libs 1:1.1.1k-4.el8 fixed in 1:1.1.1k-9.el8_7 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28390 | HIGH7.5 | openssl-libs 1:1.1.1k-4.el8 fixed in 1:1.1.1k-17.el8_6 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0464 | HIGH7.5 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28388 | HIGH7.5 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28389 | HIGH7.5 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41409 | HIGH7.5 | pcre2 10.32-2.el8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21698 | HIGH7.5 | github.com/prometheus/client_golang v1.7.1 fixed in 1.11.1 | 6.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27191 | HIGH7.5 | golang.org/x/crypto v0.0.0-20210921155107-089bfa567519 fixed in 0.0.0-20220314234659-1baeb1ce4c0b | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44716 | HIGH7.5 | golang.org/x/net v0.0.0-20210927181540-4e4d966f7476 fixed in 0.0.0-20211209124913-491a49abca63 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27664 | HIGH7.5 | golang.org/x/net v0.0.0-20210927181540-4e4d966f7476 fixed in 0.0.0-20220906165146-f3363e06e74c | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41723 | HIGH7.5 | golang.org/x/net v0.0.0-20210927181540-4e4d966f7476 fixed in 0.7.0 | 4.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39325 | HIGH7.5 | golang.org/x/net v0.0.0-20210927181540-4e4d966f7476 fixed in 0.17.0 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-38561 | HIGH7.5 | golang.org/x/text v0.3.6 fixed in 0.3.7 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32149 | HIGH7.5 | golang.org/x/text v0.3.6 fixed in 0.3.8 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-39293 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.16.8, 1.17.1 | 6.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-41771 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.16.10, 1.17.3 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-41772 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.16.10, 1.17.3 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44716 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.16.12, 1.17.5 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23772 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.16.14, 1.17.7 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24675 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.17.9, 1.18.1 | 10.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24921 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.16.15, 1.17.8 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27664 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.18.6, 1.19.1 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28131 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.17.12, 1.18.4 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28327 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.17.9, 1.18.1 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2879 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.18.7, 1.19.2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2880 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.18.7, 1.19.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29804 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.17.11, 1.18.3 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30630 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30631 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30632 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30633 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30634 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.17.11, 1.18.3 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30635 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.17.12, 1.18.4 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32189 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.17.13, 1.18.5 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41715 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.18.7, 1.19.2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41720 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.18.9, 1.19.4 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41722 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.19.6, 1.20.1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41723 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.19.6, 1.20.1 | 4.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41724 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.19.6, 1.20.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41725 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.19.6, 1.20.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24534 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.19.8, 1.20.3 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24536 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.19.8, 1.20.3 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24537 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.19.8, 1.20.3 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39325 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.20.10, 1.21.3 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45283 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.20.11, 1.21.4, 1.20.12, 1.21.5 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45287 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.20.0 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34156 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.22.7, 1.23.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-61726 | HIGH7.5 | stdlib v1.16.7b7 fixed in 1.24.12, 1.25.6 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33413 | HIGH7.48 | go.etcd.io/etcd v0.5.0-alpha.5.0.20201125193152-8a03d2e9614b No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39828 | HIGH7.48 | golang.org/x/crypto v0.0.0-20210921155107-089bfa567519 fixed in 0.52.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39832 | HIGH7.39 | golang.org/x/crypto v0.0.0-20210921155107-089bfa567519 fixed in 0.52.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-24539 | HIGH7.3 | stdlib v1.16.7b7 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29400 | HIGH7.3 | stdlib v1.16.7b7 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-39821 | MEDIUM6.97 | golang.org/x/net v0.0.0-20210927181540-4e4d966f7476 fixed in 0.55.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39831 | MEDIUM6.88 | golang.org/x/crypto v0.0.0-20210921155107-089bfa567519 fixed in 0.52.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25681 | MEDIUM6.88 | golang.org/x/net v0.0.0-20210927181540-4e4d966f7476 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27136 | MEDIUM6.88 | golang.org/x/net v0.0.0-20210927181540-4e4d966f7476 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-4304 | MEDIUM6.79 | openssl-libs 1:1.1.1k-4.el8 fixed in 1:1.1.1k-9.el8_7 | 16.2% High Exploitation Risk | Directly Exposed |
| CVE-2021-3999 | MEDIUM6.63 | glibc 2.28-164.el8 fixed in 2.28-164.el8_5.3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-3999 | MEDIUM6.63 | glibc-common 2.28-164.el8 fixed in 2.28-164.el8_5.3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-3999 | MEDIUM6.63 | glibc-langpack-en 2.28-164.el8 fixed in 2.28-164.el8_5.3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-3999 | MEDIUM6.63 | glibc-minimal-langpack 2.28-164.el8 fixed in 2.28-164.el8_5.3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-2603 | MEDIUM6.63 | libcap 2.26-5.el8 fixed in 2.48-5.el8_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | systemd-libs 239-51.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-30580 | MEDIUM6.63 | stdlib v1.16.7b7 fixed in 1.17.11, 1.18.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-29403 | MEDIUM6.63 | stdlib v1.16.7b7 fixed in 1.19.10, 1.20.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39822 | MEDIUM6.63 | stdlib v1.16.7b7 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-0793 | MEDIUM6.54 | k8s.io/kubernetes v1.21.0 fixed in 1.27.0-alpha.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4527 | MEDIUM6.5 | glibc 2.28-164.el8 fixed in 2.28-225.el8_8.6 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4527 | MEDIUM6.5 | glibc-common 2.28-164.el8 fixed in 2.28-225.el8_8.6 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4527 | MEDIUM6.5 | glibc-langpack-en 2.28-164.el8 fixed in 2.28-225.el8_8.6 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4527 | MEDIUM6.5 | glibc-minimal-langpack 2.28-164.el8 fixed in 2.28-225.el8_8.6 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-15136 | MEDIUM6.5 | go.etcd.io/etcd v0.5.0-alpha.5.0.20201125193152-8a03d2e9614b fixed in 3.4.10, 3.3.23 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2727 | MEDIUM6.5 | k8s.io/kubernetes v1.21.0 fixed in 1.27.3, 1.26.6, 1.25.11, 1.24.15 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2728 | MEDIUM6.5 | k8s.io/kubernetes v1.21.0 fixed in 1.27.3, 1.26.6, 1.25.11, 1.24.15 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1705 | MEDIUM6.5 | stdlib v1.16.7b7 fixed in 1.17.12, 1.18.4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32148 | MEDIUM6.5 | stdlib v1.16.7b7 fixed in 1.17.12, 1.18.4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29406 | MEDIUM6.5 | stdlib v1.16.7b7 fixed in 1.19.11, 1.20.6 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-35172 | MEDIUM6.38 | github.com/distribution/distribution v2.7.1+incompatible No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-43565 | MEDIUM6.38 | golang.org/x/crypto v0.0.0-20210921155107-089bfa567519 fixed in 0.0.0-20211202192323-5770296d904e | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-22869 | MEDIUM6.38 | golang.org/x/crypto v0.0.0-20210921155107-089bfa567519 fixed in 0.35.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-47913 | MEDIUM6.38 | golang.org/x/crypto v0.0.0-20210921155107-089bfa567519 fixed in 0.43.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-39829 | MEDIUM6.38 | golang.org/x/crypto v0.0.0-20210921155107-089bfa567519 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-39830 | MEDIUM6.38 | golang.org/x/crypto v0.0.0-20210921155107-089bfa567519 fixed in 0.52.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-39835 | MEDIUM6.38 | golang.org/x/crypto v0.0.0-20210921155107-089bfa567519 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46597 | MEDIUM6.38 | golang.org/x/crypto v0.0.0-20210921155107-089bfa567519 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-45338 | MEDIUM6.38 | golang.org/x/net v0.0.0-20210927181540-4e4d966f7476 fixed in 0.33.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | golang.org/x/net v0.0.0-20210927181540-4e4d966f7476 fixed in 0.53.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-22868 | MEDIUM6.38 | golang.org/x/oauth2 v0.0.0-20200107190931-bf48bf16ab8d fixed in 0.27.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-41716 | MEDIUM6.38 | stdlib v1.16.7b7 fixed in 1.18.8, 1.19.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-61729 | MEDIUM6.38 | stdlib v1.16.7b7 fixed in 1.24.11, 1.25.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25679 | MEDIUM6.38 | stdlib v1.16.7b7 fixed in 1.25.8, 1.26.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-27145 | MEDIUM6.38 | stdlib v1.16.7b7 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32280 | MEDIUM6.38 | stdlib v1.16.7b7 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32281 | MEDIUM6.38 | stdlib v1.16.7b7 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32283 | MEDIUM6.38 | stdlib v1.16.7b7 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33811 | MEDIUM6.38 | stdlib v1.16.7b7 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | stdlib v1.16.7b7 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39820 | MEDIUM6.38 | stdlib v1.16.7b7 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39836 | MEDIUM6.38 | stdlib v1.16.7b7 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42499 | MEDIUM6.38 | stdlib v1.16.7b7 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42504 | MEDIUM6.38 | stdlib v1.16.7b7 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-58183 | MEDIUM6.38 | stdlib v1.16.7b7 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61728 | MEDIUM6.38 | stdlib v1.16.7b7 fixed in 1.24.12, 1.25.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | openssl-libs 1:1.1.1k-4.el8 fixed in 1:1.1.1k-15.el8_6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42508 | MEDIUM6.29 | golang.org/x/crypto v0.0.0-20210921155107-089bfa567519 fixed in 0.52.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4911 | MEDIUM6.08 | glibc 2.28-164.el8 fixed in 2.28-225.el8_8.6 | 81.4% Actively Exploited | Post-ExploitContext importance: HIGH |
| CVE-2023-4911 | MEDIUM6.08 | glibc-common 2.28-164.el8 fixed in 2.28-225.el8_8.6 | 81.4% Actively Exploited | Post-ExploitContext importance: HIGH |
| CVE-2023-4911 | MEDIUM6.08 | glibc-langpack-en 2.28-164.el8 fixed in 2.28-225.el8_8.6 | 81.4% Actively Exploited | Post-ExploitContext importance: HIGH |
| CVE-2023-4911 | MEDIUM6.08 | glibc-minimal-langpack 2.28-164.el8 fixed in 2.28-225.el8_8.6 | 81.4% Actively Exploited | Post-ExploitContext importance: HIGH |
| CVE-2026-54369 | MEDIUM6.03 | libacl 2.2.53-1.el8 fixed in 2.4.0-1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46595 | MEDIUM6.03 | golang.org/x/crypto v0.0.0-20210921155107-089bfa567519 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | glibc 2.28-164.el8 fixed in 2.28-251.el8_10.22 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | glibc-common 2.28-164.el8 fixed in 2.28-251.el8_10.22 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | glibc-langpack-en 2.28-164.el8 fixed in 2.28-251.el8_10.22 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | glibc-minimal-langpack 2.28-164.el8 fixed in 2.28-251.el8_10.22 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM5.95 | libcap 2.26-5.el8 fixed in 2.48-6.el8_10.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44604 | MEDIUM5.95 | rpm-libs 4.14.3-19.el8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-47907 | MEDIUM5.95 | stdlib v1.16.7b7 fixed in 1.23.12, 1.24.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | glibc 2.28-164.el8 fixed in 2.28-225.el8_8.6 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | glibc 2.28-164.el8 fixed in 2.28-225.el8_8.6 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | glibc-common 2.28-164.el8 fixed in 2.28-225.el8_8.6 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | glibc-common 2.28-164.el8 fixed in 2.28-225.el8_8.6 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | glibc-langpack-en 2.28-164.el8 fixed in 2.28-225.el8_8.6 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | glibc-langpack-en 2.28-164.el8 fixed in 2.28-225.el8_8.6 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | glibc-minimal-langpack 2.28-164.el8 fixed in 2.28-225.el8_8.6 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | glibc-minimal-langpack 2.28-164.el8 fixed in 2.28-225.el8_8.6 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2408 | MEDIUM5.9 | openssl-libs 1:1.1.1k-4.el8 fixed in 1:1.1.1k-12.el8_9 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-41996 | MEDIUM5.9 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | openssl-libs 1:1.1.1k-4.el8 fixed in 1:1.1.1k-14.el8_6 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-24786 | MEDIUM5.9 | google.golang.org/protobuf v1.25.0 fixed in 1.33.0 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-9042 | MEDIUM5.9 | k8s.io/kubernetes v1.21.0 fixed in 1.29.13, 1.30.9, 1.31.5, 1.32.1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-36221 | MEDIUM5.9 | stdlib v1.16.7b7 fixed in 1.15.15, 1.16.7 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-24791 | MEDIUM5.9 | stdlib v1.16.7b7 fixed in 1.21.12, 1.22.5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34158 | MEDIUM5.9 | stdlib v1.16.7b7 fixed in 1.22.7, 1.23.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-4673 | MEDIUM5.78 | stdlib v1.16.7b7 fixed in 1.23.10, 1.24.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-35938 | MEDIUM5.7 | rpm-libs 4.14.3-19.el8 fixed in 4.14.3-28.el8_9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-35939 | MEDIUM5.7 | rpm-libs 4.14.3-19.el8 fixed in 4.14.3-28.el8_9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | systemd-libs 239-51.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5187 | MEDIUM5.7 | k8s.io/kubernetes v1.21.0 fixed in 1.31.12, 1.32.8, 1.33.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | openssl-libs 1:1.1.1k-4.el8 fixed in 1:1.1.1k-14.el8_10 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | openssl-libs 1:1.1.1k-4.el8 fixed in 1:1.1.1k-16.el8_6 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc 2.28-164.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc 2.28-164.el8 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc-common 2.28-164.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc-common 2.28-164.el8 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc-langpack-en 2.28-164.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc-langpack-en 2.28-164.el8 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc-minimal-langpack 2.28-164.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc-minimal-langpack 2.28-164.el8 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42771 | MEDIUM5.52 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41888 | MEDIUM5.52 | github.com/distribution/distribution v2.7.1+incompatible No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-2253 | MEDIUM5.52 | github.com/docker/distribution v2.7.1+incompatible fixed in 2.8.2-beta.1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-33343 | MEDIUM5.52 | go.etcd.io/etcd v0.5.0-alpha.5.0.20201125193152-8a03d2e9614b No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39827 | MEDIUM5.52 | golang.org/x/crypto v0.0.0-20210921155107-089bfa567519 fixed in 0.52.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39834 | MEDIUM5.52 | golang.org/x/crypto v0.0.0-20210921155107-089bfa567519 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-22872 | MEDIUM5.52 | golang.org/x/net v0.0.0-20210927181540-4e4d966f7476 fixed in 0.38.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25680 | MEDIUM5.52 | golang.org/x/net v0.0.0-20210927181540-4e4d966f7476 fixed in 0.55.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1767 | MEDIUM5.52 | k8s.io/kubernetes v1.21.0 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-24785 | MEDIUM5.52 | stdlib v1.16.7b7 fixed in 1.21.8, 1.22.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-47906 | MEDIUM5.52 | stdlib v1.16.7b7 fixed in 1.23.12, 1.24.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61727 | MEDIUM5.52 | stdlib v1.16.7b7 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39825 | MEDIUM5.52 | stdlib v1.16.7b7 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-14250 | MEDIUM5.5 | libgcc 8.5.0-4.el8_5 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-44605 | MEDIUM5.5 | rpm-libs 4.14.3-19.el8 No fix yet | — | Directly Exposed |
| CVE-2021-3997 | MEDIUM5.5 | systemd-libs 239-51.el8 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35937 | MEDIUM5.44 | rpm-libs 4.14.3-19.el8 fixed in 4.14.3-28.el8_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32282 | MEDIUM5.44 | stdlib v1.16.7b7 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-24784 | MEDIUM5.4 | stdlib v1.16.7b7 fixed in 1.21.8, 1.22.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl 2.2.53-1.el8 fixed in 2.4.0-1.el8_10 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM5.35 | libattr 2.4.48-3.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | glibc 2.28-164.el8 fixed in 2.28-251.el8_10.2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | glibc-common 2.28-164.el8 fixed in 2.28-251.el8_10.2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | glibc-langpack-en 2.28-164.el8 fixed in 2.28-251.el8_10.2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | glibc-minimal-langpack 2.28-164.el8 fixed in 2.28-251.el8_10.2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2097 | MEDIUM5.3 | openssl-libs 1:1.1.1k-4.el8 fixed in 1:1.1.1k-7.el8_6 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0466 | MEDIUM5.3 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0465 | MEDIUM5.3 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3446 | MEDIUM5.3 | openssl-libs 1:1.1.1k-4.el8 fixed in 1:1.1.1k-12.el8_9 | 6.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3817 | MEDIUM5.3 | openssl-libs 1:1.1.1k-4.el8 fixed in 1:1.1.1k-12.el8_9 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | openssl-libs 1:1.1.1k-4.el8 fixed in 1:1.1.1k-12.el8_9 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41717 | MEDIUM5.3 | golang.org/x/net v0.0.0-20210927181540-4e4d966f7476 fixed in 0.4.0 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29526 | MEDIUM5.3 | golang.org/x/sys v0.0.0-20210927094055-39ccf1dd6fa6 fixed in 0.0.0-20220412211240-33da011f77ad | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29526 | MEDIUM5.3 | stdlib v1.16.7b7 fixed in 1.17.10, 1.18.2 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41717 | MEDIUM5.3 | stdlib v1.16.7b7 fixed in 1.18.9, 1.19.4 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29409 | MEDIUM5.3 | stdlib v1.16.7b7 fixed in 1.19.12, 1.20.7, 1.21.0-rc.4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39326 | MEDIUM5.3 | stdlib v1.16.7b7 fixed in 1.20.12, 1.21.5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45289 | MEDIUM5.3 | stdlib v1.16.7b7 fixed in 1.21.8, 1.22.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45290 | MEDIUM5.3 | stdlib v1.16.7b7 fixed in 1.21.8, 1.22.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | p11-kit-trust 0.23.22-1.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-0426 | MEDIUM5.27 | k8s.io/kubernetes v1.21.0 fixed in 1.32.2, 1.31.6, 1.30.10, 1.29.14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-3978 | MEDIUM5.18 | golang.org/x/net v0.0.0-20210927181540-4e4d966f7476 fixed in 0.13.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42502 | MEDIUM5.18 | golang.org/x/net v0.0.0-20210927181540-4e4d966f7476 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-5321 | MEDIUM5.18 | k8s.io/kubernetes v1.21.0 fixed in 1.27.16, 1.28.12, 1.29.7, 1.30.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-39318 | MEDIUM5.18 | stdlib v1.16.7b7 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-39319 | MEDIUM5.18 | stdlib v1.16.7b7 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-32289 | MEDIUM5.18 | stdlib v1.16.7b7 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc 2.28-164.el8 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | glibc 2.28-164.el8 fixed in 2.28-251.el8_10.31 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-common 2.28-164.el8 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | glibc-common 2.28-164.el8 fixed in 2.28-251.el8_10.31 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-langpack-en 2.28-164.el8 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | glibc-langpack-en 2.28-164.el8 fixed in 2.28-251.el8_10.31 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-minimal-langpack 2.28-164.el8 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | glibc-minimal-langpack 2.28-164.el8 fixed in 2.28-251.el8_10.31 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15468 | MEDIUM5.02 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-7008 | MEDIUM5.02 | systemd-libs 239-51.el8 fixed in 239-82.el8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-24783 | MEDIUM5.02 | stdlib v1.16.7b7 fixed in 1.21.8, 1.22.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-34155 | MEDIUM5.02 | stdlib v1.16.7b7 fixed in 1.22.7, 1.23.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-45336 | MEDIUM5.02 | stdlib v1.16.7b7 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-8554 | MEDIUM5 | k8s.io/kubernetes v1.21.0 No fix yet | 9.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13281 | MEDIUM4.93 | k8s.io/kubernetes v1.21.0 fixed in 1.32.10, 1.33.6, 1.34.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 54.0% Actively Exploited | Directly Exposed |
| CVE-2021-25737 | MEDIUM4.8 | k8s.io/kubernetes v1.21.0 fixed in 1.18.19, 1.19.11, 1.20.7, 1.21.1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44717 | MEDIUM4.8 | stdlib v1.16.7b7 fixed in 1.16.12, 1.17.5 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc 2.28-164.el8 fixed in 2.28-251.el8_10.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc-common 2.28-164.el8 fixed in 2.28-251.el8_10.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc-langpack-en 2.28-164.el8 fixed in 2.28-251.el8_10.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc-minimal-langpack 2.28-164.el8 fixed in 2.28-251.el8_10.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc 8.5.0-4.el8_5 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-15469 | MEDIUM4.67 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-3821 | MEDIUM4.67 | systemd-libs 239-51.el8 fixed in 239-68.el8_7.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-4415 | MEDIUM4.67 | systemd-libs 239-51.el8 fixed in 239-68.el8_7.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib 1.2.11-17.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-1099 | MEDIUM4.67 | go.etcd.io/etcd v0.5.0-alpha.5.0.20201125193152-8a03d2e9614b fixed in 3.4.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-39833 | MEDIUM4.67 | golang.org/x/crypto v0.0.0-20210921155107-089bfa567519 fixed in 0.52.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-2431 | MEDIUM4.67 | k8s.io/kubernetes v1.21.0 fixed in 1.24.14, 1.25.10, 1.26.5, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-1962 | MEDIUM4.67 | stdlib v1.16.7b7 fixed in 1.17.12, 1.18.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-24789 | MEDIUM4.67 | stdlib v1.16.7b7 fixed in 1.21.11, 1.22.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32288 | MEDIUM4.67 | stdlib v1.16.7b7 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42506 | MEDIUM4.59 | golang.org/x/net v0.0.0-20210927181540-4e4d966f7476 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22871 | MEDIUM4.59 | stdlib v1.16.7b7 fixed in 1.23.8, 1.24.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-27142 | MEDIUM4.59 | stdlib v1.16.7b7 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39823 | MEDIUM4.59 | stdlib v1.16.7b7 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39826 | MEDIUM4.59 | stdlib v1.16.7b7 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | glibc 2.28-164.el8 fixed in 2.28-251.el8_10.31 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc 2.28-164.el8 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | glibc-common 2.28-164.el8 fixed in 2.28-251.el8_10.31 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-common 2.28-164.el8 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | glibc-langpack-en 2.28-164.el8 fixed in 2.28-251.el8_10.31 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-langpack-en 2.28-164.el8 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | glibc-minimal-langpack 2.28-164.el8 fixed in 2.28-251.el8_10.31 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-minimal-langpack 2.28-164.el8 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | xz-libs 5.2.4-3.el8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-47914 | MEDIUM4.5 | golang.org/x/crypto v0.0.0-20210921155107-089bfa567519 fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58181 | MEDIUM4.5 | golang.org/x/crypto v0.0.0-20210921155107-089bfa567519 fixed in 0.45.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46598 | MEDIUM4.5 | golang.org/x/crypto v0.0.0-20210921155107-089bfa567519 fixed in 0.52.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-47911 | MEDIUM4.5 | golang.org/x/net v0.0.0-20210927181540-4e4d966f7476 fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58190 | MEDIUM4.5 | golang.org/x/net v0.0.0-20210927181540-4e4d966f7476 fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-24532 | MEDIUM4.5 | stdlib v1.16.7b7 fixed in 1.19.7, 1.20.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-45284 | MEDIUM4.5 | stdlib v1.16.7b7 fixed in 1.20.11, 1.21.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-22866 | MEDIUM4.5 | stdlib v1.16.7b7 fixed in 1.22.12, 1.23.6, 1.24.0-rc.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-22873 | MEDIUM4.5 | stdlib v1.16.7b7 fixed in 1.23.9, 1.24.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-47912 | MEDIUM4.5 | stdlib v1.16.7b7 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58185 | MEDIUM4.5 | stdlib v1.16.7b7 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58187 | MEDIUM4.5 | stdlib v1.16.7b7 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58188 | MEDIUM4.5 | stdlib v1.16.7b7 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58189 | MEDIUM4.5 | stdlib v1.16.7b7 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61723 | MEDIUM4.5 | stdlib v1.16.7b7 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61724 | MEDIUM4.5 | stdlib v1.16.7b7 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61725 | MEDIUM4.5 | stdlib v1.16.7b7 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61730 | MEDIUM4.5 | stdlib v1.16.7b7 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42505 | MEDIUM4.5 | stdlib v1.16.7b7 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42507 | MEDIUM4.5 | stdlib v1.16.7b7 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58186 | MEDIUM4.5 | stdlib v1.16.7b7 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2018-20839 | MEDIUM4.3 | systemd-libs 239-51.el8 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc 2.28-164.el8 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc 2.28-164.el8 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-common 2.28-164.el8 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-common 2.28-164.el8 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-langpack-en 2.28-164.el8 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-langpack-en 2.28-164.el8 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-minimal-langpack 2.28-164.el8 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-minimal-langpack 2.28-164.el8 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-8561 | MEDIUM4.1 | k8s.io/kubernetes v1.21.0 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-24032 | MEDIUM4 | libzstd 1.4.4-1.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-3521 | MEDIUM4 | rpm-libs 4.14.3-19.el8 fixed in 4.14.3-19.el8_5.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-4598 | MEDIUM4 | systemd-libs 239-51.el8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | glibc 2.28-164.el8 fixed in 2.28-251.el8_10.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | glibc-common 2.28-164.el8 fixed in 2.28-251.el8_10.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | glibc-langpack-en 2.28-164.el8 fixed in 2.28-251.el8_10.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | glibc-minimal-langpack 2.28-164.el8 fixed in 2.28-251.el8_10.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-22870 | LOW3.74 | golang.org/x/net v0.0.0-20210927181540-4e4d966f7476 fixed in 0.36.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-22870 | LOW3.74 | stdlib v1.16.7b7 fixed in 1.23.7, 1.24.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-4122 | LOW3.65 | cryptsetup-libs 2.3.3-4.el8 fixed in 2.3.3-4.el8_5.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44283 | LOW3.65 | go.etcd.io/etcd v0.5.0-alpha.5.0.20201125193152-8a03d2e9614b fixed in 3.4.44 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-3676 | LOW3.64 | k8s.io/kubernetes v1.21.0 fixed in 1.28.1, 1.27.5, 1.26.8, 1.25.13, 1.24.17 | 11.7% High Exploitation Risk | Post-Exploit |
| CVE-2026-44604 | LOW3.57 | rpm 4.14.3-19.el8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-8058 | LOW3.57 | glibc 2.28-164.el8 fixed in 2.28-251.el8_10.25 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | glibc-common 2.28-164.el8 fixed in 2.28-251.el8_10.25 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | glibc-langpack-en 2.28-164.el8 fixed in 2.28-251.el8_10.25 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | glibc-minimal-langpack 2.28-164.el8 fixed in 2.28-251.el8_10.25 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45341 | LOW3.57 | stdlib v1.16.7b7 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-23218 | LOW3.53 | glibc 2.28-164.el8 fixed in 2.28-164.el8_5.3 | 4.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-23219 | LOW3.53 | glibc 2.28-164.el8 fixed in 2.28-164.el8_5.3 | 4.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-23218 | LOW3.53 | glibc-common 2.28-164.el8 fixed in 2.28-164.el8_5.3 | 4.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-23219 | LOW3.53 | glibc-common 2.28-164.el8 fixed in 2.28-164.el8_5.3 | 4.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-23218 | LOW3.53 | glibc-langpack-en 2.28-164.el8 fixed in 2.28-164.el8_5.3 | 4.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-23219 | LOW3.53 | glibc-langpack-en 2.28-164.el8 fixed in 2.28-164.el8_5.3 | 4.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-23218 | LOW3.53 | glibc-minimal-langpack 2.28-164.el8 fixed in 2.28-164.el8_5.3 | 4.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-23219 | LOW3.53 | glibc-minimal-langpack 2.28-164.el8 fixed in 2.28-164.el8_5.3 | 4.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2526 | LOW3.53 | systemd-libs 239-51.el8 fixed in 239-58.el8_6.4 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2023-24538 | LOW3.53 | stdlib v1.16.7b7 fixed in 1.19.8, 1.20.3 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2021-35938 | LOW3.42 | rpm 4.14.3-19.el8 fixed in 4.14.3-28.el8_9 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2021-35939 | LOW3.42 | rpm 4.14.3-19.el8 fixed in 4.14.3-28.el8_9 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-25260 | LOW3.4 | elfutils-libelf 0.185-1.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | glibc 2.28-164.el8 fixed in 2.28-251.el8_10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc 2.28-164.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | glibc-common 2.28-164.el8 fixed in 2.28-251.el8_10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc-common 2.28-164.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | glibc-langpack-en 2.28-164.el8 fixed in 2.28-251.el8_10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc-langpack-en 2.28-164.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | glibc-minimal-langpack 2.28-164.el8 fixed in 2.28-251.el8_10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc-minimal-langpack 2.28-164.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | openssl-libs 1:1.1.1k-4.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-46836 | LOW3.37 | net-tools 2.0-0.52.20160912git.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-44605 | LOW3.3 | rpm 4.14.3-19.el8 No fix yet | — | Post-Exploit |
| CVE-2021-35937 | LOW3.26 | rpm 4.14.3-19.el8 fixed in 4.14.3-28.el8_9 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.5-2.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-1271 | LOW3.17 | gzip 1.9-12.el8 fixed in 1.9-13.el8_5 | 4.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-56391 | LOW3.11 | coreutils-single 8.30-12.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.32.1-28.el8 fixed in 2.32.1-48.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2020-8562 | LOW3.1 | k8s.io/kubernetes v1.21.0 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-25740 | LOW3.1 | k8s.io/kubernetes v1.21.0 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4641 | LOW2.8 | shadow-utils 2:4.6-14.el8 fixed in 2:4.6-19.el8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-2602 | LOW2.8 | libcap 2.26-5.el8 fixed in 2.48-5.el8_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW2.7 | util-linux 2.32.1-28.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-3177 | LOW2.7 | k8s.io/kubernetes v1.21.0 fixed in 1.27.13, 1.29.4, 1.28.9 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33540 | LOW2.63 | github.com/distribution/distribution v2.7.1+incompatible No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-30629 | LOW2.63 | stdlib v1.16.7b7 fixed in 1.17.11, 1.18.3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-25743 | LOW2.55 | k8s.io/kubernetes v1.21.0 fixed in 1.26.0-alpha.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-41991 | LOW2.4 | gzip 1.9-12.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-3521 | LOW2.4 | rpm 4.14.3-19.el8 fixed in 4.14.3-19.el8_5.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.32.1-28.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils-single 8.30-12.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.24 | coreutils-single 8.30-12.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27139 | LOW2.12 | stdlib v1.16.7b7 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56433 | LOW1.84 | shadow-utils 2:4.6-14.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11961 | LOW1.61 | libpcap 14:1.9.1-5.el8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-2526 | NONE0 | systemd-pam 239-51.el8 fixed in 239-58.el8_6.4 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-39537 | NONE0 | ncurses-base 6.1-9.20180224.el8 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-39537 | NONE0 | ncurses-libs 6.1-9.20180224.el8 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-6345 | NONE0 | platform-python-setuptools 39.2.0-6.el8 fixed in 39.2.0-8.el8_10 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-47273 | NONE0 | platform-python-setuptools 39.2.0-6.el8 fixed in 39.2.0-9.el8_10 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-6345 | NONE0 | python3-setuptools-wheel 39.2.0-6.el8 fixed in 39.2.0-8.el8_10 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-47273 | NONE0 | python3-setuptools-wheel 39.2.0-6.el8 fixed in 39.2.0-9.el8_10 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-29491 | NONE0 | ncurses-base 6.1-9.20180224.el8 fixed in 6.1-9.20180224.el8_8.1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-29491 | NONE0 | ncurses-libs 6.1-9.20180224.el8 fixed in 6.1-9.20180224.el8_8.1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | pam 1.3.1-15.el8 fixed in 1.3.1-38.el8_10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-8941 | NONE0 | pam 1.3.1-15.el8 fixed in 1.3.1-38.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-26604 | NONE0 | systemd-pam 239-51.el8 fixed in 239-74.el8_8.2 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-29111 | NONE0 | systemd-pam 239-51.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-10963 | NONE0 | pam 1.3.1-15.el8 fixed in 1.3.1-36.el8_10 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | systemd-pam 239-51.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2020-19185 | NONE0 | ncurses-base 6.1-9.20180224.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19186 | NONE0 | ncurses-base 6.1-9.20180224.el8 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-19187 | NONE0 | ncurses-base 6.1-9.20180224.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19188 | NONE0 | ncurses-base 6.1-9.20180224.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19189 | NONE0 | ncurses-base 6.1-9.20180224.el8 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-19190 | NONE0 | ncurses-base 6.1-9.20180224.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.1-9.20180224.el8 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2020-19185 | NONE0 | ncurses-libs 6.1-9.20180224.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19186 | NONE0 | ncurses-libs 6.1-9.20180224.el8 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-19187 | NONE0 | ncurses-libs 6.1-9.20180224.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19188 | NONE0 | ncurses-libs 6.1-9.20180224.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19189 | NONE0 | ncurses-libs 6.1-9.20180224.el8 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-19190 | NONE0 | ncurses-libs 6.1-9.20180224.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-libs 6.1-9.20180224.el8 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-12610 | NONE0 | pam 1.3.1-15.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-40897 | NONE0 | platform-python-setuptools 39.2.0-6.el8 fixed in 39.2.0-6.el8_7.1 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-40897 | NONE0 | python3-setuptools-wheel 39.2.0-6.el8 fixed in 39.2.0-6.el8_7.1 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-7008 | NONE0 | systemd-pam 239-51.el8 fixed in 239-82.el8 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2018-19211 | NONE0 | ncurses-base 6.1-9.20180224.el8 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2018-19211 | NONE0 | ncurses-libs 6.1-9.20180224.el8 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | pam 1.3.1-15.el8 fixed in 1.3.1-33.el8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-3821 | NONE0 | systemd-pam 239-51.el8 fixed in 239-68.el8_7.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-4415 | NONE0 | systemd-pam 239-51.el8 fixed in 239-68.el8_7.4 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2021-3997 | NONE0 | systemd-pam 239-51.el8 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-54411 | NONE0 | pam 1.3.1-15.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | pam 1.3.1-15.el8 fixed in 1.3.1-36.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-4598 | NONE0 | systemd-pam 239-51.el8 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2018-20839 | NONE0 | systemd-pam 239-51.el8 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| GHSA-qq97-vm5h-rrhg | NONE0 | github.com/docker/distribution v2.7.1+incompatible fixed in 2.8.0 | — | Not Applicable |
| CVE-2022-30636 | NONE0 | golang.org/x/crypto v0.0.0-20210921155107-089bfa567519 fixed in 0.0.0-20220525230936-793ad666bf5e | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46600 | NONE0 | golang.org/x/net v0.0.0-20210927181540-4e4d966f7476 fixed in 0.56.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39824 | NONE0 | golang.org/x/sys v0.0.0-20210927094055-39ccf1dd6fa6 fixed in 0.44.0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56852 | NONE0 | golang.org/x/text v0.3.6 fixed in 0.39.0 | 0.4% Theoretical Threat | Not Applicable |
| GHSA-hrxh-6v49-42gf | NONE0 | google.golang.org/grpc v1.27.1 fixed in 1.82.1 | — | Not Applicable |
| GHSA-m425-mq94-257g | NONE0 | google.golang.org/grpc v1.27.1 fixed in 1.56.3, 1.57.1, 1.58.3 | — | Not Applicable |
| CVE-2025-0913 | NONE0 | stdlib v1.16.7b7 fixed in 1.23.10, 1.24.4 | 0.2% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.