Last scanned:
AI verdict failed due to an error.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2023-0286 | MEDIUM5.77 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u4 | 59.5% Actively Exploited | Post-Exploit |
| CVE-2022-4450 | MEDIUM5.17 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u4 | 20.4% High Exploitation Risk | Post-Exploit |
| CVE-2023-2650 | MEDIUM5.07 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u5 | 75.1% Actively Exploited | Post-Exploit |
| CVE-2026-45447 | MEDIUM4.86 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u8 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0215 | MEDIUM4.5 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u4 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0464 | MEDIUM4.5 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u5 | 3.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28388 | MEDIUM4.5 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u7 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28389 | MEDIUM4.5 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u7 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28390 | MEDIUM4.5 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u7 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28387 | MEDIUM4.13 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u7 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2022-4304 | MEDIUM4.07 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u4 | 16.2% High Exploitation Risk | Post-Exploit |
| CVE-2025-69421 | LOW3.82 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-69419 | LOW3.77 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-5535 | LOW3.54 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u2 | 5.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-9230 | LOW3.36 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u4 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4741 | LOW3.36 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u2 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2024-0727 | LOW3.3 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u2 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2097 | LOW3.18 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u4 | 4.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0465 | LOW3.18 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u5 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0466 | LOW3.18 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u5 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-3446 | LOW3.18 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1v-0~deb11u1 | 6.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-3817 | LOW3.18 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1v-0~deb11u1 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5678 | LOW3.18 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u2 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-69420 | LOW3.01 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-22796 | LOW3.01 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW3 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u8 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2511 | LOW2.89 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u2 | 54.0% Actively Exploited | Post-Exploit |
| CVE-2026-22795 | LOW2.8 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u8 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2024-13176 | LOW2.4 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-68160 | LOW2.4 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-9143 | LOW2.22 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u2 | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2025-69418 | LOW2.04 | openssl 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68121 | NONE0 | stdlib v1.18 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-68121 | NONE0 | stdlib v1.17.11 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc6 2.31-13+deb11u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-24538 | NONE0 | stdlib v1.18 fixed in 1.19.8, 1.20.3 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-24540 | NONE0 | stdlib v1.18 fixed in 1.19.9, 1.20.4 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-24790 | NONE0 | stdlib v1.18 fixed in 1.21.11, 1.22.4 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-24538 | NONE0 | stdlib v1.17.11 fixed in 1.19.8, 1.20.3 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-24540 | NONE0 | stdlib v1.17.11 fixed in 1.19.9, 1.20.4 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-24790 | NONE0 | stdlib v1.17.11 fixed in 1.21.11, 1.22.4 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-33186 | NONE0 | google.golang.org/grpc v1.38.0 fixed in 1.79.3 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-33186 | NONE0 | google.golang.org/grpc v1.40.0 fixed in 1.79.3 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2024-2961 | NONE0 | libc6 2.31-13+deb11u3 fixed in 2.31-13+deb11u9 | 88.3% Actively Exploited | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc6 2.31-13+deb11u3 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-39828 | NONE0 | golang.org/x/crypto v0.0.0-20210616213533-5ff15b29337e fixed in 0.52.0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-39828 | NONE0 | golang.org/x/crypto v0.0.0-20210817164053-32db794688a5 fixed in 0.52.0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-39832 | NONE0 | golang.org/x/crypto v0.0.0-20210616213533-5ff15b29337e fixed in 0.52.0 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-39832 | NONE0 | golang.org/x/crypto v0.0.0-20210817164053-32db794688a5 fixed in 0.52.0 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-45337 | NONE0 | golang.org/x/crypto v0.0.0-20210616213533-5ff15b29337e fixed in 0.31.0 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-39821 | NONE0 | golang.org/x/net v0.0.0-20210614182718-04defd469f4e fixed in 0.55.0 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-45337 | NONE0 | golang.org/x/crypto v0.0.0-20210817164053-32db794688a5 fixed in 0.31.0 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-39821 | NONE0 | golang.org/x/net v0.0.0-20210525063256-abc453219eb5 fixed in 0.55.0 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-0861 | NONE0 | libc6 2.31-13+deb11u3 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-28387 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u7 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-45447 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u8 | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-39831 | NONE0 | golang.org/x/crypto v0.0.0-20210616213533-5ff15b29337e fixed in 0.52.0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25681 | NONE0 | golang.org/x/net v0.0.0-20210614182718-04defd469f4e fixed in 0.55.0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27136 | NONE0 | golang.org/x/net v0.0.0-20210614182718-04defd469f4e fixed in 0.55.0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39831 | NONE0 | golang.org/x/crypto v0.0.0-20210817164053-32db794688a5 fixed in 0.52.0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25681 | NONE0 | golang.org/x/net v0.0.0-20210525063256-abc453219eb5 fixed in 0.55.0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27136 | NONE0 | golang.org/x/net v0.0.0-20210525063256-abc453219eb5 fixed in 0.55.0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-3999 | NONE0 | libc6 2.31-13+deb11u3 fixed in 2.31-13+deb11u4 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-4911 | NONE0 | libc6 2.31-13+deb11u3 fixed in 2.31-13+deb11u7 | 81.4% Actively Exploited | Not Applicable |
| CVE-2022-30580 | NONE0 | stdlib v1.18 fixed in 1.17.11, 1.18.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-29403 | NONE0 | stdlib v1.18 fixed in 1.19.10, 1.20.5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-39822 | NONE0 | stdlib v1.18 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-29403 | NONE0 | stdlib v1.17.11 fixed in 1.19.10, 1.20.5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-39822 | NONE0 | stdlib v1.17.11 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-33599 | NONE0 | libc6 2.31-13+deb11u3 fixed in 2.31-13+deb11u10 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2018-20796 | NONE0 | libc6 2.31-13+deb11u3 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc6 2.31-13+deb11u3 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-4450 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u4 | 20.4% High Exploitation Risk | Not Applicable |
| CVE-2023-0215 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u4 | 4.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-0464 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u5 | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2025-69421 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-28388 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u7 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-28389 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u7 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-28390 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u7 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2021-43565 | NONE0 | golang.org/x/crypto v0.0.0-20210616213533-5ff15b29337e fixed in 0.0.0-20211202192323-5770296d904e | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-27191 | NONE0 | golang.org/x/crypto v0.0.0-20210616213533-5ff15b29337e fixed in 0.0.0-20220314234659-1baeb1ce4c0b | 3.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-22869 | NONE0 | golang.org/x/crypto v0.0.0-20210616213533-5ff15b29337e fixed in 0.35.0 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-47913 | NONE0 | golang.org/x/crypto v0.0.0-20210616213533-5ff15b29337e fixed in 0.43.0 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-39829 | NONE0 | golang.org/x/crypto v0.0.0-20210616213533-5ff15b29337e fixed in 0.52.0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-39830 | NONE0 | golang.org/x/crypto v0.0.0-20210616213533-5ff15b29337e fixed in 0.52.0 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-39835 | NONE0 | golang.org/x/crypto v0.0.0-20210616213533-5ff15b29337e fixed in 0.52.0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46597 | NONE0 | golang.org/x/crypto v0.0.0-20210616213533-5ff15b29337e fixed in 0.52.0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-44716 | NONE0 | golang.org/x/net v0.0.0-20210614182718-04defd469f4e fixed in 0.0.0-20211209124913-491a49abca63 | 4.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-27664 | NONE0 | golang.org/x/net v0.0.0-20210614182718-04defd469f4e fixed in 0.0.0-20220906165146-f3363e06e74c | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-41723 | NONE0 | golang.org/x/net v0.0.0-20210614182718-04defd469f4e fixed in 0.7.0 | 4.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-39325 | NONE0 | golang.org/x/net v0.0.0-20210614182718-04defd469f4e fixed in 0.17.0 | 3.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-45288 | NONE0 | golang.org/x/net v0.0.0-20210614182718-04defd469f4e fixed in 0.23.0 | 92.0% Actively Exploited | Not Applicable |
| CVE-2024-45338 | NONE0 | golang.org/x/net v0.0.0-20210614182718-04defd469f4e fixed in 0.33.0 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | golang.org/x/net v0.0.0-20210614182718-04defd469f4e fixed in 0.53.0 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-22868 | NONE0 | golang.org/x/oauth2 v0.0.0-20210628180205-a41e5a781914 fixed in 0.27.0 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2021-38561 | NONE0 | golang.org/x/text v0.3.6 fixed in 0.3.7 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-32149 | NONE0 | golang.org/x/text v0.3.6 fixed in 0.3.8 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-24675 | NONE0 | stdlib v1.18 fixed in 1.17.9, 1.18.1 | 10.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-27536 | NONE0 | stdlib v1.18 fixed in 1.18.1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-27664 | NONE0 | stdlib v1.18 fixed in 1.18.6, 1.19.1 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-28131 | NONE0 | stdlib v1.18 fixed in 1.17.12, 1.18.4 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-28327 | NONE0 | stdlib v1.18 fixed in 1.17.9, 1.18.1 | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-2879 | NONE0 | stdlib v1.18 fixed in 1.18.7, 1.19.2 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-2880 | NONE0 | stdlib v1.18 fixed in 1.18.7, 1.19.2 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-29804 | NONE0 | stdlib v1.18 fixed in 1.17.11, 1.18.3 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-30630 | NONE0 | stdlib v1.18 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-30631 | NONE0 | stdlib v1.18 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-30632 | NONE0 | stdlib v1.18 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-30633 | NONE0 | stdlib v1.18 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-30634 | NONE0 | stdlib v1.18 fixed in 1.17.11, 1.18.3 | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-30635 | NONE0 | stdlib v1.18 fixed in 1.17.12, 1.18.4 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-32189 | NONE0 | stdlib v1.18 fixed in 1.17.13, 1.18.5 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-41715 | NONE0 | stdlib v1.18 fixed in 1.18.7, 1.19.2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-41716 | NONE0 | stdlib v1.18 fixed in 1.18.8, 1.19.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-41720 | NONE0 | stdlib v1.18 fixed in 1.18.9, 1.19.4 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-41722 | NONE0 | stdlib v1.18 fixed in 1.19.6, 1.20.1 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-41723 | NONE0 | stdlib v1.18 fixed in 1.19.6, 1.20.1 | 4.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-41724 | NONE0 | stdlib v1.18 fixed in 1.19.6, 1.20.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-41725 | NONE0 | stdlib v1.18 fixed in 1.19.6, 1.20.1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-24534 | NONE0 | stdlib v1.18 fixed in 1.19.8, 1.20.3 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2023-24536 | NONE0 | stdlib v1.18 fixed in 1.19.8, 1.20.3 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-24537 | NONE0 | stdlib v1.18 fixed in 1.19.8, 1.20.3 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-39325 | NONE0 | stdlib v1.18 fixed in 1.20.10, 1.21.3 | 3.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-45283 | NONE0 | stdlib v1.18 fixed in 1.20.11, 1.21.4, 1.20.12, 1.21.5 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-45287 | NONE0 | stdlib v1.18 fixed in 1.20.0 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-45288 | NONE0 | stdlib v1.18 fixed in 1.21.9, 1.22.2 | 92.0% Actively Exploited | Not Applicable |
| CVE-2024-34156 | NONE0 | stdlib v1.18 fixed in 1.22.7, 1.23.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-61726 | NONE0 | stdlib v1.18 fixed in 1.24.12, 1.25.6 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-61729 | NONE0 | stdlib v1.18 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25679 | NONE0 | stdlib v1.18 fixed in 1.25.8, 1.26.1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.18 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32280 | NONE0 | stdlib v1.18 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32281 | NONE0 | stdlib v1.18 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32283 | NONE0 | stdlib v1.18 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33811 | NONE0 | stdlib v1.18 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | stdlib v1.18 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39820 | NONE0 | stdlib v1.18 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39836 | NONE0 | stdlib v1.18 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42499 | NONE0 | stdlib v1.18 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.18 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58183 | NONE0 | stdlib v1.18 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61728 | NONE0 | stdlib v1.18 fixed in 1.24.12, 1.25.6 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-65637 | NONE0 | github.com/sirupsen/logrus v1.8.1 fixed in 1.8.3, 1.9.1, 1.9.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-43565 | NONE0 | golang.org/x/crypto v0.0.0-20210817164053-32db794688a5 fixed in 0.0.0-20211202192323-5770296d904e | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-27191 | NONE0 | golang.org/x/crypto v0.0.0-20210817164053-32db794688a5 fixed in 0.0.0-20220314234659-1baeb1ce4c0b | 3.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-22869 | NONE0 | golang.org/x/crypto v0.0.0-20210817164053-32db794688a5 fixed in 0.35.0 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-47913 | NONE0 | golang.org/x/crypto v0.0.0-20210817164053-32db794688a5 fixed in 0.43.0 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-39829 | NONE0 | golang.org/x/crypto v0.0.0-20210817164053-32db794688a5 fixed in 0.52.0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-39830 | NONE0 | golang.org/x/crypto v0.0.0-20210817164053-32db794688a5 fixed in 0.52.0 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-39835 | NONE0 | golang.org/x/crypto v0.0.0-20210817164053-32db794688a5 fixed in 0.52.0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46597 | NONE0 | golang.org/x/crypto v0.0.0-20210817164053-32db794688a5 fixed in 0.52.0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-44716 | NONE0 | golang.org/x/net v0.0.0-20210525063256-abc453219eb5 fixed in 0.0.0-20211209124913-491a49abca63 | 4.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-27664 | NONE0 | golang.org/x/net v0.0.0-20210525063256-abc453219eb5 fixed in 0.0.0-20220906165146-f3363e06e74c | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-41723 | NONE0 | golang.org/x/net v0.0.0-20210525063256-abc453219eb5 fixed in 0.7.0 | 4.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-39325 | NONE0 | golang.org/x/net v0.0.0-20210525063256-abc453219eb5 fixed in 0.17.0 | 3.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-45288 | NONE0 | golang.org/x/net v0.0.0-20210525063256-abc453219eb5 fixed in 0.23.0 | 92.0% Actively Exploited | Not Applicable |
| CVE-2024-45338 | NONE0 | golang.org/x/net v0.0.0-20210525063256-abc453219eb5 fixed in 0.33.0 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | golang.org/x/net v0.0.0-20210525063256-abc453219eb5 fixed in 0.53.0 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-22868 | NONE0 | golang.org/x/oauth2 v0.0.0-20210819190943-2bc19b11175f fixed in 0.27.0 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-32149 | NONE0 | golang.org/x/text v0.3.7 fixed in 0.3.8 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-28948 | NONE0 | gopkg.in/yaml.v3 v3.0.0-20210107192922-496545a6307b fixed in 3.0.1 | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-27664 | NONE0 | stdlib v1.17.11 fixed in 1.18.6, 1.19.1 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-28131 | NONE0 | stdlib v1.17.11 fixed in 1.17.12, 1.18.4 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-2879 | NONE0 | stdlib v1.17.11 fixed in 1.18.7, 1.19.2 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-2880 | NONE0 | stdlib v1.17.11 fixed in 1.18.7, 1.19.2 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-30630 | NONE0 | stdlib v1.17.11 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-30631 | NONE0 | stdlib v1.17.11 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-30632 | NONE0 | stdlib v1.17.11 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-30633 | NONE0 | stdlib v1.17.11 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-30635 | NONE0 | stdlib v1.17.11 fixed in 1.17.12, 1.18.4 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-32189 | NONE0 | stdlib v1.17.11 fixed in 1.17.13, 1.18.5 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-41715 | NONE0 | stdlib v1.17.11 fixed in 1.18.7, 1.19.2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-41716 | NONE0 | stdlib v1.17.11 fixed in 1.18.8, 1.19.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-41720 | NONE0 | stdlib v1.17.11 fixed in 1.18.9, 1.19.4 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-41722 | NONE0 | stdlib v1.17.11 fixed in 1.19.6, 1.20.1 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-41723 | NONE0 | stdlib v1.17.11 fixed in 1.19.6, 1.20.1 | 4.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-41724 | NONE0 | stdlib v1.17.11 fixed in 1.19.6, 1.20.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-41725 | NONE0 | stdlib v1.17.11 fixed in 1.19.6, 1.20.1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-24534 | NONE0 | stdlib v1.17.11 fixed in 1.19.8, 1.20.3 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2023-24536 | NONE0 | stdlib v1.17.11 fixed in 1.19.8, 1.20.3 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-24537 | NONE0 | stdlib v1.17.11 fixed in 1.19.8, 1.20.3 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-39325 | NONE0 | stdlib v1.17.11 fixed in 1.20.10, 1.21.3 | 3.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-45283 | NONE0 | stdlib v1.17.11 fixed in 1.20.11, 1.21.4, 1.20.12, 1.21.5 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-45287 | NONE0 | stdlib v1.17.11 fixed in 1.20.0 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-45288 | NONE0 | stdlib v1.17.11 fixed in 1.21.9, 1.22.2 | 92.0% Actively Exploited | Not Applicable |
| CVE-2024-34156 | NONE0 | stdlib v1.17.11 fixed in 1.22.7, 1.23.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-61726 | NONE0 | stdlib v1.17.11 fixed in 1.24.12, 1.25.6 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-61729 | NONE0 | stdlib v1.17.11 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25679 | NONE0 | stdlib v1.17.11 fixed in 1.25.8, 1.26.1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.17.11 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32280 | NONE0 | stdlib v1.17.11 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32281 | NONE0 | stdlib v1.17.11 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32283 | NONE0 | stdlib v1.17.11 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33811 | NONE0 | stdlib v1.17.11 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | stdlib v1.17.11 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39820 | NONE0 | stdlib v1.17.11 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39836 | NONE0 | stdlib v1.17.11 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42499 | NONE0 | stdlib v1.17.11 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.17.11 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58183 | NONE0 | stdlib v1.17.11 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61728 | NONE0 | stdlib v1.17.11 fixed in 1.24.12, 1.25.6 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-0286 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u4 | 59.5% Actively Exploited | Not Applicable |
| CVE-2025-69419 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42508 | NONE0 | golang.org/x/crypto v0.0.0-20210616213533-5ff15b29337e fixed in 0.52.0 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42508 | NONE0 | golang.org/x/crypto v0.0.0-20210817164053-32db794688a5 fixed in 0.52.0 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-24539 | NONE0 | stdlib v1.18 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-29400 | NONE0 | stdlib v1.18 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-24539 | NONE0 | stdlib v1.17.11 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-29400 | NONE0 | stdlib v1.17.11 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-46595 | NONE0 | golang.org/x/crypto v0.0.0-20210616213533-5ff15b29337e fixed in 0.52.0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46595 | NONE0 | golang.org/x/crypto v0.0.0-20210817164053-32db794688a5 fixed in 0.52.0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-4802 | NONE0 | libc6 2.31-13+deb11u3 fixed in 2.31-13+deb11u13 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-47907 | NONE0 | stdlib v1.18 fixed in 1.23.12, 1.24.6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-47907 | NONE0 | stdlib v1.17.11 fixed in 1.23.12, 1.24.6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-4673 | NONE0 | stdlib v1.18 fixed in 1.23.10, 1.24.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-4673 | NONE0 | stdlib v1.17.11 fixed in 1.23.10, 1.24.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc6 2.31-13+deb11u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-2650 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u5 | 75.1% Actively Exploited | Not Applicable |
| CVE-2026-39827 | NONE0 | golang.org/x/crypto v0.0.0-20210616213533-5ff15b29337e fixed in 0.52.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39834 | NONE0 | golang.org/x/crypto v0.0.0-20210616213533-5ff15b29337e fixed in 0.52.0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-22872 | NONE0 | golang.org/x/net v0.0.0-20210614182718-04defd469f4e fixed in 0.38.0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25680 | NONE0 | golang.org/x/net v0.0.0-20210614182718-04defd469f4e fixed in 0.55.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-1705 | NONE0 | stdlib v1.18 fixed in 1.17.12, 1.18.4 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-32148 | NONE0 | stdlib v1.18 fixed in 1.17.12, 1.18.4 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-29406 | NONE0 | stdlib v1.18 fixed in 1.19.11, 1.20.6 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-24785 | NONE0 | stdlib v1.18 fixed in 1.21.8, 1.22.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-47906 | NONE0 | stdlib v1.18 fixed in 1.23.12, 1.24.6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61727 | NONE0 | stdlib v1.18 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39825 | NONE0 | stdlib v1.18 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-35469 | NONE0 | github.com/moby/spdystream v0.2.0 fixed in 0.5.1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-39827 | NONE0 | golang.org/x/crypto v0.0.0-20210817164053-32db794688a5 fixed in 0.52.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39834 | NONE0 | golang.org/x/crypto v0.0.0-20210817164053-32db794688a5 fixed in 0.52.0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-22872 | NONE0 | golang.org/x/net v0.0.0-20210525063256-abc453219eb5 fixed in 0.38.0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25680 | NONE0 | golang.org/x/net v0.0.0-20210525063256-abc453219eb5 fixed in 0.55.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-1705 | NONE0 | stdlib v1.17.11 fixed in 1.17.12, 1.18.4 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-32148 | NONE0 | stdlib v1.17.11 fixed in 1.17.12, 1.18.4 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-29406 | NONE0 | stdlib v1.17.11 fixed in 1.19.11, 1.20.6 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-24785 | NONE0 | stdlib v1.17.11 fixed in 1.21.8, 1.22.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-47906 | NONE0 | stdlib v1.17.11 fixed in 1.23.12, 1.24.6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61727 | NONE0 | stdlib v1.17.11 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39825 | NONE0 | stdlib v1.17.11 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32282 | NONE0 | stdlib v1.18 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32282 | NONE0 | stdlib v1.17.11 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-3978 | NONE0 | golang.org/x/net v0.0.0-20210614182718-04defd469f4e fixed in 0.13.0 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-42502 | NONE0 | golang.org/x/net v0.0.0-20210614182718-04defd469f4e fixed in 0.55.0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-39318 | NONE0 | stdlib v1.18 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-39319 | NONE0 | stdlib v1.18 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-32289 | NONE0 | stdlib v1.18 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-3978 | NONE0 | golang.org/x/net v0.0.0-20210525063256-abc453219eb5 fixed in 0.13.0 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-42502 | NONE0 | golang.org/x/net v0.0.0-20210525063256-abc453219eb5 fixed in 0.55.0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-39318 | NONE0 | stdlib v1.17.11 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-39319 | NONE0 | stdlib v1.17.11 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-32289 | NONE0 | stdlib v1.17.11 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-4806 | NONE0 | libc6 2.31-13+deb11u3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-4813 | NONE0 | libc6 2.31-13+deb11u3 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-5435 | NONE0 | libc6 2.31-13+deb11u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-15281 | NONE0 | libc6 2.31-13+deb11u3 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-4304 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u4 | 16.2% High Exploitation Risk | Not Applicable |
| CVE-2024-5535 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u2 | 5.6% Low-Moderate Risk | Not Applicable |
| CVE-2025-69420 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-22796 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-9076 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-48795 | NONE0 | golang.org/x/crypto v0.0.0-20210616213533-5ff15b29337e fixed in 0.17.0 | 93.3% Actively Exploited | Not Applicable |
| CVE-2024-24786 | NONE0 | google.golang.org/protobuf v1.26.0 fixed in 1.33.0 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-24783 | NONE0 | stdlib v1.18 fixed in 1.21.8, 1.22.1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-24791 | NONE0 | stdlib v1.18 fixed in 1.21.12, 1.22.5 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-34155 | NONE0 | stdlib v1.18 fixed in 1.22.7, 1.23.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-34158 | NONE0 | stdlib v1.18 fixed in 1.22.7, 1.23.1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2024-45336 | NONE0 | stdlib v1.18 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-48795 | NONE0 | golang.org/x/crypto v0.0.0-20210817164053-32db794688a5 fixed in 0.17.0 | 93.3% Actively Exploited | Not Applicable |
| CVE-2024-24786 | NONE0 | google.golang.org/protobuf v1.27.1 fixed in 1.33.0 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-24783 | NONE0 | stdlib v1.17.11 fixed in 1.21.8, 1.22.1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-24791 | NONE0 | stdlib v1.17.11 fixed in 1.21.12, 1.22.5 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-34155 | NONE0 | stdlib v1.17.11 fixed in 1.22.7, 1.23.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-34158 | NONE0 | stdlib v1.17.11 fixed in 1.22.7, 1.23.1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2024-45336 | NONE0 | stdlib v1.17.11 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-9230 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u4 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2024-4741 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u2 | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-8911 | NONE0 | github.com/aws/aws-sdk-go v1.28.2 fixed in 1.34.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-0395 | NONE0 | libc6 2.31-13+deb11u3 fixed in 2.31-13+deb11u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-0727 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u2 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-22795 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-7383 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-39833 | NONE0 | golang.org/x/crypto v0.0.0-20210616213533-5ff15b29337e fixed in 0.52.0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-1962 | NONE0 | stdlib v1.18 fixed in 1.17.12, 1.18.4 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-24789 | NONE0 | stdlib v1.18 fixed in 1.21.11, 1.22.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32288 | NONE0 | stdlib v1.18 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39833 | NONE0 | golang.org/x/crypto v0.0.0-20210817164053-32db794688a5 fixed in 0.52.0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-1962 | NONE0 | stdlib v1.17.11 fixed in 1.17.12, 1.18.4 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-24789 | NONE0 | stdlib v1.17.11 fixed in 1.21.11, 1.22.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32288 | NONE0 | stdlib v1.17.11 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42506 | NONE0 | golang.org/x/net v0.0.0-20210614182718-04defd469f4e fixed in 0.55.0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-24784 | NONE0 | stdlib v1.18 fixed in 1.21.8, 1.22.1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-22871 | NONE0 | stdlib v1.18 fixed in 1.23.8, 1.24.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-27142 | NONE0 | stdlib v1.18 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39823 | NONE0 | stdlib v1.18 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39826 | NONE0 | stdlib v1.18 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42506 | NONE0 | golang.org/x/net v0.0.0-20210525063256-abc453219eb5 fixed in 0.55.0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-24784 | NONE0 | stdlib v1.17.11 fixed in 1.21.8, 1.22.1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-22871 | NONE0 | stdlib v1.17.11 fixed in 1.23.8, 1.24.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-27142 | NONE0 | stdlib v1.17.11 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39823 | NONE0 | stdlib v1.17.11 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39826 | NONE0 | stdlib v1.17.11 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-33600 | NONE0 | libc6 2.31-13+deb11u3 fixed in 2.31-13+deb11u10 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-0915 | NONE0 | libc6 2.31-13+deb11u3 fixed in 2.31-13+deb11u14 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | libc6 2.31-13+deb11u3 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc6 2.31-13+deb11u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc6 2.31-13+deb11u3 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-2097 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u4 | 4.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-0465 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u5 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-0466 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u5 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-3446 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1v-0~deb11u1 | 6.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-3817 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1v-0~deb11u1 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-5678 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u2 | 4.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-42766 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u8 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2025-47914 | NONE0 | golang.org/x/crypto v0.0.0-20210616213533-5ff15b29337e fixed in 0.45.0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58181 | NONE0 | golang.org/x/crypto v0.0.0-20210616213533-5ff15b29337e fixed in 0.45.0 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46598 | NONE0 | golang.org/x/crypto v0.0.0-20210616213533-5ff15b29337e fixed in 0.52.0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-41717 | NONE0 | golang.org/x/net v0.0.0-20210614182718-04defd469f4e fixed in 0.4.0 | 5.6% Low-Moderate Risk | Not Applicable |
| CVE-2025-47911 | NONE0 | golang.org/x/net v0.0.0-20210614182718-04defd469f4e fixed in 0.45.0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58190 | NONE0 | golang.org/x/net v0.0.0-20210614182718-04defd469f4e fixed in 0.45.0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-29526 | NONE0 | golang.org/x/sys v0.0.0-20210630005230-0f9fa26af87c fixed in 0.0.0-20220412211240-33da011f77ad | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-29526 | NONE0 | stdlib v1.18 fixed in 1.17.10, 1.18.2 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-41717 | NONE0 | stdlib v1.18 fixed in 1.18.9, 1.19.4 | 5.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-24532 | NONE0 | stdlib v1.18 fixed in 1.19.7, 1.20.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-29409 | NONE0 | stdlib v1.18 fixed in 1.19.12, 1.20.7, 1.21.0-rc.4 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-39326 | NONE0 | stdlib v1.18 fixed in 1.20.12, 1.21.5 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-45284 | NONE0 | stdlib v1.18 fixed in 1.20.11, 1.21.4 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45289 | NONE0 | stdlib v1.18 fixed in 1.21.8, 1.22.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-45290 | NONE0 | stdlib v1.18 fixed in 1.21.8, 1.22.1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-22866 | NONE0 | stdlib v1.18 fixed in 1.22.12, 1.23.6, 1.24.0-rc.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22873 | NONE0 | stdlib v1.18 fixed in 1.23.9, 1.24.3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-47912 | NONE0 | stdlib v1.18 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58185 | NONE0 | stdlib v1.18 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58187 | NONE0 | stdlib v1.18 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58188 | NONE0 | stdlib v1.18 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58189 | NONE0 | stdlib v1.18 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61723 | NONE0 | stdlib v1.18 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61724 | NONE0 | stdlib v1.18 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61725 | NONE0 | stdlib v1.18 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61730 | NONE0 | stdlib v1.18 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.18 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42507 | NONE0 | stdlib v1.18 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58186 | NONE0 | stdlib v1.18 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-47914 | NONE0 | golang.org/x/crypto v0.0.0-20210817164053-32db794688a5 fixed in 0.45.0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58181 | NONE0 | golang.org/x/crypto v0.0.0-20210817164053-32db794688a5 fixed in 0.45.0 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46598 | NONE0 | golang.org/x/crypto v0.0.0-20210817164053-32db794688a5 fixed in 0.52.0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-41717 | NONE0 | golang.org/x/net v0.0.0-20210525063256-abc453219eb5 fixed in 0.4.0 | 5.6% Low-Moderate Risk | Not Applicable |
| CVE-2025-47911 | NONE0 | golang.org/x/net v0.0.0-20210525063256-abc453219eb5 fixed in 0.45.0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58190 | NONE0 | golang.org/x/net v0.0.0-20210525063256-abc453219eb5 fixed in 0.45.0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-29526 | NONE0 | golang.org/x/sys v0.0.0-20220114195835-da31bd327af9 fixed in 0.0.0-20220412211240-33da011f77ad | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-41717 | NONE0 | stdlib v1.17.11 fixed in 1.18.9, 1.19.4 | 5.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-24532 | NONE0 | stdlib v1.17.11 fixed in 1.19.7, 1.20.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-29409 | NONE0 | stdlib v1.17.11 fixed in 1.19.12, 1.20.7, 1.21.0-rc.4 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-39326 | NONE0 | stdlib v1.17.11 fixed in 1.20.12, 1.21.5 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-45284 | NONE0 | stdlib v1.17.11 fixed in 1.20.11, 1.21.4 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45289 | NONE0 | stdlib v1.17.11 fixed in 1.21.8, 1.22.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-45290 | NONE0 | stdlib v1.17.11 fixed in 1.21.8, 1.22.1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-22866 | NONE0 | stdlib v1.17.11 fixed in 1.22.12, 1.23.6, 1.24.0-rc.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22873 | NONE0 | stdlib v1.17.11 fixed in 1.23.9, 1.24.3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-47912 | NONE0 | stdlib v1.17.11 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58185 | NONE0 | stdlib v1.17.11 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58187 | NONE0 | stdlib v1.17.11 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58188 | NONE0 | stdlib v1.17.11 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58189 | NONE0 | stdlib v1.17.11 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61723 | NONE0 | stdlib v1.17.11 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61724 | NONE0 | stdlib v1.17.11 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61725 | NONE0 | stdlib v1.17.11 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61730 | NONE0 | stdlib v1.17.11 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.17.11 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42507 | NONE0 | stdlib v1.17.11 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58186 | NONE0 | stdlib v1.17.11 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc6 2.31-13+deb11u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc6 2.31-13+deb11u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-34180 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u8 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2024-13176 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-68160 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22870 | NONE0 | golang.org/x/net v0.0.0-20210614182718-04defd469f4e fixed in 0.36.0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22870 | NONE0 | stdlib v1.18 fixed in 1.23.7, 1.24.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22870 | NONE0 | golang.org/x/net v0.0.0-20210525063256-abc453219eb5 fixed in 0.36.0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22870 | NONE0 | stdlib v1.17.11 fixed in 1.23.7, 1.24.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-2582 | NONE0 | github.com/aws/aws-sdk-go v1.28.2 fixed in 1.34.0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-8058 | NONE0 | libc6 2.31-13+deb11u3 fixed in 2.31-13+deb11u14 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45341 | NONE0 | stdlib v1.18 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-45341 | NONE0 | stdlib v1.17.11 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2010-4756 | NONE0 | libc6 2.31-13+deb11u3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2024-33601 | NONE0 | libc6 2.31-13+deb11u3 fixed in 2.31-13+deb11u10 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-33602 | NONE0 | libc6 2.31-13+deb11u3 fixed in 2.31-13+deb11u10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69418 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-2511 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u2 | 54.0% Actively Exploited | Not Applicable |
| CVE-2024-9143 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u2 | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-30629 | NONE0 | stdlib v1.18 fixed in 1.17.11, 1.18.3 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-27139 | NONE0 | stdlib v1.18 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-8912 | NONE0 | github.com/aws/aws-sdk-go v1.28.2 fixed in 1.34.0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27139 | NONE0 | stdlib v1.17.11 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-27587 | NONE0 | openssl 1.1.1n-0+deb11u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| DLA-3972-1 | NONE0 | tzdata 2021a-1+deb11u4 fixed in 2024b-0+deb11u1 | — | Not Applicable |
| DLA-4085-1 | NONE0 | tzdata 2021a-1+deb11u4 fixed in 2025a-0+deb11u1 | — | Not Applicable |
| DLA-4105-1 | NONE0 | tzdata 2021a-1+deb11u4 fixed in 2025b-0+deb11u1 | — | Not Applicable |
| DLA-4403-1 | NONE0 | tzdata 2021a-1+deb11u4 fixed in 2025b-0+deb11u2 | — | Not Applicable |
| DLA-4569-1 | NONE0 | tzdata 2021a-1+deb11u4 fixed in 2026b-0+deb11u1 | — | Not Applicable |
| CVE-2022-30636 | NONE0 | golang.org/x/crypto v0.0.0-20210616213533-5ff15b29337e fixed in 0.0.0-20220525230936-793ad666bf5e | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46600 | NONE0 | golang.org/x/net v0.0.0-20210614182718-04defd469f4e fixed in 0.56.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39824 | NONE0 | golang.org/x/sys v0.0.0-20210630005230-0f9fa26af87c 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.38.0 fixed in 1.82.1 | — | Not Applicable |
| GHSA-m425-mq94-257g | NONE0 | google.golang.org/grpc v1.38.0 fixed in 1.56.3, 1.57.1, 1.58.3 | — | Not Applicable |
| CVE-2025-0913 | NONE0 | stdlib v1.18 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-20210817164053-32db794688a5 fixed in 0.0.0-20220525230936-793ad666bf5e | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46600 | NONE0 | golang.org/x/net v0.0.0-20210525063256-abc453219eb5 fixed in 0.56.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39824 | NONE0 | golang.org/x/sys v0.0.0-20220114195835-da31bd327af9 fixed in 0.44.0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56852 | NONE0 | golang.org/x/text v0.3.7 fixed in 0.39.0 | 0.4% Theoretical Threat | Not Applicable |
| GHSA-hrxh-6v49-42gf | NONE0 | google.golang.org/grpc v1.40.0 fixed in 1.82.1 | — | Not Applicable |
| GHSA-m425-mq94-257g | NONE0 | google.golang.org/grpc v1.40.0 fixed in 1.56.3, 1.57.1, 1.58.3 | — | Not Applicable |
| CVE-2025-0913 | NONE0 | stdlib v1.17.11 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.