Last scanned:
This image poses a critical security risk and must not be used in production, especially as an internet-facing service. The most severe finding, CVE-2023-45288, allows a remote attacker to exhaust CPU and connections by sending excessive HTTP/2 CONTINUATION frames, leading to denial of service. The image also exposes 677 total vulnerabilities, including 225 with severity 7.0 or higher, and other critical issues that can expose host files or weaken TLS security. Given the high exploit probability and criticality, no production deployment should be considered until all exposed vulnerabilities are remediated.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2023-45288 | CRITICAL9.75 | golang.org/x/net v0.0.0-20201110031124-69a78807bb2b fixed in 0.23.0 | 92.0% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2023-45288 | CRITICAL9.75 | stdlib v1.16 fixed in 1.21.9, 1.22.2 | 92.0% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2023-45288 | CRITICAL9.75 | stdlib v1.15.7 fixed in 1.21.9, 1.22.2 | 92.0% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2023-45288 | CRITICAL9.75 | stdlib v1.14.10 fixed in 1.21.9, 1.22.2 | 92.0% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2023-45288 | CRITICAL9.75 | stdlib v1.15.6 fixed in 1.21.9, 1.22.2 | 92.0% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2022-23648 | HIGH8.62 | github.com/containerd/containerd v1.3.4 fixed in 1.4.13, 1.5.10, 1.6.1 | 27.4% High Exploitation Risk | Directly Exposed |
| CVE-2021-3121 | HIGH8.6 | github.com/gogo/protobuf v1.3.1 fixed in 1.3.2 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-68121 | HIGH8.5 | stdlib v1.16 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-68121 | HIGH8.5 | stdlib v1.15.7 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-68121 | HIGH8.5 | stdlib v1.14.10 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-68121 | HIGH8.5 | stdlib v1.15.6 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-30465 | HIGH8.5 | github.com/opencontainers/runc v0.1.1 fixed in 1.0.0-rc95 | 6.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45337 | HIGH8.2 | golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 fixed in 0.31.0 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45337 | HIGH8.2 | golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 fixed in 0.31.0 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-21613 | HIGH8.1 | gopkg.in/src-d/go-git.v4 v4.13.1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-25741 | HIGH8.1 | k8s.io/kubernetes v1.20.4 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.20.4 fixed in 1.28.12, 1.29.7, 1.30.3 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-49569 | HIGH7.84 | gopkg.in/src-d/go-git.v4 v4.13.1 No fix yet | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-24538 | HIGH7.84 | stdlib v1.16 fixed in 1.19.8, 1.20.3 | 2.3% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-24540 | HIGH7.84 | stdlib v1.16 fixed in 1.19.9, 1.20.4 | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2024-24790 | HIGH7.84 | stdlib v1.16 fixed in 1.21.11, 1.22.4 | 2.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-24538 | HIGH7.84 | stdlib v1.15.7 fixed in 1.19.8, 1.20.3 | 2.3% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-24540 | HIGH7.84 | stdlib v1.15.7 fixed in 1.19.9, 1.20.4 | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2024-24790 | HIGH7.84 | stdlib v1.15.7 fixed in 1.21.11, 1.22.4 | 2.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-24538 | HIGH7.84 | stdlib v1.14.10 fixed in 1.19.8, 1.20.3 | 2.3% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-24540 | HIGH7.84 | stdlib v1.14.10 fixed in 1.19.9, 1.20.4 | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2024-24790 | HIGH7.84 | stdlib v1.14.10 fixed in 1.21.11, 1.22.4 | 2.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-24538 | HIGH7.84 | stdlib v1.15.6 fixed in 1.19.8, 1.20.3 | 2.3% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-24540 | HIGH7.84 | stdlib v1.15.6 fixed in 1.19.9, 1.20.4 | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2024-24790 | HIGH7.84 | stdlib v1.15.6 fixed in 1.21.11, 1.22.4 | 2.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2021-21272 | HIGH7.7 | github.com/deislabs/oras v0.8.1 fixed in 0.9.0 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-48795 | HIGH7.67 | golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 fixed in 0.17.0 | 93.3% Actively Exploited | Directly Exposed |
| CVE-2023-48795 | HIGH7.67 | golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 fixed in 0.17.0 | 93.3% Actively Exploited | Directly Exposed |
| CVE-2021-3580 | HIGH7.5 | libhogweed6 3.6-2ubuntu0.1 fixed in 3.6-2ubuntu0.2 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3580 | HIGH7.5 | libnettle8 3.6-2ubuntu0.1 fixed in 3.6-2ubuntu0.2 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-26160 | HIGH7.5 | github.com/dgrijalva/jwt-go v3.2.0+incompatible No fix yet | 2.2% 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-2020-29652 | HIGH7.5 | golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 fixed in 0.0.0-20201216223049-8b5274cf687f | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27191 | HIGH7.5 | golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 fixed in 0.0.0-20220314234659-1baeb1ce4c0b | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33194 | HIGH7.5 | golang.org/x/net v0.0.0-20201110031124-69a78807bb2b fixed in 0.0.0-20210520170846-37e1c6afe023 | 7.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44716 | HIGH7.5 | golang.org/x/net v0.0.0-20201110031124-69a78807bb2b 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-20201110031124-69a78807bb2b 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-20201110031124-69a78807bb2b fixed in 0.7.0 | 4.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39325 | HIGH7.5 | golang.org/x/net v0.0.0-20201110031124-69a78807bb2b fixed in 0.17.0 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-38561 | HIGH7.5 | golang.org/x/text v0.3.4 fixed in 0.3.7 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32149 | HIGH7.5 | golang.org/x/text v0.3.4 fixed in 0.3.8 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-27918 | HIGH7.5 | stdlib v1.16 fixed in 1.15.9, 1.16.1 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33196 | HIGH7.5 | stdlib v1.16 fixed in 1.15.13, 1.16.5 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33198 | HIGH7.5 | stdlib v1.16 fixed in 1.15.13, 1.16.5 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-39293 | HIGH7.5 | stdlib v1.16 fixed in 1.16.8, 1.17.1 | 6.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-41771 | HIGH7.5 | stdlib v1.16 fixed in 1.16.10, 1.17.3 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-41772 | HIGH7.5 | stdlib v1.16 fixed in 1.16.10, 1.17.3 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44716 | HIGH7.5 | stdlib v1.16 fixed in 1.16.12, 1.17.5 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23772 | HIGH7.5 | stdlib v1.16 fixed in 1.16.14, 1.17.7 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24675 | HIGH7.5 | stdlib v1.16 fixed in 1.17.9, 1.18.1 | 10.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24921 | HIGH7.5 | stdlib v1.16 fixed in 1.16.15, 1.17.8 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27664 | HIGH7.5 | stdlib v1.16 fixed in 1.18.6, 1.19.1 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28131 | HIGH7.5 | stdlib v1.16 fixed in 1.17.12, 1.18.4 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28327 | HIGH7.5 | stdlib v1.16 fixed in 1.17.9, 1.18.1 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2879 | HIGH7.5 | stdlib v1.16 fixed in 1.18.7, 1.19.2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2880 | HIGH7.5 | stdlib v1.16 fixed in 1.18.7, 1.19.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29804 | HIGH7.5 | stdlib v1.16 fixed in 1.17.11, 1.18.3 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30630 | HIGH7.5 | stdlib v1.16 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30631 | HIGH7.5 | stdlib v1.16 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30632 | HIGH7.5 | stdlib v1.16 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30633 | HIGH7.5 | stdlib v1.16 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30634 | HIGH7.5 | stdlib v1.16 fixed in 1.17.11, 1.18.3 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30635 | HIGH7.5 | stdlib v1.16 fixed in 1.17.12, 1.18.4 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32189 | HIGH7.5 | stdlib v1.16 fixed in 1.17.13, 1.18.5 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41715 | HIGH7.5 | stdlib v1.16 fixed in 1.18.7, 1.19.2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41720 | HIGH7.5 | stdlib v1.16 fixed in 1.18.9, 1.19.4 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41722 | HIGH7.5 | stdlib v1.16 fixed in 1.19.6, 1.20.1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41723 | HIGH7.5 | stdlib v1.16 fixed in 1.19.6, 1.20.1 | 4.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41724 | HIGH7.5 | stdlib v1.16 fixed in 1.19.6, 1.20.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41725 | HIGH7.5 | stdlib v1.16 fixed in 1.19.6, 1.20.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24534 | HIGH7.5 | stdlib v1.16 fixed in 1.19.8, 1.20.3 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24536 | HIGH7.5 | stdlib v1.16 fixed in 1.19.8, 1.20.3 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24537 | HIGH7.5 | stdlib v1.16 fixed in 1.19.8, 1.20.3 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39325 | HIGH7.5 | stdlib v1.16 fixed in 1.20.10, 1.21.3 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45283 | HIGH7.5 | stdlib v1.16 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 fixed in 1.20.0 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34156 | HIGH7.5 | stdlib v1.16 fixed in 1.22.7, 1.23.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-61726 | HIGH7.5 | stdlib v1.16 fixed in 1.24.12, 1.25.6 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-41092 | HIGH7.5 | github.com/docker/cli v0.0.0-20200130152716-5d0cf8839492 fixed in 20.10.9 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11468 | HIGH7.5 | github.com/docker/distribution v0.0.0-20191216044856-a8371794149d fixed in 2.7.0-rc.0 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-13509 | HIGH7.5 | github.com/docker/docker v1.4.2-0.20200203170920-46ec8731fbce fixed in 18.09.8 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-16884 | HIGH7.5 | github.com/opencontainers/runc v0.1.1 fixed in 1.0.0-rc8.0.20190930145003-cad42f6e0932 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-27918 | HIGH7.5 | stdlib v1.15.7 fixed in 1.15.9, 1.16.1 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33196 | HIGH7.5 | stdlib v1.15.7 fixed in 1.15.13, 1.16.5 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33198 | HIGH7.5 | stdlib v1.15.7 fixed in 1.15.13, 1.16.5 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-39293 | HIGH7.5 | stdlib v1.15.7 fixed in 1.16.8, 1.17.1 | 6.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-41771 | HIGH7.5 | stdlib v1.15.7 fixed in 1.16.10, 1.17.3 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-41772 | HIGH7.5 | stdlib v1.15.7 fixed in 1.16.10, 1.17.3 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44716 | HIGH7.5 | stdlib v1.15.7 fixed in 1.16.12, 1.17.5 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23772 | HIGH7.5 | stdlib v1.15.7 fixed in 1.16.14, 1.17.7 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24675 | HIGH7.5 | stdlib v1.15.7 fixed in 1.17.9, 1.18.1 | 10.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24921 | HIGH7.5 | stdlib v1.15.7 fixed in 1.16.15, 1.17.8 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27664 | HIGH7.5 | stdlib v1.15.7 fixed in 1.18.6, 1.19.1 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28131 | HIGH7.5 | stdlib v1.15.7 fixed in 1.17.12, 1.18.4 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28327 | HIGH7.5 | stdlib v1.15.7 fixed in 1.17.9, 1.18.1 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2879 | HIGH7.5 | stdlib v1.15.7 fixed in 1.18.7, 1.19.2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2880 | HIGH7.5 | stdlib v1.15.7 fixed in 1.18.7, 1.19.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29804 | HIGH7.5 | stdlib v1.15.7 fixed in 1.17.11, 1.18.3 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30630 | HIGH7.5 | stdlib v1.15.7 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30631 | HIGH7.5 | stdlib v1.15.7 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30632 | HIGH7.5 | stdlib v1.15.7 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30633 | HIGH7.5 | stdlib v1.15.7 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30634 | HIGH7.5 | stdlib v1.15.7 fixed in 1.17.11, 1.18.3 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30635 | HIGH7.5 | stdlib v1.15.7 fixed in 1.17.12, 1.18.4 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32189 | HIGH7.5 | stdlib v1.15.7 fixed in 1.17.13, 1.18.5 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41715 | HIGH7.5 | stdlib v1.15.7 fixed in 1.18.7, 1.19.2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41720 | HIGH7.5 | stdlib v1.15.7 fixed in 1.18.9, 1.19.4 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41722 | HIGH7.5 | stdlib v1.15.7 fixed in 1.19.6, 1.20.1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41723 | HIGH7.5 | stdlib v1.15.7 fixed in 1.19.6, 1.20.1 | 4.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41724 | HIGH7.5 | stdlib v1.15.7 fixed in 1.19.6, 1.20.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41725 | HIGH7.5 | stdlib v1.15.7 fixed in 1.19.6, 1.20.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24534 | HIGH7.5 | stdlib v1.15.7 fixed in 1.19.8, 1.20.3 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24536 | HIGH7.5 | stdlib v1.15.7 fixed in 1.19.8, 1.20.3 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24537 | HIGH7.5 | stdlib v1.15.7 fixed in 1.19.8, 1.20.3 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39325 | HIGH7.5 | stdlib v1.15.7 fixed in 1.20.10, 1.21.3 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45283 | HIGH7.5 | stdlib v1.15.7 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.15.7 fixed in 1.20.0 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34156 | HIGH7.5 | stdlib v1.15.7 fixed in 1.22.7, 1.23.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-61726 | HIGH7.5 | stdlib v1.15.7 fixed in 1.24.12, 1.25.6 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2020-28362 | HIGH7.5 | stdlib v1.14.10 fixed in 1.14.12, 1.15.5 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-27918 | HIGH7.5 | stdlib v1.14.10 fixed in 1.15.9, 1.16.1 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33196 | HIGH7.5 | stdlib v1.14.10 fixed in 1.15.13, 1.16.5 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33198 | HIGH7.5 | stdlib v1.14.10 fixed in 1.15.13, 1.16.5 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-39293 | HIGH7.5 | stdlib v1.14.10 fixed in 1.16.8, 1.17.1 | 6.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-41771 | HIGH7.5 | stdlib v1.14.10 fixed in 1.16.10, 1.17.3 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-41772 | HIGH7.5 | stdlib v1.14.10 fixed in 1.16.10, 1.17.3 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44716 | HIGH7.5 | stdlib v1.14.10 fixed in 1.16.12, 1.17.5 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23772 | HIGH7.5 | stdlib v1.14.10 fixed in 1.16.14, 1.17.7 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24675 | HIGH7.5 | stdlib v1.14.10 fixed in 1.17.9, 1.18.1 | 10.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24921 | HIGH7.5 | stdlib v1.14.10 fixed in 1.16.15, 1.17.8 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27664 | HIGH7.5 | stdlib v1.14.10 fixed in 1.18.6, 1.19.1 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28131 | HIGH7.5 | stdlib v1.14.10 fixed in 1.17.12, 1.18.4 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28327 | HIGH7.5 | stdlib v1.14.10 fixed in 1.17.9, 1.18.1 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2879 | HIGH7.5 | stdlib v1.14.10 fixed in 1.18.7, 1.19.2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2880 | HIGH7.5 | stdlib v1.14.10 fixed in 1.18.7, 1.19.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29804 | HIGH7.5 | stdlib v1.14.10 fixed in 1.17.11, 1.18.3 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30630 | HIGH7.5 | stdlib v1.14.10 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30631 | HIGH7.5 | stdlib v1.14.10 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30632 | HIGH7.5 | stdlib v1.14.10 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30633 | HIGH7.5 | stdlib v1.14.10 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30634 | HIGH7.5 | stdlib v1.14.10 fixed in 1.17.11, 1.18.3 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30635 | HIGH7.5 | stdlib v1.14.10 fixed in 1.17.12, 1.18.4 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32189 | HIGH7.5 | stdlib v1.14.10 fixed in 1.17.13, 1.18.5 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41715 | HIGH7.5 | stdlib v1.14.10 fixed in 1.18.7, 1.19.2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41720 | HIGH7.5 | stdlib v1.14.10 fixed in 1.18.9, 1.19.4 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41722 | HIGH7.5 | stdlib v1.14.10 fixed in 1.19.6, 1.20.1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41723 | HIGH7.5 | stdlib v1.14.10 fixed in 1.19.6, 1.20.1 | 4.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41724 | HIGH7.5 | stdlib v1.14.10 fixed in 1.19.6, 1.20.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41725 | HIGH7.5 | stdlib v1.14.10 fixed in 1.19.6, 1.20.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24534 | HIGH7.5 | stdlib v1.14.10 fixed in 1.19.8, 1.20.3 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24536 | HIGH7.5 | stdlib v1.14.10 fixed in 1.19.8, 1.20.3 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24537 | HIGH7.5 | stdlib v1.14.10 fixed in 1.19.8, 1.20.3 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39325 | HIGH7.5 | stdlib v1.14.10 fixed in 1.20.10, 1.21.3 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45283 | HIGH7.5 | stdlib v1.14.10 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.14.10 fixed in 1.20.0 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34156 | HIGH7.5 | stdlib v1.14.10 fixed in 1.22.7, 1.23.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-61726 | HIGH7.5 | stdlib v1.14.10 fixed in 1.24.12, 1.25.6 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2020-29652 | HIGH7.5 | golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 fixed in 0.0.0-20201216223049-8b5274cf687f | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27191 | HIGH7.5 | golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 fixed in 0.0.0-20220314234659-1baeb1ce4c0b | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28948 | HIGH7.5 | gopkg.in/yaml.v3 v3.0.0-20200313102051-9f266ea9e77c fixed in 3.0.1 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-27918 | HIGH7.5 | stdlib v1.15.6 fixed in 1.15.9, 1.16.1 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33196 | HIGH7.5 | stdlib v1.15.6 fixed in 1.15.13, 1.16.5 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33198 | HIGH7.5 | stdlib v1.15.6 fixed in 1.15.13, 1.16.5 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-39293 | HIGH7.5 | stdlib v1.15.6 fixed in 1.16.8, 1.17.1 | 6.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-41771 | HIGH7.5 | stdlib v1.15.6 fixed in 1.16.10, 1.17.3 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-41772 | HIGH7.5 | stdlib v1.15.6 fixed in 1.16.10, 1.17.3 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44716 | HIGH7.5 | stdlib v1.15.6 fixed in 1.16.12, 1.17.5 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23772 | HIGH7.5 | stdlib v1.15.6 fixed in 1.16.14, 1.17.7 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24675 | HIGH7.5 | stdlib v1.15.6 fixed in 1.17.9, 1.18.1 | 10.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24921 | HIGH7.5 | stdlib v1.15.6 fixed in 1.16.15, 1.17.8 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27664 | HIGH7.5 | stdlib v1.15.6 fixed in 1.18.6, 1.19.1 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28131 | HIGH7.5 | stdlib v1.15.6 fixed in 1.17.12, 1.18.4 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28327 | HIGH7.5 | stdlib v1.15.6 fixed in 1.17.9, 1.18.1 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2879 | HIGH7.5 | stdlib v1.15.6 fixed in 1.18.7, 1.19.2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2880 | HIGH7.5 | stdlib v1.15.6 fixed in 1.18.7, 1.19.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29804 | HIGH7.5 | stdlib v1.15.6 fixed in 1.17.11, 1.18.3 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30630 | HIGH7.5 | stdlib v1.15.6 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30631 | HIGH7.5 | stdlib v1.15.6 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30632 | HIGH7.5 | stdlib v1.15.6 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30633 | HIGH7.5 | stdlib v1.15.6 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30634 | HIGH7.5 | stdlib v1.15.6 fixed in 1.17.11, 1.18.3 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30635 | HIGH7.5 | stdlib v1.15.6 fixed in 1.17.12, 1.18.4 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32189 | HIGH7.5 | stdlib v1.15.6 fixed in 1.17.13, 1.18.5 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41715 | HIGH7.5 | stdlib v1.15.6 fixed in 1.18.7, 1.19.2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41720 | HIGH7.5 | stdlib v1.15.6 fixed in 1.18.9, 1.19.4 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41722 | HIGH7.5 | stdlib v1.15.6 fixed in 1.19.6, 1.20.1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41723 | HIGH7.5 | stdlib v1.15.6 fixed in 1.19.6, 1.20.1 | 4.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41724 | HIGH7.5 | stdlib v1.15.6 fixed in 1.19.6, 1.20.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41725 | HIGH7.5 | stdlib v1.15.6 fixed in 1.19.6, 1.20.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24534 | HIGH7.5 | stdlib v1.15.6 fixed in 1.19.8, 1.20.3 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24536 | HIGH7.5 | stdlib v1.15.6 fixed in 1.19.8, 1.20.3 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24537 | HIGH7.5 | stdlib v1.15.6 fixed in 1.19.8, 1.20.3 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39325 | HIGH7.5 | stdlib v1.15.6 fixed in 1.20.10, 1.21.3 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45283 | HIGH7.5 | stdlib v1.15.6 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.15.6 fixed in 1.20.0 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34156 | HIGH7.5 | stdlib v1.15.6 fixed in 1.22.7, 1.23.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-61726 | HIGH7.5 | stdlib v1.15.6 fixed in 1.24.12, 1.25.6 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-39828 | HIGH7.48 | golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 fixed in 0.52.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39828 | HIGH7.48 | golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 fixed in 0.52.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39832 | HIGH7.39 | golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 fixed in 0.52.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-39832 | HIGH7.39 | golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 fixed in 0.52.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-33195 | HIGH7.3 | stdlib v1.16 fixed in 1.15.13, 1.16.5 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24539 | HIGH7.3 | stdlib v1.16 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29400 | HIGH7.3 | stdlib v1.16 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33195 | HIGH7.3 | stdlib v1.15.7 fixed in 1.15.13, 1.16.5 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24539 | HIGH7.3 | stdlib v1.15.7 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29400 | HIGH7.3 | stdlib v1.15.7 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33195 | HIGH7.3 | stdlib v1.14.10 fixed in 1.15.13, 1.16.5 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24539 | HIGH7.3 | stdlib v1.14.10 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29400 | HIGH7.3 | stdlib v1.14.10 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33195 | HIGH7.3 | stdlib v1.15.6 fixed in 1.15.13, 1.16.5 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24539 | HIGH7.3 | stdlib v1.15.6 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29400 | HIGH7.3 | stdlib v1.15.6 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1996 | HIGH7.28 | github.com/emicklei/go-restful v2.9.5+incompatible fixed in 2.16.0 | 2.7% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33186 | HIGH7.28 | google.golang.org/grpc v1.15.0 fixed in 1.79.3 | 1.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-23806 | HIGH7.28 | stdlib v1.16 fixed in 1.16.14, 1.17.7 | 3.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33186 | HIGH7.28 | google.golang.org/grpc v1.27.1 fixed in 1.79.3 | 1.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-23806 | HIGH7.28 | stdlib v1.15.7 fixed in 1.16.14, 1.17.7 | 3.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-23806 | HIGH7.28 | stdlib v1.14.10 fixed in 1.16.14, 1.17.7 | 3.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-23806 | HIGH7.28 | stdlib v1.15.6 fixed in 1.16.14, 1.17.7 | 3.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-39821 | MEDIUM6.97 | golang.org/x/net v0.0.0-20201110031124-69a78807bb2b fixed in 0.55.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-39831 | MEDIUM6.88 | golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 fixed in 0.52.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25681 | MEDIUM6.88 | golang.org/x/net v0.0.0-20201110031124-69a78807bb2b fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27136 | MEDIUM6.88 | golang.org/x/net v0.0.0-20201110031124-69a78807bb2b fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33997 | MEDIUM6.88 | github.com/docker/docker v1.4.2-0.20200203170920-46ec8731fbce fixed in 29.3.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39831 | MEDIUM6.88 | golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 fixed in 0.52.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-30580 | MEDIUM6.63 | stdlib v1.16 fixed in 1.17.11, 1.18.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-29403 | MEDIUM6.63 | stdlib v1.16 fixed in 1.19.10, 1.20.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39822 | MEDIUM6.63 | stdlib v1.16 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-25621 | MEDIUM6.63 | github.com/containerd/containerd v1.3.4 fixed in 1.7.29 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-41103 | MEDIUM6.63 | github.com/containerd/containerd v1.3.4 fixed in 1.4.11, 1.5.7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-25173 | MEDIUM6.63 | github.com/containerd/containerd v1.3.4 fixed in 1.5.18, 1.6.18 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-40635 | MEDIUM6.63 | github.com/containerd/containerd v1.3.4 fixed in 1.7.27, 1.6.38 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-24557 | MEDIUM6.63 | github.com/docker/docker v1.4.2-0.20200203170920-46ec8731fbce fixed in 24.0.9, 25.0.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-31133 | MEDIUM6.63 | github.com/opencontainers/runc v0.1.1 fixed in 1.2.8, 1.3.3, 1.4.0-rc.3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-29162 | MEDIUM6.63 | github.com/opencontainers/runc v0.1.1 fixed in 1.1.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-28642 | MEDIUM6.63 | github.com/opencontainers/runc v0.1.1 fixed in 1.1.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-30580 | MEDIUM6.63 | stdlib v1.15.7 fixed in 1.17.11, 1.18.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-29403 | MEDIUM6.63 | stdlib v1.15.7 fixed in 1.19.10, 1.20.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39822 | MEDIUM6.63 | stdlib v1.15.7 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-30580 | MEDIUM6.63 | stdlib v1.14.10 fixed in 1.17.11, 1.18.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-29403 | MEDIUM6.63 | stdlib v1.14.10 fixed in 1.19.10, 1.20.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39822 | MEDIUM6.63 | stdlib v1.14.10 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-30580 | MEDIUM6.63 | stdlib v1.15.6 fixed in 1.17.11, 1.18.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-29403 | MEDIUM6.63 | stdlib v1.15.6 fixed in 1.19.10, 1.20.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39822 | MEDIUM6.63 | stdlib v1.15.6 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.20.4 fixed in 1.27.0-alpha.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-25735 | MEDIUM6.5 | k8s.io/kubernetes v1.20.4 fixed in 1.20.6, 1.19.10, 1.18.18 | 5.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2727 | MEDIUM6.5 | k8s.io/kubernetes v1.20.4 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.20.4 fixed in 1.27.3, 1.26.6, 1.25.11, 1.24.15 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-34558 | MEDIUM6.5 | stdlib v1.16 fixed in 1.15.14, 1.16.6 | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1705 | MEDIUM6.5 | stdlib v1.16 fixed in 1.17.12, 1.18.4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32148 | MEDIUM6.5 | stdlib v1.16 fixed in 1.17.12, 1.18.4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29406 | MEDIUM6.5 | stdlib v1.16 fixed in 1.19.11, 1.20.6 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23471 | MEDIUM6.5 | github.com/containerd/containerd v1.3.4 fixed in 1.5.16, 1.6.12 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-34558 | MEDIUM6.5 | stdlib v1.15.7 fixed in 1.15.14, 1.16.6 | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1705 | MEDIUM6.5 | stdlib v1.15.7 fixed in 1.17.12, 1.18.4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32148 | MEDIUM6.5 | stdlib v1.15.7 fixed in 1.17.12, 1.18.4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29406 | MEDIUM6.5 | stdlib v1.15.7 fixed in 1.19.11, 1.20.6 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3114 | MEDIUM6.5 | stdlib v1.14.10 fixed in 1.14.14, 1.15.7 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-34558 | MEDIUM6.5 | stdlib v1.14.10 fixed in 1.15.14, 1.16.6 | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1705 | MEDIUM6.5 | stdlib v1.14.10 fixed in 1.17.12, 1.18.4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32148 | MEDIUM6.5 | stdlib v1.14.10 fixed in 1.17.12, 1.18.4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29406 | MEDIUM6.5 | stdlib v1.14.10 fixed in 1.19.11, 1.20.6 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3114 | MEDIUM6.5 | stdlib v1.15.6 fixed in 1.14.14, 1.15.7 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-34558 | MEDIUM6.5 | stdlib v1.15.6 fixed in 1.15.14, 1.16.6 | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1705 | MEDIUM6.5 | stdlib v1.15.6 fixed in 1.17.12, 1.18.4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32148 | MEDIUM6.5 | stdlib v1.15.6 fixed in 1.17.12, 1.18.4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29406 | MEDIUM6.5 | stdlib v1.15.6 fixed in 1.19.11, 1.20.6 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-65637 | MEDIUM6.38 | github.com/sirupsen/logrus v1.6.0 fixed in 1.8.3, 1.9.1, 1.9.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-43565 | MEDIUM6.38 | golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 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-20201002170205-7f63de1d35b0 fixed in 0.35.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-47913 | MEDIUM6.38 | golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 fixed in 0.43.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-39829 | MEDIUM6.38 | golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-39830 | MEDIUM6.38 | golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 fixed in 0.52.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-39835 | MEDIUM6.38 | golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46597 | MEDIUM6.38 | golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-45338 | MEDIUM6.38 | golang.org/x/net v0.0.0-20201110031124-69a78807bb2b fixed in 0.33.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | golang.org/x/net v0.0.0-20201110031124-69a78807bb2b 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-2023-49568 | MEDIUM6.38 | gopkg.in/src-d/go-git.v4 v4.13.1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-21614 | MEDIUM6.38 | gopkg.in/src-d/go-git.v4 v4.13.1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-41716 | MEDIUM6.38 | stdlib v1.16 fixed in 1.18.8, 1.19.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-61729 | MEDIUM6.38 | stdlib v1.16 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25679 | MEDIUM6.38 | stdlib v1.16 fixed in 1.25.8, 1.26.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-27145 | MEDIUM6.38 | stdlib v1.16 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32280 | MEDIUM6.38 | stdlib v1.16 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32281 | MEDIUM6.38 | stdlib v1.16 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32283 | MEDIUM6.38 | stdlib v1.16 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33811 | MEDIUM6.38 | stdlib v1.16 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | stdlib v1.16 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39820 | MEDIUM6.38 | stdlib v1.16 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39836 | MEDIUM6.38 | stdlib v1.16 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42499 | MEDIUM6.38 | stdlib v1.16 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42504 | MEDIUM6.38 | stdlib v1.16 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-58183 | MEDIUM6.38 | stdlib v1.16 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61728 | MEDIUM6.38 | stdlib v1.16 fixed in 1.24.12, 1.25.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2018-12608 | MEDIUM6.38 | github.com/docker/docker v1.4.2-0.20200203170920-46ec8731fbce fixed in 17.06.0-ce | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-41567 | MEDIUM6.38 | github.com/docker/docker v1.4.2-0.20200203170920-46ec8731fbce No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-29018 | MEDIUM6.38 | github.com/docker/docker v1.4.2-0.20200203170920-46ec8731fbce fixed in 26.0.0-rc3, 25.0.5, 23.0.11 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-52881 | MEDIUM6.38 | github.com/opencontainers/runc v0.1.1 fixed in 1.2.8, 1.3.3, 1.4.0-rc.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-65637 | MEDIUM6.38 | github.com/sirupsen/logrus v1.7.0 fixed in 1.8.3, 1.9.1, 1.9.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-41716 | MEDIUM6.38 | stdlib v1.15.7 fixed in 1.18.8, 1.19.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-61729 | MEDIUM6.38 | stdlib v1.15.7 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25679 | MEDIUM6.38 | stdlib v1.15.7 fixed in 1.25.8, 1.26.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-27145 | MEDIUM6.38 | stdlib v1.15.7 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32280 | MEDIUM6.38 | stdlib v1.15.7 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32281 | MEDIUM6.38 | stdlib v1.15.7 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32283 | MEDIUM6.38 | stdlib v1.15.7 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33811 | MEDIUM6.38 | stdlib v1.15.7 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | stdlib v1.15.7 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39820 | MEDIUM6.38 | stdlib v1.15.7 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39836 | MEDIUM6.38 | stdlib v1.15.7 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42499 | MEDIUM6.38 | stdlib v1.15.7 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42504 | MEDIUM6.38 | stdlib v1.15.7 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-58183 | MEDIUM6.38 | stdlib v1.15.7 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61728 | MEDIUM6.38 | stdlib v1.15.7 fixed in 1.24.12, 1.25.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-41716 | MEDIUM6.38 | stdlib v1.14.10 fixed in 1.18.8, 1.19.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-61729 | MEDIUM6.38 | stdlib v1.14.10 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25679 | MEDIUM6.38 | stdlib v1.14.10 fixed in 1.25.8, 1.26.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-27145 | MEDIUM6.38 | stdlib v1.14.10 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32280 | MEDIUM6.38 | stdlib v1.14.10 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32281 | MEDIUM6.38 | stdlib v1.14.10 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32283 | MEDIUM6.38 | stdlib v1.14.10 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33811 | MEDIUM6.38 | stdlib v1.14.10 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | stdlib v1.14.10 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39820 | MEDIUM6.38 | stdlib v1.14.10 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39836 | MEDIUM6.38 | stdlib v1.14.10 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42499 | MEDIUM6.38 | stdlib v1.14.10 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42504 | MEDIUM6.38 | stdlib v1.14.10 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-58183 | MEDIUM6.38 | stdlib v1.14.10 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61728 | MEDIUM6.38 | stdlib v1.14.10 fixed in 1.24.12, 1.25.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-43565 | MEDIUM6.38 | golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 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-20200622213623-75b288015ac9 fixed in 0.35.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-47913 | MEDIUM6.38 | golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 fixed in 0.43.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-39829 | MEDIUM6.38 | golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-39830 | MEDIUM6.38 | golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 fixed in 0.52.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-39835 | MEDIUM6.38 | golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46597 | MEDIUM6.38 | golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-22868 | MEDIUM6.38 | golang.org/x/oauth2 v0.0.0-20190604053449-0f29369cfe45 fixed in 0.27.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-41716 | MEDIUM6.38 | stdlib v1.15.6 fixed in 1.18.8, 1.19.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-61729 | MEDIUM6.38 | stdlib v1.15.6 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25679 | MEDIUM6.38 | stdlib v1.15.6 fixed in 1.25.8, 1.26.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-27145 | MEDIUM6.38 | stdlib v1.15.6 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32280 | MEDIUM6.38 | stdlib v1.15.6 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32281 | MEDIUM6.38 | stdlib v1.15.6 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32283 | MEDIUM6.38 | stdlib v1.15.6 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33811 | MEDIUM6.38 | stdlib v1.15.6 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | stdlib v1.15.6 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39820 | MEDIUM6.38 | stdlib v1.15.6 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39836 | MEDIUM6.38 | stdlib v1.15.6 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42499 | MEDIUM6.38 | stdlib v1.15.6 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42504 | MEDIUM6.38 | stdlib v1.15.6 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-58183 | MEDIUM6.38 | stdlib v1.15.6 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61728 | MEDIUM6.38 | stdlib v1.15.6 fixed in 1.24.12, 1.25.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-21334 | MEDIUM6.3 | github.com/containerd/containerd v1.3.4 fixed in 1.4.4, 1.3.10 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-32760 | MEDIUM6.3 | github.com/containerd/containerd v1.3.4 fixed in 1.4.8, 1.5.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-41091 | MEDIUM6.3 | github.com/docker/docker v1.4.2-0.20200203170920-46ec8731fbce fixed in 20.10.9 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42508 | MEDIUM6.29 | golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 fixed in 0.52.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42508 | MEDIUM6.29 | golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 fixed in 0.52.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42306 | MEDIUM6.12 | github.com/docker/docker v1.4.2-0.20200203170920-46ec8731fbce No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2015-3627 | MEDIUM6.12 | github.com/docker/docker v1.4.2-0.20200203170920-46ec8731fbce fixed in 1.6.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2020-13529 | MEDIUM6.1 | libsystemd0 246.6-1ubuntu1.3 fixed in 246.6-1ubuntu1.7 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-13529 | MEDIUM6.1 | libudev1 246.6-1ubuntu1.3 fixed in 246.6-1ubuntu1.7 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-46595 | MEDIUM6.03 | golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46595 | MEDIUM6.03 | golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-47907 | MEDIUM5.95 | stdlib v1.16 fixed in 1.23.12, 1.24.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-19921 | MEDIUM5.95 | github.com/opencontainers/runc v0.1.1 fixed in 1.0.0-rc9.0.20200122160610-2fc03cc11c77 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-47907 | MEDIUM5.95 | stdlib v1.15.7 fixed in 1.23.12, 1.24.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-47907 | MEDIUM5.95 | stdlib v1.14.10 fixed in 1.23.12, 1.24.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-47907 | MEDIUM5.95 | stdlib v1.15.6 fixed in 1.23.12, 1.24.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-31525 | MEDIUM5.9 | golang.org/x/net v0.0.0-20201110031124-69a78807bb2b fixed in 0.0.0-20210428140749-89ef3d95e781 | 3.7% 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.20.4 fixed in 1.29.13, 1.30.9, 1.31.5, 1.32.1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-31525 | MEDIUM5.9 | stdlib v1.16 fixed in 1.15.12, 1.16.4 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-36221 | MEDIUM5.9 | stdlib v1.16 fixed in 1.15.15, 1.16.7 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-24791 | MEDIUM5.9 | stdlib v1.16 fixed in 1.21.12, 1.22.5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34158 | MEDIUM5.9 | stdlib v1.16 fixed in 1.22.7, 1.23.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-31525 | MEDIUM5.9 | stdlib v1.15.7 fixed in 1.15.12, 1.16.4 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-36221 | MEDIUM5.9 | stdlib v1.15.7 fixed in 1.15.15, 1.16.7 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-24791 | MEDIUM5.9 | stdlib v1.15.7 fixed in 1.21.12, 1.22.5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34158 | MEDIUM5.9 | stdlib v1.15.7 fixed in 1.22.7, 1.23.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-31525 | MEDIUM5.9 | stdlib v1.14.10 fixed in 1.15.12, 1.16.4 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-36221 | MEDIUM5.9 | stdlib v1.14.10 fixed in 1.15.15, 1.16.7 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-24791 | MEDIUM5.9 | stdlib v1.14.10 fixed in 1.21.12, 1.22.5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34158 | MEDIUM5.9 | stdlib v1.14.10 fixed in 1.22.7, 1.23.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-31525 | MEDIUM5.9 | stdlib v1.15.6 fixed in 1.15.12, 1.16.4 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-36221 | MEDIUM5.9 | stdlib v1.15.6 fixed in 1.15.15, 1.16.7 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-24791 | MEDIUM5.9 | stdlib v1.15.6 fixed in 1.21.12, 1.22.5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34158 | MEDIUM5.9 | stdlib v1.15.6 fixed in 1.22.7, 1.23.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-4673 | MEDIUM5.78 | stdlib v1.16 fixed in 1.23.10, 1.24.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4673 | MEDIUM5.78 | stdlib v1.15.7 fixed in 1.23.10, 1.24.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4673 | MEDIUM5.78 | stdlib v1.14.10 fixed in 1.23.10, 1.24.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4673 | MEDIUM5.78 | stdlib v1.15.6 fixed in 1.23.10, 1.24.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-5187 | MEDIUM5.7 | k8s.io/kubernetes v1.20.4 fixed in 1.31.12, 1.32.8, 1.33.4 | 0.5% 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-2021-20329 | MEDIUM5.52 | go.mongodb.org/mongo-driver v1.1.2 fixed in 1.5.1 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-39827 | MEDIUM5.52 | golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 fixed in 0.52.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39834 | MEDIUM5.52 | golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-22872 | MEDIUM5.52 | golang.org/x/net v0.0.0-20201110031124-69a78807bb2b fixed in 0.38.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25680 | MEDIUM5.52 | golang.org/x/net v0.0.0-20201110031124-69a78807bb2b fixed in 0.55.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1767 | MEDIUM5.52 | k8s.io/kubernetes v1.20.4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-24785 | MEDIUM5.52 | stdlib v1.16 fixed in 1.21.8, 1.22.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-47906 | MEDIUM5.52 | stdlib v1.16 fixed in 1.23.12, 1.24.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61727 | MEDIUM5.52 | stdlib v1.16 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39825 | MEDIUM5.52 | stdlib v1.16 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-2253 | MEDIUM5.52 | github.com/docker/distribution v0.0.0-20191216044856-a8371794149d fixed in 2.8.2-beta.1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-24785 | MEDIUM5.52 | stdlib v1.15.7 fixed in 1.21.8, 1.22.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-47906 | MEDIUM5.52 | stdlib v1.15.7 fixed in 1.23.12, 1.24.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61727 | MEDIUM5.52 | stdlib v1.15.7 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39825 | MEDIUM5.52 | stdlib v1.15.7 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-24785 | MEDIUM5.52 | stdlib v1.14.10 fixed in 1.21.8, 1.22.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-47906 | MEDIUM5.52 | stdlib v1.14.10 fixed in 1.23.12, 1.24.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61727 | MEDIUM5.52 | stdlib v1.14.10 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39825 | MEDIUM5.52 | stdlib v1.14.10 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39827 | MEDIUM5.52 | golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 fixed in 0.52.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39834 | MEDIUM5.52 | golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-24785 | MEDIUM5.52 | stdlib v1.15.6 fixed in 1.21.8, 1.22.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-47906 | MEDIUM5.52 | stdlib v1.15.6 fixed in 1.23.12, 1.24.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61727 | MEDIUM5.52 | stdlib v1.15.6 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39825 | MEDIUM5.52 | stdlib v1.15.6 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-33910 | MEDIUM5.5 | libsystemd0 246.6-1ubuntu1.3 fixed in 246.6-1ubuntu1.7 | 8.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33910 | MEDIUM5.5 | libudev1 246.6-1ubuntu1.3 fixed in 246.6-1ubuntu1.7 | 8.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-27919 | MEDIUM5.5 | stdlib v1.16 fixed in 1.16.1 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-32282 | MEDIUM5.44 | stdlib v1.16 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2016-9962 | MEDIUM5.44 | github.com/opencontainers/runc v0.1.1 fixed in 1.0.0-rc3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32282 | MEDIUM5.44 | stdlib v1.15.7 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32282 | MEDIUM5.44 | stdlib v1.14.10 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32282 | MEDIUM5.44 | stdlib v1.15.6 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-24784 | MEDIUM5.4 | stdlib v1.16 fixed in 1.21.8, 1.22.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-24784 | MEDIUM5.4 | stdlib v1.15.7 fixed in 1.21.8, 1.22.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-24784 | MEDIUM5.4 | stdlib v1.14.10 fixed in 1.21.8, 1.22.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-24784 | MEDIUM5.4 | stdlib v1.15.6 fixed in 1.21.8, 1.22.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-25736 | MEDIUM5.35 | k8s.io/kubernetes v1.20.4 fixed in 1.21.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-36109 | MEDIUM5.35 | github.com/docker/docker v1.4.2-0.20200203170920-46ec8731fbce fixed in 20.10.18 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-41089 | MEDIUM5.35 | github.com/docker/docker v1.4.2-0.20200203170920-46ec8731fbce fixed in 20.10.9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-25809 | MEDIUM5.35 | github.com/opencontainers/runc v0.1.1 fixed in 1.1.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-41717 | MEDIUM5.3 | golang.org/x/net v0.0.0-20201110031124-69a78807bb2b fixed in 0.4.0 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29526 | MEDIUM5.3 | golang.org/x/sys v0.0.0-20201112073958-5cba982894dd fixed in 0.0.0-20220412211240-33da011f77ad | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33197 | MEDIUM5.3 | stdlib v1.16 fixed in 1.15.13, 1.16.5 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29526 | MEDIUM5.3 | stdlib v1.16 fixed in 1.17.10, 1.18.2 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41717 | MEDIUM5.3 | stdlib v1.16 fixed in 1.18.9, 1.19.4 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29409 | MEDIUM5.3 | stdlib v1.16 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 fixed in 1.20.12, 1.21.5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45289 | MEDIUM5.3 | stdlib v1.16 fixed in 1.21.8, 1.22.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45290 | MEDIUM5.3 | stdlib v1.16 fixed in 1.21.8, 1.22.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27534 | MEDIUM5.3 | github.com/docker/docker v1.4.2-0.20200203170920-46ec8731fbce fixed in 19.03.9 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33197 | MEDIUM5.3 | stdlib v1.15.7 fixed in 1.15.13, 1.16.5 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29526 | MEDIUM5.3 | stdlib v1.15.7 fixed in 1.17.10, 1.18.2 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41717 | MEDIUM5.3 | stdlib v1.15.7 fixed in 1.18.9, 1.19.4 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29409 | MEDIUM5.3 | stdlib v1.15.7 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.15.7 fixed in 1.20.12, 1.21.5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45289 | MEDIUM5.3 | stdlib v1.15.7 fixed in 1.21.8, 1.22.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45290 | MEDIUM5.3 | stdlib v1.15.7 fixed in 1.21.8, 1.22.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33197 | MEDIUM5.3 | stdlib v1.14.10 fixed in 1.15.13, 1.16.5 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29526 | MEDIUM5.3 | stdlib v1.14.10 fixed in 1.17.10, 1.18.2 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41717 | MEDIUM5.3 | stdlib v1.14.10 fixed in 1.18.9, 1.19.4 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29409 | MEDIUM5.3 | stdlib v1.14.10 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.14.10 fixed in 1.20.12, 1.21.5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45289 | MEDIUM5.3 | stdlib v1.14.10 fixed in 1.21.8, 1.22.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45290 | MEDIUM5.3 | stdlib v1.14.10 fixed in 1.21.8, 1.22.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29526 | MEDIUM5.3 | golang.org/x/sys v0.0.0-20200930185726-fdedc70b468f fixed in 0.0.0-20220412211240-33da011f77ad | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33197 | MEDIUM5.3 | stdlib v1.15.6 fixed in 1.15.13, 1.16.5 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29526 | MEDIUM5.3 | stdlib v1.15.6 fixed in 1.17.10, 1.18.2 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41717 | MEDIUM5.3 | stdlib v1.15.6 fixed in 1.18.9, 1.19.4 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29409 | MEDIUM5.3 | stdlib v1.15.6 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.15.6 fixed in 1.20.12, 1.21.5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45289 | MEDIUM5.3 | stdlib v1.15.6 fixed in 1.21.8, 1.22.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45290 | MEDIUM5.3 | stdlib v1.15.6 fixed in 1.21.8, 1.22.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-0426 | MEDIUM5.27 | k8s.io/kubernetes v1.20.4 fixed in 1.32.2, 1.31.6, 1.30.10, 1.29.14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-15257 | MEDIUM5.2 | github.com/containerd/containerd v1.3.4 fixed in 1.3.9, 1.4.3 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3978 | MEDIUM5.18 | golang.org/x/net v0.0.0-20201110031124-69a78807bb2b fixed in 0.13.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-42502 | MEDIUM5.18 | golang.org/x/net v0.0.0-20201110031124-69a78807bb2b fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-5321 | MEDIUM5.18 | k8s.io/kubernetes v1.20.4 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 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-39319 | MEDIUM5.18 | stdlib v1.16 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-32289 | MEDIUM5.18 | stdlib v1.16 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-39318 | MEDIUM5.18 | stdlib v1.15.7 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-39319 | MEDIUM5.18 | stdlib v1.15.7 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-32289 | MEDIUM5.18 | stdlib v1.15.7 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-39318 | MEDIUM5.18 | stdlib v1.14.10 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-39319 | MEDIUM5.18 | stdlib v1.14.10 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-32289 | MEDIUM5.18 | stdlib v1.14.10 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-39318 | MEDIUM5.18 | stdlib v1.15.6 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-39319 | MEDIUM5.18 | stdlib v1.15.6 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-32289 | MEDIUM5.18 | stdlib v1.15.6 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-24783 | MEDIUM5.02 | stdlib v1.16 fixed in 1.21.8, 1.22.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-34155 | MEDIUM5.02 | stdlib v1.16 fixed in 1.22.7, 1.23.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-45336 | MEDIUM5.02 | stdlib v1.16 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-24769 | MEDIUM5.02 | github.com/docker/docker v1.4.2-0.20200203170920-46ec8731fbce fixed in 20.10.14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-24783 | MEDIUM5.02 | stdlib v1.15.7 fixed in 1.21.8, 1.22.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-34155 | MEDIUM5.02 | stdlib v1.15.7 fixed in 1.22.7, 1.23.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-45336 | MEDIUM5.02 | stdlib v1.15.7 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-24783 | MEDIUM5.02 | stdlib v1.14.10 fixed in 1.21.8, 1.22.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-34155 | MEDIUM5.02 | stdlib v1.14.10 fixed in 1.22.7, 1.23.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-45336 | MEDIUM5.02 | stdlib v1.14.10 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-24783 | MEDIUM5.02 | stdlib v1.15.6 fixed in 1.21.8, 1.22.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-34155 | MEDIUM5.02 | stdlib v1.15.6 fixed in 1.22.7, 1.23.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-45336 | MEDIUM5.02 | stdlib v1.15.6 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2020-8554 | MEDIUM5 | k8s.io/kubernetes v1.20.4 No fix yet | 9.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-43784 | MEDIUM5 | github.com/opencontainers/runc v0.1.1 fixed in 1.0.3 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13281 | MEDIUM4.93 | k8s.io/kubernetes v1.20.4 fixed in 1.32.10, 1.33.6, 1.34.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-25737 | MEDIUM4.8 | k8s.io/kubernetes v1.20.4 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 fixed in 1.16.12, 1.17.5 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44717 | MEDIUM4.8 | stdlib v1.15.7 fixed in 1.16.12, 1.17.5 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44717 | MEDIUM4.8 | stdlib v1.14.10 fixed in 1.16.12, 1.17.5 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44717 | MEDIUM4.8 | stdlib v1.15.6 fixed in 1.16.12, 1.17.5 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-39833 | MEDIUM4.67 | golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 fixed in 0.52.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-2431 | MEDIUM4.67 | k8s.io/kubernetes v1.20.4 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 fixed in 1.17.12, 1.18.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-24789 | MEDIUM4.67 | stdlib v1.16 fixed in 1.21.11, 1.22.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32288 | MEDIUM4.67 | stdlib v1.16 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-31030 | MEDIUM4.67 | github.com/containerd/containerd v1.3.4 fixed in 1.5.13, 1.6.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-25153 | MEDIUM4.67 | github.com/containerd/containerd v1.3.4 fixed in 1.5.18, 1.6.18 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-64329 | MEDIUM4.67 | github.com/containerd/containerd v1.3.4 fixed in 1.7.29 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-1962 | MEDIUM4.67 | stdlib v1.15.7 fixed in 1.17.12, 1.18.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-24789 | MEDIUM4.67 | stdlib v1.15.7 fixed in 1.21.11, 1.22.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32288 | MEDIUM4.67 | stdlib v1.15.7 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-1962 | MEDIUM4.67 | stdlib v1.14.10 fixed in 1.17.12, 1.18.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-24789 | MEDIUM4.67 | stdlib v1.14.10 fixed in 1.21.11, 1.22.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32288 | MEDIUM4.67 | stdlib v1.14.10 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39833 | MEDIUM4.67 | golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 fixed in 0.52.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-8565 | MEDIUM4.67 | k8s.io/client-go v0.18.10 fixed in 0.19.6, 0.20.0-alpha.2, 0.18.14, 0.17.16 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-1962 | MEDIUM4.67 | stdlib v1.15.6 fixed in 1.17.12, 1.18.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-24789 | MEDIUM4.67 | stdlib v1.15.6 fixed in 1.21.11, 1.22.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32288 | MEDIUM4.67 | stdlib v1.15.6 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-20201110031124-69a78807bb2b fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22871 | MEDIUM4.59 | stdlib v1.16 fixed in 1.23.8, 1.24.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-27142 | MEDIUM4.59 | stdlib v1.16 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39823 | MEDIUM4.59 | stdlib v1.16 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39826 | MEDIUM4.59 | stdlib v1.16 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-22871 | MEDIUM4.59 | stdlib v1.15.7 fixed in 1.23.8, 1.24.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-27142 | MEDIUM4.59 | stdlib v1.15.7 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39823 | MEDIUM4.59 | stdlib v1.15.7 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39826 | MEDIUM4.59 | stdlib v1.15.7 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-22871 | MEDIUM4.59 | stdlib v1.14.10 fixed in 1.23.8, 1.24.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-27142 | MEDIUM4.59 | stdlib v1.14.10 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39823 | MEDIUM4.59 | stdlib v1.14.10 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39826 | MEDIUM4.59 | stdlib v1.14.10 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-22871 | MEDIUM4.59 | stdlib v1.15.6 fixed in 1.23.8, 1.24.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-27142 | MEDIUM4.59 | stdlib v1.15.6 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39823 | MEDIUM4.59 | stdlib v1.15.6 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39826 | MEDIUM4.59 | stdlib v1.15.6 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-47914 | MEDIUM4.5 | golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58181 | MEDIUM4.5 | golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 fixed in 0.45.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46598 | MEDIUM4.5 | golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 fixed in 0.52.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-47911 | MEDIUM4.5 | golang.org/x/net v0.0.0-20201110031124-69a78807bb2b fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58190 | MEDIUM4.5 | golang.org/x/net v0.0.0-20201110031124-69a78807bb2b fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-24532 | MEDIUM4.5 | stdlib v1.16 fixed in 1.19.7, 1.20.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-45284 | MEDIUM4.5 | stdlib v1.16 fixed in 1.20.11, 1.21.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-22866 | MEDIUM4.5 | stdlib v1.16 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 fixed in 1.23.9, 1.24.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-47912 | MEDIUM4.5 | stdlib v1.16 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58185 | MEDIUM4.5 | stdlib v1.16 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58187 | MEDIUM4.5 | stdlib v1.16 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58188 | MEDIUM4.5 | stdlib v1.16 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58189 | MEDIUM4.5 | stdlib v1.16 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61723 | MEDIUM4.5 | stdlib v1.16 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61724 | MEDIUM4.5 | stdlib v1.16 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61725 | MEDIUM4.5 | stdlib v1.16 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61730 | MEDIUM4.5 | stdlib v1.16 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42505 | MEDIUM4.5 | stdlib v1.16 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 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58186 | MEDIUM4.5 | stdlib v1.16 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-24532 | MEDIUM4.5 | stdlib v1.15.7 fixed in 1.19.7, 1.20.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-45284 | MEDIUM4.5 | stdlib v1.15.7 fixed in 1.20.11, 1.21.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-22866 | MEDIUM4.5 | stdlib v1.15.7 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.15.7 fixed in 1.23.9, 1.24.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-47912 | MEDIUM4.5 | stdlib v1.15.7 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58185 | MEDIUM4.5 | stdlib v1.15.7 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58187 | MEDIUM4.5 | stdlib v1.15.7 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58188 | MEDIUM4.5 | stdlib v1.15.7 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58189 | MEDIUM4.5 | stdlib v1.15.7 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61723 | MEDIUM4.5 | stdlib v1.15.7 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61724 | MEDIUM4.5 | stdlib v1.15.7 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61725 | MEDIUM4.5 | stdlib v1.15.7 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61730 | MEDIUM4.5 | stdlib v1.15.7 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42505 | MEDIUM4.5 | stdlib v1.15.7 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.15.7 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58186 | MEDIUM4.5 | stdlib v1.15.7 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-24532 | MEDIUM4.5 | stdlib v1.14.10 fixed in 1.19.7, 1.20.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-45284 | MEDIUM4.5 | stdlib v1.14.10 fixed in 1.20.11, 1.21.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-22866 | MEDIUM4.5 | stdlib v1.14.10 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.14.10 fixed in 1.23.9, 1.24.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-47912 | MEDIUM4.5 | stdlib v1.14.10 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58185 | MEDIUM4.5 | stdlib v1.14.10 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58187 | MEDIUM4.5 | stdlib v1.14.10 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58188 | MEDIUM4.5 | stdlib v1.14.10 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58189 | MEDIUM4.5 | stdlib v1.14.10 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61723 | MEDIUM4.5 | stdlib v1.14.10 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61724 | MEDIUM4.5 | stdlib v1.14.10 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61725 | MEDIUM4.5 | stdlib v1.14.10 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61730 | MEDIUM4.5 | stdlib v1.14.10 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42505 | MEDIUM4.5 | stdlib v1.14.10 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.14.10 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58186 | MEDIUM4.5 | stdlib v1.14.10 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58058 | MEDIUM4.5 | github.com/ulikunitz/xz v0.5.8 fixed in 0.5.15 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-47914 | MEDIUM4.5 | golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58181 | MEDIUM4.5 | golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 fixed in 0.45.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46598 | MEDIUM4.5 | golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 fixed in 0.52.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-24532 | MEDIUM4.5 | stdlib v1.15.6 fixed in 1.19.7, 1.20.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-45284 | MEDIUM4.5 | stdlib v1.15.6 fixed in 1.20.11, 1.21.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-22866 | MEDIUM4.5 | stdlib v1.15.6 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.15.6 fixed in 1.23.9, 1.24.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-47912 | MEDIUM4.5 | stdlib v1.15.6 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58185 | MEDIUM4.5 | stdlib v1.15.6 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58187 | MEDIUM4.5 | stdlib v1.15.6 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58188 | MEDIUM4.5 | stdlib v1.15.6 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58189 | MEDIUM4.5 | stdlib v1.15.6 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61723 | MEDIUM4.5 | stdlib v1.15.6 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61724 | MEDIUM4.5 | stdlib v1.15.6 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61725 | MEDIUM4.5 | stdlib v1.15.6 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61730 | MEDIUM4.5 | stdlib v1.15.6 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42505 | MEDIUM4.5 | stdlib v1.15.6 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.15.6 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58186 | MEDIUM4.5 | stdlib v1.15.6 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-54410 | MEDIUM4.42 | github.com/docker/docker v1.4.2-0.20200203170920-46ec8731fbce fixed in 25.0.13, 28.0.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-28180 | MEDIUM4.3 | gopkg.in/square/go-jose.v2 v2.2.2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-8561 | MEDIUM4.1 | k8s.io/kubernetes v1.20.4 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-39304 | MEDIUM4 | github.com/bradleyfalzon/ghinstallation v1.1.1 fixed in 2.0.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-30922 | LOW3.82 | pyasn1 0.4.8 fixed in 0.6.3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-59885 | LOW3.82 | pyasn1 0.4.8 fixed in 0.6.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59886 | LOW3.82 | pyasn1 0.4.8 fixed in 0.6.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66471 | LOW3.82 | urllib3 1.25.11 fixed in 2.6.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-22870 | LOW3.74 | golang.org/x/net v0.0.0-20201110031124-69a78807bb2b fixed in 0.36.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-22870 | LOW3.74 | stdlib v1.16 fixed in 1.23.7, 1.24.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-22870 | LOW3.74 | stdlib v1.15.7 fixed in 1.23.7, 1.24.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-22870 | LOW3.74 | stdlib v1.14.10 fixed in 1.23.7, 1.24.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-22870 | LOW3.74 | stdlib v1.15.6 fixed in 1.23.7, 1.24.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-3676 | LOW3.64 | k8s.io/kubernetes v1.20.4 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-2024-45341 | LOW3.57 | stdlib v1.16 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-45341 | LOW3.57 | stdlib v1.15.7 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-45341 | LOW3.57 | stdlib v1.14.10 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-45341 | LOW3.57 | stdlib v1.15.6 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-25658 | LOW3.54 | rsa 3.4.2 fixed in 4.7 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3520 | LOW3.53 | liblz4-1 1.9.2-2 fixed in 1.9.2-2ubuntu0.20.10.1 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2021-29921 | LOW3.53 | libpython3.8 3.8.6-1ubuntu0.2 fixed in 3.8.6-1ubuntu0.3 | 6.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-29921 | LOW3.53 | libpython3.8-dev 3.8.6-1ubuntu0.2 fixed in 3.8.6-1ubuntu0.3 | 6.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-29921 | LOW3.53 | libpython3.8-minimal 3.8.6-1ubuntu0.2 fixed in 3.8.6-1ubuntu0.3 | 6.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-29921 | LOW3.53 | libpython3.8-stdlib 3.8.6-1ubuntu0.2 fixed in 3.8.6-1ubuntu0.3 | 6.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-29921 | LOW3.53 | python3.8 3.8.6-1ubuntu0.2 fixed in 3.8.6-1ubuntu0.3 | 6.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-29921 | LOW3.53 | python3.8-dev 3.8.6-1ubuntu0.2 fixed in 3.8.6-1ubuntu0.3 | 6.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-29921 | LOW3.53 | python3.8-minimal 3.8.6-1ubuntu0.2 fixed in 3.8.6-1ubuntu0.3 | 6.8% Low-Moderate Risk | Post-Exploit |
| CVE-2020-14343 | LOW3.53 | PyYAML 5.3.1 fixed in 5.4 | 6.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-21235 | LOW3.53 | github.com/Masterminds/vcs v1.13.1 fixed in 1.13.2 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-41568 | LOW3.31 | github.com/docker/docker v1.4.2-0.20200203170920-46ec8731fbce No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-4238 | LOW3.28 | github.com/Masterminds/goutils v1.1.0 fixed in 1.1.1 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34040 | LOW3.23 | github.com/docker/docker v1.4.2-0.20200203170920-46ec8731fbce fixed in 29.3.1 | 10.1% High Exploitation Risk | Post-Exploit |
| CVE-2023-3955 | LOW3.17 | k8s.io/kubernetes v1.20.4 fixed in 1.28.1, 1.27.5, 1.26.8, 1.25.13, 1.24.17 | 3.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5528 | LOW3.17 | k8s.io/kubernetes v1.20.4 fixed in 1.28.4, 1.27.8, 1.26.11, 1.25.16 | 3.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-50181 | LOW3.11 | urllib3 1.25.11 fixed in 2.5.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2020-8562 | LOW3.1 | k8s.io/kubernetes v1.20.4 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-25740 | LOW3.1 | k8s.io/kubernetes v1.20.4 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3631 | LOW3.06 | github.com/docker/docker v1.4.2-0.20200203170920-46ec8731fbce fixed in 1.6.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-45310 | LOW3.06 | github.com/opencontainers/runc v0.1.1 fixed in 1.1.14, 1.2.0-rc.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41579 | LOW3.06 | github.com/opencontainers/runc v0.1.1 fixed in 1.3.6, 1.4.3, 1.5.0-rc.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59884 | LOW3.01 | pyasn1 0.4.8 fixed in 0.6.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-43804 | LOW2.92 | urllib3 1.25.11 fixed in 2.0.6, 1.26.17 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-13769 | LOW2.8 | awscli 1.18.80 fixed in 1.44.78 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2020-13757 | LOW2.7 | rsa 3.4.2 fixed in 4.1 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2021-33503 | LOW2.7 | urllib3 1.25.11 fixed in 1.26.5 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-21441 | LOW2.7 | urllib3 1.25.11 fixed in 2.6.3 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-44431 | LOW2.7 | urllib3 1.25.11 fixed in 2.7.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-3177 | LOW2.7 | k8s.io/kubernetes v1.20.4 fixed in 1.27.13, 1.29.4, 1.28.9 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30629 | LOW2.63 | stdlib v1.16 fixed in 1.17.11, 1.18.3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-30629 | LOW2.63 | stdlib v1.15.7 fixed in 1.17.11, 1.18.3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-30629 | LOW2.63 | stdlib v1.14.10 fixed in 1.17.11, 1.18.3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-30629 | LOW2.63 | stdlib v1.15.6 fixed in 1.17.11, 1.18.3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-25743 | LOW2.55 | k8s.io/kubernetes v1.20.4 fixed in 1.26.0-alpha.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-37891 | LOW2.34 | urllib3 1.25.11 fixed in 1.26.19, 2.2.2 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-66418 | LOW2.29 | urllib3 1.25.11 fixed in 2.6.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-45803 | LOW2.14 | urllib3 1.25.11 fixed in 2.0.7, 1.26.18 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-27139 | LOW2.12 | stdlib v1.16 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27139 | LOW2.12 | stdlib v1.15.7 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27139 | LOW2.12 | stdlib v1.14.10 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27139 | LOW2.12 | stdlib v1.15.6 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-31535 | NONE0 | libx11-6 2:1.6.12-1 fixed in 2:1.6.12-1ubuntu0.1 | 10.6% High Exploitation Risk | Not Applicable |
| CVE-2021-31535 | NONE0 | libx11-data 2:1.6.12-1 fixed in 2:1.6.12-1ubuntu0.1 | 10.6% High Exploitation Risk | Not Applicable |
| CVE-2021-28660 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-55.62 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-22555 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-55.62 | 78.7% Actively Exploited | Not Applicable |
| CVE-2021-33909 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-63.71 | 9.7% Low-Moderate Risk | Not Applicable |
| CVE-2020-25670 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-59.66 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2020-25671 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-59.66 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-33033 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-55.62 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-33034 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-61.68 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2021-3483 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-55.62 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-28952 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-55.62 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-25672 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-59.66 | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-3506 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-61.68 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-3609 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-59.66 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-23133 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-59.66 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-31440 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-59.66 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2021-32399 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-61.68 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-28972 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-55.62 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2021-31916 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-55.62 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2020-26141 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-59.66 | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2020-26145 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-59.66 | 3.5% Low-Moderate Risk | Not Applicable |
| CVE-2021-28038 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-55.62 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-28688 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-55.62 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-30002 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-55.62 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-25673 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-59.66 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-28950 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-55.62 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-28971 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-55.62 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-29155 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-59.66 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-31829 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-59.66 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-29647 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-55.62 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-26147 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-59.66 | 7.6% Low-Moderate Risk | Not Applicable |
| CVE-2020-26139 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-59.66 | 6.5% Low-Moderate Risk | Not Applicable |
| CVE-2021-28964 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-55.62 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-23134 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-61.68 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-24586 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-59.66 | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2020-24588 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-59.66 | 3.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-24587 | NONE0 | linux-libc-dev 5.8.0-53.60 fixed in 5.8.0-59.66 | 2.6% Low-Moderate Risk | Not Applicable |
| GHSA-747p-wmpv-9c78 | NONE0 | awscli 1.18.80 fixed in 1.44.38 | — | Not Applicable |
| GHSA-274v-mgcv-cm8j | NONE0 | github.com/argoproj/gitops-engine v0.3.2 fixed in 0.7.1-0.20250129155113-4c6e03c463141 | — | Not Applicable |
| GHSA-qq97-vm5h-rrhg | NONE0 | github.com/docker/distribution v2.7.1+incompatible fixed in 2.8.0 | — | Not Applicable |
| CVE-2026-2303 | NONE0 | go.mongodb.org/mongo-driver v1.1.2 fixed in 1.17.7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-30636 | NONE0 | golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 fixed in 0.0.0-20220525230936-793ad666bf5e | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46600 | NONE0 | golang.org/x/net v0.0.0-20201110031124-69a78807bb2b fixed in 0.56.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39824 | NONE0 | golang.org/x/sys v0.0.0-20201112073958-5cba982894dd fixed in 0.44.0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56852 | NONE0 | golang.org/x/text v0.3.4 fixed in 0.39.0 | 0.4% Theoretical Threat | Not Applicable |
| GHSA-hrxh-6v49-42gf | NONE0 | google.golang.org/grpc v1.15.0 fixed in 1.82.1 | — | Not Applicable |
| GHSA-m425-mq94-257g | NONE0 | google.golang.org/grpc v1.15.0 fixed in 1.56.3, 1.57.1, 1.58.3 | — | Not Applicable |
| CVE-2025-0913 | NONE0 | stdlib v1.16 fixed in 1.23.10, 1.24.4 | 0.2% Theoretical Threat | Not Applicable |
| GHSA-7ww5-4wqc-m92c | NONE0 | github.com/containerd/containerd v1.3.4 fixed in 1.6.26, 1.7.11 | — | Not Applicable |
| GHSA-5j5w-g665-5m35 | NONE0 | github.com/containerd/containerd v1.3.4 fixed in 1.4.12, 1.5.8 | — | Not Applicable |
| GHSA-c9cp-9c75-9v8c | NONE0 | github.com/containerd/containerd v1.3.4 fixed in 1.5.11, 1.6.2 | — | Not Applicable |
| GHSA-6xv5-86q9-7xr8 | NONE0 | github.com/cyphar/filepath-securejoin v0.2.2 fixed in 0.2.4 | — | Not Applicable |
| GHSA-qq97-vm5h-rrhg | NONE0 | github.com/docker/distribution v0.0.0-20191216044856-a8371794149d fixed in 2.8.0 | — | Not Applicable |
| GHSA-jq35-85cj-fj4p | NONE0 | github.com/docker/docker v1.4.2-0.20200203170920-46ec8731fbce fixed in 24.0.7, 23.0.8, 20.10.27 | — | Not Applicable |
| GHSA-xmmx-7jpf-fx42 | NONE0 | github.com/docker/docker v1.4.2-0.20200203170920-46ec8731fbce fixed in 20.10.11 | — | Not Applicable |
| GHSA-vp35-85q5-9f25 | NONE0 | github.com/docker/docker v1.4.2-0.20200203170920-46ec8731fbce fixed in 20.10.20 | — | Not Applicable |
| GHSA-77vh-xpmg-72qh | NONE0 | github.com/opencontainers/image-spec v1.0.1 fixed in 1.0.2 | — | Not Applicable |
| GHSA-g54h-m393-cpwq | NONE0 | github.com/opencontainers/runc v0.1.1 fixed in 1.0.0-rc91 | — | 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.15.7 fixed in 1.23.10, 1.24.4 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-0913 | NONE0 | stdlib v1.14.10 fixed in 1.23.10, 1.24.4 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-30636 | NONE0 | golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 fixed in 0.0.0-20220525230936-793ad666bf5e | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-39824 | NONE0 | golang.org/x/sys v0.0.0-20200930185726-fdedc70b468f fixed in 0.44.0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-0913 | NONE0 | stdlib v1.15.6 fixed in 1.23.10, 1.24.4 | 0.2% Theoretical Threat | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.