Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker could exploit TLS resumption issues to bypass certificate validation or use SQL injection to gain unauthorized access to Vault's backend data, potentially exposing secrets. Upgrading affected libraries to patched versions (e.g., pgx 5.9.2) would fully eliminate some of these risks. Note that some findings only apply when non-default protocols are enabled (e.g., CVE-2026-41889 requires the simple query protocol).
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| 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.5 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-41889 | HIGH8.33 | github.com/jackc/pgx v3.3.0+incompatible No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-45337 | HIGH8.2 | golang.org/x/crypto v0.0.0-20210513164829-c07d793c2f9a fixed in 0.31.0 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-27304 | HIGH8.1 | github.com/jackc/pgx v3.3.0+incompatible fixed in 4.18.2, 5.5.4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-0377 | HIGH7.73 | github.com/hashicorp/go-slug v0.4.1 fixed in 0.16.3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2020-15114 | HIGH7.7 | go.etcd.io/etcd v0.5.0-alpha.5.0.20200425165423-262c93980547 fixed in 3.4.10, 3.3.23 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-48795 | HIGH7.67 | golang.org/x/crypto v0.0.0-20210513164829-c07d793c2f9a fixed in 0.17.0 | 93.3% Actively Exploited | Directly Exposed |
| CVE-2026-32952 | HIGH7.5 | github.com/Azure/go-ntlmssp v0.0.0-20200615164410-66371956d46c fixed in 0.1.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-13509 | HIGH7.5 | github.com/docker/docker v17.12.0-ce-rc1.0.20200309214505-aa6a9891b09c+incompatible fixed in 18.09.8 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-29529 | HIGH7.5 | github.com/hashicorp/go-slug v0.4.1 fixed in 0.5.0 | 2.8% 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-2021-29482 | HIGH7.5 | github.com/ulikunitz/xz v0.5.7 fixed in 0.5.8 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27191 | HIGH7.5 | golang.org/x/crypto v0.0.0-20210513164829-c07d793c2f9a 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-20210510120150-4163338589ed 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-20210510120150-4163338589ed 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-20210510120150-4163338589ed 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-20210510120150-4163338589ed fixed in 0.7.0 | 4.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39325 | HIGH7.5 | golang.org/x/net v0.0.0-20210510120150-4163338589ed fixed in 0.17.0 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-38561 | HIGH7.5 | golang.org/x/text v0.3.6 fixed in 0.3.7 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32149 | HIGH7.5 | golang.org/x/text v0.3.6 fixed in 0.3.8 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28948 | HIGH7.5 | gopkg.in/yaml.v3 v3.0.0-20210107192922-496545a6307b fixed in 3.0.1 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-39293 | HIGH7.5 | stdlib v1.16.5 fixed in 1.16.8, 1.17.1 | 6.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-41771 | HIGH7.5 | stdlib v1.16.5 fixed in 1.16.10, 1.17.3 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-41772 | HIGH7.5 | stdlib v1.16.5 fixed in 1.16.10, 1.17.3 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44716 | HIGH7.5 | stdlib v1.16.5 fixed in 1.16.12, 1.17.5 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23772 | HIGH7.5 | stdlib v1.16.5 fixed in 1.16.14, 1.17.7 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24675 | HIGH7.5 | stdlib v1.16.5 fixed in 1.17.9, 1.18.1 | 10.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24921 | HIGH7.5 | stdlib v1.16.5 fixed in 1.16.15, 1.17.8 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27664 | HIGH7.5 | stdlib v1.16.5 fixed in 1.18.6, 1.19.1 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28131 | HIGH7.5 | stdlib v1.16.5 fixed in 1.17.12, 1.18.4 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28327 | HIGH7.5 | stdlib v1.16.5 fixed in 1.17.9, 1.18.1 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2879 | HIGH7.5 | stdlib v1.16.5 fixed in 1.18.7, 1.19.2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2880 | HIGH7.5 | stdlib v1.16.5 fixed in 1.18.7, 1.19.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29804 | HIGH7.5 | stdlib v1.16.5 fixed in 1.17.11, 1.18.3 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30630 | HIGH7.5 | stdlib v1.16.5 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30631 | HIGH7.5 | stdlib v1.16.5 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30632 | HIGH7.5 | stdlib v1.16.5 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30633 | HIGH7.5 | stdlib v1.16.5 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30634 | HIGH7.5 | stdlib v1.16.5 fixed in 1.17.11, 1.18.3 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30635 | HIGH7.5 | stdlib v1.16.5 fixed in 1.17.12, 1.18.4 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32189 | HIGH7.5 | stdlib v1.16.5 fixed in 1.17.13, 1.18.5 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41715 | HIGH7.5 | stdlib v1.16.5 fixed in 1.18.7, 1.19.2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41720 | HIGH7.5 | stdlib v1.16.5 fixed in 1.18.9, 1.19.4 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41722 | HIGH7.5 | stdlib v1.16.5 fixed in 1.19.6, 1.20.1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41723 | HIGH7.5 | stdlib v1.16.5 fixed in 1.19.6, 1.20.1 | 4.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41724 | HIGH7.5 | stdlib v1.16.5 fixed in 1.19.6, 1.20.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41725 | HIGH7.5 | stdlib v1.16.5 fixed in 1.19.6, 1.20.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24534 | HIGH7.5 | stdlib v1.16.5 fixed in 1.19.8, 1.20.3 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24536 | HIGH7.5 | stdlib v1.16.5 fixed in 1.19.8, 1.20.3 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24537 | HIGH7.5 | stdlib v1.16.5 fixed in 1.19.8, 1.20.3 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39325 | HIGH7.5 | stdlib v1.16.5 fixed in 1.20.10, 1.21.3 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45283 | HIGH7.5 | stdlib v1.16.5 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.5 fixed in 1.20.0 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34156 | HIGH7.5 | stdlib v1.16.5 fixed in 1.22.7, 1.23.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-61726 | HIGH7.5 | stdlib v1.16.5 fixed in 1.24.12, 1.25.6 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33413 | HIGH7.48 | go.etcd.io/etcd v0.5.0-alpha.5.0.20200425165423-262c93980547 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39828 | HIGH7.48 | golang.org/x/crypto v0.0.0-20210513164829-c07d793c2f9a fixed in 0.52.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39832 | HIGH7.39 | golang.org/x/crypto v0.0.0-20210513164829-c07d793c2f9a fixed in 0.52.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-24539 | HIGH7.3 | stdlib v1.16.5 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29400 | HIGH7.3 | stdlib v1.16.5 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-39821 | MEDIUM6.97 | golang.org/x/net v0.0.0-20210510120150-4163338589ed fixed in 0.55.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-33997 | MEDIUM6.88 | github.com/docker/docker v17.12.0-ce-rc1.0.20200309214505-aa6a9891b09c+incompatible fixed in 29.3.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-27289 | MEDIUM6.88 | github.com/jackc/pgx v3.3.0+incompatible fixed in 4.18.2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-3445 | MEDIUM6.88 | github.com/mholt/archiver v3.1.1+incompatible No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39831 | MEDIUM6.88 | golang.org/x/crypto v0.0.0-20210513164829-c07d793c2f9a fixed in 0.52.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25681 | MEDIUM6.88 | golang.org/x/net v0.0.0-20210510120150-4163338589ed fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27136 | MEDIUM6.88 | golang.org/x/net v0.0.0-20210510120150-4163338589ed fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-28842 | MEDIUM6.8 | github.com/docker/docker v17.12.0-ce-rc1.0.20200309214505-aa6a9891b09c+incompatible fixed in 20.10.24, 23.0.3 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-8559 | MEDIUM6.8 | k8s.io/apimachinery v0.18.2 fixed in 0.16.13, 0.17.9, 0.18.7 | 6.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-24557 | MEDIUM6.63 | github.com/docker/docker v17.12.0-ce-rc1.0.20200309214505-aa6a9891b09c+incompatible fixed in 24.0.9, 25.0.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-0406 | MEDIUM6.63 | github.com/mholt/archiver v3.1.1+incompatible No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-30580 | MEDIUM6.63 | stdlib v1.16.5 fixed in 1.17.11, 1.18.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-29403 | MEDIUM6.63 | stdlib v1.16.5 fixed in 1.19.10, 1.20.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39822 | MEDIUM6.63 | stdlib v1.16.5 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-11254 | MEDIUM6.5 | github.com/go-yaml/yaml v2.1.0+incompatible No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-15136 | MEDIUM6.5 | go.etcd.io/etcd v0.5.0-alpha.5.0.20200425165423-262c93980547 fixed in 3.4.10, 3.3.23 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-34558 | MEDIUM6.5 | stdlib v1.16.5 fixed in 1.15.14, 1.16.6 | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1705 | MEDIUM6.5 | stdlib v1.16.5 fixed in 1.17.12, 1.18.4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32148 | MEDIUM6.5 | stdlib v1.16.5 fixed in 1.17.12, 1.18.4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29406 | MEDIUM6.5 | stdlib v1.16.5 fixed in 1.19.11, 1.20.6 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-41567 | MEDIUM6.38 | github.com/docker/docker v17.12.0-ce-rc1.0.20200309214505-aa6a9891b09c+incompatible No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-29018 | MEDIUM6.38 | github.com/docker/docker v17.12.0-ce-rc1.0.20200309214505-aa6a9891b09c+incompatible fixed in 26.0.0-rc3, 25.0.5, 23.0.11 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-38149 | MEDIUM6.38 | github.com/hashicorp/consul-template v0.26.0 fixed in 0.27.3, 0.28.3, 0.29.2 | 0.7% Theoretical Threat | 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-20210513164829-c07d793c2f9a 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-20210513164829-c07d793c2f9a fixed in 0.35.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-47913 | MEDIUM6.38 | golang.org/x/crypto v0.0.0-20210513164829-c07d793c2f9a fixed in 0.43.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-39829 | MEDIUM6.38 | golang.org/x/crypto v0.0.0-20210513164829-c07d793c2f9a fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-39830 | MEDIUM6.38 | golang.org/x/crypto v0.0.0-20210513164829-c07d793c2f9a fixed in 0.52.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-39835 | MEDIUM6.38 | golang.org/x/crypto v0.0.0-20210513164829-c07d793c2f9a fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46597 | MEDIUM6.38 | golang.org/x/crypto v0.0.0-20210513164829-c07d793c2f9a fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-45338 | MEDIUM6.38 | golang.org/x/net v0.0.0-20210510120150-4163338589ed fixed in 0.33.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | golang.org/x/net v0.0.0-20210510120150-4163338589ed fixed in 0.53.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-22868 | MEDIUM6.38 | golang.org/x/oauth2 v0.0.0-20200107190931-bf48bf16ab8d fixed in 0.27.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-41716 | MEDIUM6.38 | stdlib v1.16.5 fixed in 1.18.8, 1.19.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-61729 | MEDIUM6.38 | stdlib v1.16.5 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25679 | MEDIUM6.38 | stdlib v1.16.5 fixed in 1.25.8, 1.26.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-27145 | MEDIUM6.38 | stdlib v1.16.5 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32280 | MEDIUM6.38 | stdlib v1.16.5 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32281 | MEDIUM6.38 | stdlib v1.16.5 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32283 | MEDIUM6.38 | stdlib v1.16.5 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33811 | MEDIUM6.38 | stdlib v1.16.5 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | stdlib v1.16.5 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39820 | MEDIUM6.38 | stdlib v1.16.5 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39836 | MEDIUM6.38 | stdlib v1.16.5 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42499 | MEDIUM6.38 | stdlib v1.16.5 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42504 | MEDIUM6.38 | stdlib v1.16.5 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-58183 | MEDIUM6.38 | stdlib v1.16.5 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61728 | MEDIUM6.38 | stdlib v1.16.5 fixed in 1.24.12, 1.25.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-41091 | MEDIUM6.3 | github.com/docker/docker v17.12.0-ce-rc1.0.20200309214505-aa6a9891b09c+incompatible fixed in 20.10.9 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42508 | MEDIUM6.29 | golang.org/x/crypto v0.0.0-20210513164829-c07d793c2f9a fixed in 0.52.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42306 | MEDIUM6.12 | github.com/docker/docker v17.12.0-ce-rc1.0.20200309214505-aa6a9891b09c+incompatible No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46595 | MEDIUM6.03 | golang.org/x/crypto v0.0.0-20210513164829-c07d793c2f9a fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-47907 | MEDIUM5.95 | stdlib v1.16.5 fixed in 1.23.12, 1.24.6 | 0.4% Theoretical Threat | 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-2021-36221 | MEDIUM5.9 | stdlib v1.16.5 fixed in 1.15.15, 1.16.7 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-24791 | MEDIUM5.9 | stdlib v1.16.5 fixed in 1.21.12, 1.22.5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34158 | MEDIUM5.9 | stdlib v1.16.5 fixed in 1.22.7, 1.23.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45288 | MEDIUM5.85 | golang.org/x/net v0.0.0-20210510120150-4163338589ed fixed in 0.23.0 | 92.0% Actively Exploited | Directly Exposed |
| CVE-2023-45288 | MEDIUM5.85 | stdlib v1.16.5 fixed in 1.21.9, 1.22.2 | 92.0% Actively Exploited | Directly Exposed |
| CVE-2023-28841 | MEDIUM5.78 | github.com/docker/docker v17.12.0-ce-rc1.0.20200309214505-aa6a9891b09c+incompatible fixed in 20.10.24, 23.0.3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-4673 | MEDIUM5.78 | stdlib v1.16.5 fixed in 1.23.10, 1.24.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11579 | MEDIUM5.52 | github.com/nwaples/rardecode v1.1.0 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-33343 | MEDIUM5.52 | go.etcd.io/etcd v0.5.0-alpha.5.0.20200425165423-262c93980547 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-20329 | MEDIUM5.52 | go.mongodb.org/mongo-driver v1.4.6 fixed in 1.5.1 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-39827 | MEDIUM5.52 | golang.org/x/crypto v0.0.0-20210513164829-c07d793c2f9a fixed in 0.52.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39834 | MEDIUM5.52 | golang.org/x/crypto v0.0.0-20210513164829-c07d793c2f9a fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-22872 | MEDIUM5.52 | golang.org/x/net v0.0.0-20210510120150-4163338589ed fixed in 0.38.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25680 | MEDIUM5.52 | golang.org/x/net v0.0.0-20210510120150-4163338589ed fixed in 0.55.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-24785 | MEDIUM5.52 | stdlib v1.16.5 fixed in 1.21.8, 1.22.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-47906 | MEDIUM5.52 | stdlib v1.16.5 fixed in 1.23.12, 1.24.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61727 | MEDIUM5.52 | stdlib v1.16.5 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39825 | MEDIUM5.52 | stdlib v1.16.5 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-10743 | MEDIUM5.5 | github.com/mholt/archiver v3.1.1+incompatible fixed in 3.3.2 | 6.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23806 | MEDIUM5.46 | stdlib v1.16.5 fixed in 1.16.14, 1.17.7 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-32282 | MEDIUM5.44 | stdlib v1.16.5 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-24784 | MEDIUM5.4 | stdlib v1.16.5 fixed in 1.21.8, 1.22.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-36109 | MEDIUM5.35 | github.com/docker/docker v17.12.0-ce-rc1.0.20200309214505-aa6a9891b09c+incompatible fixed in 20.10.18 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-41089 | MEDIUM5.35 | github.com/docker/docker v17.12.0-ce-rc1.0.20200309214505-aa6a9891b09c+incompatible fixed in 20.10.9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-2097 | MEDIUM5.3 | libcrypto1.1 1.1.1k-r0 fixed in 1.1.1q-r0 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2097 | MEDIUM5.3 | libssl1.1 1.1.1k-r0 fixed in 1.1.1q-r0 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27534 | MEDIUM5.3 | github.com/docker/docker v17.12.0-ce-rc1.0.20200309214505-aa6a9891b09c+incompatible fixed in 19.03.9 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41717 | MEDIUM5.3 | golang.org/x/net v0.0.0-20210510120150-4163338589ed fixed in 0.4.0 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29526 | MEDIUM5.3 | golang.org/x/sys v0.0.0-20210514084401-e8d321eab015 fixed in 0.0.0-20220412211240-33da011f77ad | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29526 | MEDIUM5.3 | stdlib v1.16.5 fixed in 1.17.10, 1.18.2 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41717 | MEDIUM5.3 | stdlib v1.16.5 fixed in 1.18.9, 1.19.4 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29409 | MEDIUM5.3 | stdlib v1.16.5 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.5 fixed in 1.20.12, 1.21.5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45289 | MEDIUM5.3 | stdlib v1.16.5 fixed in 1.21.8, 1.22.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45290 | MEDIUM5.3 | stdlib v1.16.5 fixed in 1.21.8, 1.22.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3978 | MEDIUM5.18 | golang.org/x/net v0.0.0-20210510120150-4163338589ed fixed in 0.13.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-42502 | MEDIUM5.18 | golang.org/x/net v0.0.0-20210510120150-4163338589ed fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-39318 | MEDIUM5.18 | stdlib v1.16.5 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-39319 | MEDIUM5.18 | stdlib v1.16.5 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-32289 | MEDIUM5.18 | stdlib v1.16.5 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-24769 | MEDIUM5.02 | github.com/docker/docker v17.12.0-ce-rc1.0.20200309214505-aa6a9891b09c+incompatible fixed in 20.10.14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-24783 | MEDIUM5.02 | stdlib v1.16.5 fixed in 1.21.8, 1.22.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-34155 | MEDIUM5.02 | stdlib v1.16.5 fixed in 1.22.7, 1.23.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-45336 | MEDIUM5.02 | stdlib v1.16.5 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-44717 | MEDIUM4.8 | stdlib v1.16.5 fixed in 1.16.12, 1.17.5 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-4235 | MEDIUM4.67 | github.com/go-yaml/yaml v2.1.0+incompatible No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-6104 | MEDIUM4.67 | github.com/hashicorp/go-retryablehttp v0.6.7 fixed in 0.7.7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-1099 | MEDIUM4.67 | go.etcd.io/etcd v0.5.0-alpha.5.0.20200425165423-262c93980547 fixed in 3.4.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-39833 | MEDIUM4.67 | golang.org/x/crypto v0.0.0-20210513164829-c07d793c2f9a fixed in 0.52.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-8565 | MEDIUM4.67 | k8s.io/client-go v0.18.2 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.16.5 fixed in 1.17.12, 1.18.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-24789 | MEDIUM4.67 | stdlib v1.16.5 fixed in 1.21.11, 1.22.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32288 | MEDIUM4.67 | stdlib v1.16.5 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-20210510120150-4163338589ed fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22871 | MEDIUM4.59 | stdlib v1.16.5 fixed in 1.23.8, 1.24.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-27142 | MEDIUM4.59 | stdlib v1.16.5 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39823 | MEDIUM4.59 | stdlib v1.16.5 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39826 | MEDIUM4.59 | stdlib v1.16.5 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-3711 | MEDIUM4.58 | libcrypto1.1 1.1.1k-r0 fixed in 1.1.1l-r0 | 87.8% Actively Exploited | Post-Exploit |
| CVE-2021-3711 | MEDIUM4.58 | libssl1.1 1.1.1k-r0 fixed in 1.1.1l-r0 | 87.8% Actively Exploited | Post-Exploit |
| CVE-2025-58058 | MEDIUM4.5 | github.com/ulikunitz/xz v0.5.7 fixed in 0.5.15 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-47914 | MEDIUM4.5 | golang.org/x/crypto v0.0.0-20210513164829-c07d793c2f9a fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58181 | MEDIUM4.5 | golang.org/x/crypto v0.0.0-20210513164829-c07d793c2f9a fixed in 0.45.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46598 | MEDIUM4.5 | golang.org/x/crypto v0.0.0-20210513164829-c07d793c2f9a fixed in 0.52.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-47911 | MEDIUM4.5 | golang.org/x/net v0.0.0-20210510120150-4163338589ed fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58190 | MEDIUM4.5 | golang.org/x/net v0.0.0-20210510120150-4163338589ed fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-24532 | MEDIUM4.5 | stdlib v1.16.5 fixed in 1.19.7, 1.20.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-45284 | MEDIUM4.5 | stdlib v1.16.5 fixed in 1.20.11, 1.21.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-22866 | MEDIUM4.5 | stdlib v1.16.5 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.5 fixed in 1.23.9, 1.24.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-47912 | MEDIUM4.5 | stdlib v1.16.5 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58185 | MEDIUM4.5 | stdlib v1.16.5 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58187 | MEDIUM4.5 | stdlib v1.16.5 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58188 | MEDIUM4.5 | stdlib v1.16.5 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58189 | MEDIUM4.5 | stdlib v1.16.5 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61723 | MEDIUM4.5 | stdlib v1.16.5 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61724 | MEDIUM4.5 | stdlib v1.16.5 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61725 | MEDIUM4.5 | stdlib v1.16.5 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61730 | MEDIUM4.5 | stdlib v1.16.5 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42505 | MEDIUM4.5 | stdlib v1.16.5 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.5 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58186 | MEDIUM4.5 | stdlib v1.16.5 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-54410 | MEDIUM4.42 | github.com/docker/docker v17.12.0-ce-rc1.0.20200309214505-aa6a9891b09c+incompatible fixed in 25.0.13, 28.0.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-42381 | MEDIUM4.32 | busybox 1.32.1-r6 fixed in 1.32.1-r7 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42382 | MEDIUM4.32 | busybox 1.32.1-r6 fixed in 1.32.1-r7 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42383 | MEDIUM4.32 | busybox 1.32.1-r6 fixed in 1.32.1-r7 | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42384 | MEDIUM4.32 | busybox 1.32.1-r6 fixed in 1.32.1-r7 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42385 | MEDIUM4.32 | busybox 1.32.1-r6 fixed in 1.32.1-r7 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42386 | MEDIUM4.32 | busybox 1.32.1-r6 fixed in 1.32.1-r7 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42381 | MEDIUM4.32 | ssl_client 1.32.1-r6 fixed in 1.32.1-r7 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42382 | MEDIUM4.32 | ssl_client 1.32.1-r6 fixed in 1.32.1-r7 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42383 | MEDIUM4.32 | ssl_client 1.32.1-r6 fixed in 1.32.1-r7 | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42384 | MEDIUM4.32 | ssl_client 1.32.1-r6 fixed in 1.32.1-r7 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42385 | MEDIUM4.32 | ssl_client 1.32.1-r6 fixed in 1.32.1-r7 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42386 | MEDIUM4.32 | ssl_client 1.32.1-r6 fixed in 1.32.1-r7 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28180 | MEDIUM4.3 | gopkg.in/square/go-jose.v2 v2.5.1 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17572 | MEDIUM4.08 | github.com/influxdata/influxdb v0.0.0-20190411212539-d24b7ba8c4c4 fixed in 0.9.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-37434 | MEDIUM4.06 | zlib 1.2.11-r3 fixed in 1.2.12-r2 | 15.5% High Exploitation Risk | Post-Exploit |
| CVE-2019-20933 | MEDIUM4.06 | github.com/influxdata/influxdb v0.0.0-20190411212539-d24b7ba8c4c4 fixed in 1.7.6 | 30.9% High Exploitation Risk | Post-Exploit |
| CVE-2025-22870 | LOW3.74 | golang.org/x/net v0.0.0-20210510120150-4163338589ed fixed in 0.36.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-22870 | LOW3.74 | stdlib v1.16.5 fixed in 1.23.7, 1.24.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44283 | LOW3.65 | go.etcd.io/etcd v0.5.0-alpha.5.0.20200425165423-262c93980547 fixed in 3.4.44 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45341 | LOW3.57 | stdlib v1.16.5 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-24538 | LOW3.53 | stdlib v1.16.5 fixed in 1.19.8, 1.20.3 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-24540 | LOW3.53 | stdlib v1.16.5 fixed in 1.19.9, 1.20.4 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-24790 | LOW3.53 | stdlib v1.16.5 fixed in 1.21.11, 1.22.4 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-0778 | LOW3.51 | libcrypto1.1 1.1.1k-r0 fixed in 1.1.1n-r0 | 70.6% Actively Exploited | Post-Exploit |
| CVE-2022-0778 | LOW3.51 | libssl1.1 1.1.1k-r0 fixed in 1.1.1n-r0 | 70.6% Actively Exploited | Post-Exploit |
| CVE-2018-25032 | LOW3.51 | zlib 1.2.11-r3 fixed in 1.2.12-r0 | 52.1% Actively Exploited | Post-Exploit |
| CVE-2021-3712 | LOW3.46 | libcrypto1.1 1.1.1k-r0 fixed in 1.1.1l-r0 | 50.4% Actively Exploited | Post-Exploit |
| CVE-2021-3712 | LOW3.46 | libssl1.1 1.1.1k-r0 fixed in 1.1.1l-r0 | 50.4% Actively Exploited | Post-Exploit |
| CVE-2026-41568 | LOW3.31 | github.com/docker/docker v17.12.0-ce-rc1.0.20200309214505-aa6a9891b09c+incompatible No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-36159 | LOW3.28 | apk-tools 2.12.5-r0 fixed in 2.12.6-r0 | 2.6% Low-Moderate Risk | Post-Exploit |
| 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-33186 | LOW3.28 | google.golang.org/grpc v1.29.1 fixed in 1.79.3 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34040 | LOW3.23 | github.com/docker/docker v17.12.0-ce-rc1.0.20200309214505-aa6a9891b09c+incompatible fixed in 29.3.1 | 10.1% High Exploitation Risk | Post-Exploit |
| CVE-2022-28391 | LOW3.17 | busybox 1.32.1-r6 fixed in 1.32.1-r8 | 3.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-28391 | LOW3.17 | ssl_client 1.32.1-r6 fixed in 1.32.1-r8 | 3.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34231 | LOW3.17 | github.com/snowflakedb/gosnowflake v1.3.11 fixed in 1.6.19 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28840 | LOW3.13 | github.com/docker/docker v17.12.0-ce-rc1.0.20200309214505-aa6a9891b09c+incompatible fixed in 20.10.24, 23.0.3 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-30065 | LOW2.81 | busybox 1.32.1-r6 fixed in 1.32.1-r9 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-30065 | LOW2.81 | ssl_client 1.32.1-r6 fixed in 1.32.1-r9 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42375 | LOW2.8 | busybox 1.32.1-r6 fixed in 1.32.1-r7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-42375 | LOW2.8 | ssl_client 1.32.1-r6 fixed in 1.32.1-r7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-42374 | LOW2.7 | busybox 1.32.1-r6 fixed in 1.32.1-r7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2021-42374 | LOW2.7 | ssl_client 1.32.1-r6 fixed in 1.32.1-r7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-30629 | LOW2.63 | stdlib v1.16.5 fixed in 1.17.11, 1.18.3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-42378 | LOW2.59 | busybox 1.32.1-r6 fixed in 1.32.1-r7 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42379 | LOW2.59 | busybox 1.32.1-r6 fixed in 1.32.1-r7 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42380 | LOW2.59 | busybox 1.32.1-r6 fixed in 1.32.1-r7 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42378 | LOW2.59 | ssl_client 1.32.1-r6 fixed in 1.32.1-r7 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42379 | LOW2.59 | ssl_client 1.32.1-r6 fixed in 1.32.1-r7 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42380 | LOW2.59 | ssl_client 1.32.1-r6 fixed in 1.32.1-r7 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-27139 | LOW2.12 | stdlib v1.16.5 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Directly Exposed |
| GHSA-jq35-85cj-fj4p | NONE0 | github.com/docker/docker v17.12.0-ce-rc1.0.20200309214505-aa6a9891b09c+incompatible fixed in 24.0.7, 23.0.8, 20.10.27 | — | Not Applicable |
| GHSA-xmmx-7jpf-fx42 | NONE0 | github.com/docker/docker v17.12.0-ce-rc1.0.20200309214505-aa6a9891b09c+incompatible fixed in 20.10.11 | — | Not Applicable |
| GHSA-vp35-85q5-9f25 | NONE0 | github.com/docker/docker v17.12.0-ce-rc1.0.20200309214505-aa6a9891b09c+incompatible fixed in 20.10.20 | — | Not Applicable |
| CVE-2026-2303 | NONE0 | go.mongodb.org/mongo-driver v1.4.6 fixed in 1.17.7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-30636 | NONE0 | golang.org/x/crypto v0.0.0-20210513164829-c07d793c2f9a fixed in 0.0.0-20220525230936-793ad666bf5e | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46600 | NONE0 | golang.org/x/net v0.0.0-20210510120150-4163338589ed fixed in 0.56.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39824 | NONE0 | golang.org/x/sys v0.0.0-20210514084401-e8d321eab015 fixed in 0.44.0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56852 | NONE0 | golang.org/x/text v0.3.6 fixed in 0.39.0 | 0.4% Theoretical Threat | Not Applicable |
| GHSA-hrxh-6v49-42gf | NONE0 | google.golang.org/grpc v1.29.1 fixed in 1.82.1 | — | Not Applicable |
| GHSA-m425-mq94-257g | NONE0 | google.golang.org/grpc v1.29.1 fixed in 1.56.3, 1.57.1, 1.58.3 | — | Not Applicable |
| CVE-2025-0913 | NONE0 | stdlib v1.16.5 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.