Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker could exploit CVE-2023-24538 to inject malicious JavaScript via Go templates, or CVE-2021-3450 to bypass CA certificate validation, leading to unauthorized access or service disruption. Upgrading the Go runtime and OpenSSL packages to patched versions fully mitigates these top findings. Note that CVE-2021-3450 only affects configurations that explicitly enable the X509_V_FLAG_X509_STRICT flag.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2023-24538 | CRITICAL9.8 | stdlib v1.14.7 fixed in 1.19.8, 1.20.3 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24540 | CRITICAL9.8 | stdlib v1.14.7 fixed in 1.19.9, 1.20.4 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-24790 | CRITICAL9.8 | stdlib v1.14.7 fixed in 1.21.11, 1.22.4 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-23840 | CRITICAL9.75 | libcrypto1.1 1.1.1g-r0 fixed in 1.1.1j-r0 | 50.7% Actively Exploited | Directly Exposed |
| CVE-2021-23840 | CRITICAL9.75 | libssl1.1 1.1.1g-r0 fixed in 1.1.1j-r0 | 50.7% Actively Exploited | Directly Exposed |
| CVE-2023-45288 | CRITICAL9.75 | stdlib v1.14.7 fixed in 1.21.9, 1.22.2 | 92.0% Actively Exploited | Directly Exposed |
| CVE-2022-23806 | CRITICAL9.1 | stdlib v1.14.7 fixed in 1.16.14, 1.17.7 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3450 | HIGH8.51 | libcrypto1.1 1.1.1g-r0 fixed in 1.1.1k-r0 | 18.3% High Exploitation Risk | Directly Exposed |
| CVE-2021-3450 | HIGH8.51 | libssl1.1 1.1.1g-r0 fixed in 1.1.1k-r0 | 18.3% High Exploitation Risk | Directly Exposed |
| CVE-2025-68121 | HIGH8.5 | stdlib v1.14.7 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-3449 | HIGH7.67 | libcrypto1.1 1.1.1g-r0 fixed in 1.1.1k-r0 | 62.9% Actively Exploited | Directly Exposed |
| CVE-2021-3449 | HIGH7.67 | libssl1.1 1.1.1g-r0 fixed in 1.1.1k-r0 | 62.9% Actively Exploited | Directly Exposed |
| CVE-2020-28362 | HIGH7.5 | stdlib v1.14.7 fixed in 1.14.12, 1.15.5 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-27918 | HIGH7.5 | stdlib v1.14.7 fixed in 1.15.9, 1.16.1 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33196 | HIGH7.5 | stdlib v1.14.7 fixed in 1.15.13, 1.16.5 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33198 | HIGH7.5 | stdlib v1.14.7 fixed in 1.15.13, 1.16.5 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-39293 | HIGH7.5 | stdlib v1.14.7 fixed in 1.16.8, 1.17.1 | 6.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-41771 | HIGH7.5 | stdlib v1.14.7 fixed in 1.16.10, 1.17.3 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-41772 | HIGH7.5 | stdlib v1.14.7 fixed in 1.16.10, 1.17.3 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44716 | HIGH7.5 | stdlib v1.14.7 fixed in 1.16.12, 1.17.5 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23772 | HIGH7.5 | stdlib v1.14.7 fixed in 1.16.14, 1.17.7 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24675 | HIGH7.5 | stdlib v1.14.7 fixed in 1.17.9, 1.18.1 | 10.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24921 | HIGH7.5 | stdlib v1.14.7 fixed in 1.16.15, 1.17.8 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27664 | HIGH7.5 | stdlib v1.14.7 fixed in 1.18.6, 1.19.1 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28131 | HIGH7.5 | stdlib v1.14.7 fixed in 1.17.12, 1.18.4 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28327 | HIGH7.5 | stdlib v1.14.7 fixed in 1.17.9, 1.18.1 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2879 | HIGH7.5 | stdlib v1.14.7 fixed in 1.18.7, 1.19.2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2880 | HIGH7.5 | stdlib v1.14.7 fixed in 1.18.7, 1.19.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29804 | HIGH7.5 | stdlib v1.14.7 fixed in 1.17.11, 1.18.3 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30630 | HIGH7.5 | stdlib v1.14.7 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30631 | HIGH7.5 | stdlib v1.14.7 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30632 | HIGH7.5 | stdlib v1.14.7 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30633 | HIGH7.5 | stdlib v1.14.7 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30634 | HIGH7.5 | stdlib v1.14.7 fixed in 1.17.11, 1.18.3 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30635 | HIGH7.5 | stdlib v1.14.7 fixed in 1.17.12, 1.18.4 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32189 | HIGH7.5 | stdlib v1.14.7 fixed in 1.17.13, 1.18.5 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41715 | HIGH7.5 | stdlib v1.14.7 fixed in 1.18.7, 1.19.2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41720 | HIGH7.5 | stdlib v1.14.7 fixed in 1.18.9, 1.19.4 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41722 | HIGH7.5 | stdlib v1.14.7 fixed in 1.19.6, 1.20.1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41723 | HIGH7.5 | stdlib v1.14.7 fixed in 1.19.6, 1.20.1 | 4.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41724 | HIGH7.5 | stdlib v1.14.7 fixed in 1.19.6, 1.20.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41725 | HIGH7.5 | stdlib v1.14.7 fixed in 1.19.6, 1.20.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24534 | HIGH7.5 | stdlib v1.14.7 fixed in 1.19.8, 1.20.3 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24536 | HIGH7.5 | stdlib v1.14.7 fixed in 1.19.8, 1.20.3 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24537 | HIGH7.5 | stdlib v1.14.7 fixed in 1.19.8, 1.20.3 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39325 | HIGH7.5 | stdlib v1.14.7 fixed in 1.20.10, 1.21.3 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45283 | HIGH7.5 | stdlib v1.14.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.14.7 fixed in 1.20.0 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34156 | HIGH7.5 | stdlib v1.14.7 fixed in 1.22.7, 1.23.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-61726 | HIGH7.5 | stdlib v1.14.7 fixed in 1.24.12, 1.25.6 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33195 | HIGH7.3 | stdlib v1.14.7 fixed in 1.15.13, 1.16.5 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24539 | HIGH7.3 | stdlib v1.14.7 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29400 | HIGH7.3 | stdlib v1.14.7 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30580 | MEDIUM6.63 | stdlib v1.14.7 fixed in 1.17.11, 1.18.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-29403 | MEDIUM6.63 | stdlib v1.14.7 fixed in 1.19.10, 1.20.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39822 | MEDIUM6.63 | stdlib v1.14.7 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-3114 | MEDIUM6.5 | stdlib v1.14.7 fixed in 1.14.14, 1.15.7 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-34558 | MEDIUM6.5 | stdlib v1.14.7 fixed in 1.15.14, 1.16.6 | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1705 | MEDIUM6.5 | stdlib v1.14.7 fixed in 1.17.12, 1.18.4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32148 | MEDIUM6.5 | stdlib v1.14.7 fixed in 1.17.12, 1.18.4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29406 | MEDIUM6.5 | stdlib v1.14.7 fixed in 1.19.11, 1.20.6 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41716 | MEDIUM6.38 | stdlib v1.14.7 fixed in 1.18.8, 1.19.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-61729 | MEDIUM6.38 | stdlib v1.14.7 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25679 | MEDIUM6.38 | stdlib v1.14.7 fixed in 1.25.8, 1.26.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-27145 | MEDIUM6.38 | stdlib v1.14.7 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32280 | MEDIUM6.38 | stdlib v1.14.7 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32281 | MEDIUM6.38 | stdlib v1.14.7 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32283 | MEDIUM6.38 | stdlib v1.14.7 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33811 | MEDIUM6.38 | stdlib v1.14.7 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | stdlib v1.14.7 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39820 | MEDIUM6.38 | stdlib v1.14.7 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39836 | MEDIUM6.38 | stdlib v1.14.7 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42499 | MEDIUM6.38 | stdlib v1.14.7 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42504 | MEDIUM6.38 | stdlib v1.14.7 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-58183 | MEDIUM6.38 | stdlib v1.14.7 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61728 | MEDIUM6.38 | stdlib v1.14.7 fixed in 1.24.12, 1.25.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2020-24553 | MEDIUM6.1 | stdlib v1.14.7 fixed in 1.14.8, 1.15.1 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-47907 | MEDIUM5.95 | stdlib v1.14.7 fixed in 1.23.12, 1.24.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-1971 | MEDIUM5.9 | libcrypto1.1 1.1.1g-r0 fixed in 1.1.1i-r0 | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-23841 | MEDIUM5.9 | libcrypto1.1 1.1.1g-r0 fixed in 1.1.1j-r0 | 7.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-1971 | MEDIUM5.9 | libssl1.1 1.1.1g-r0 fixed in 1.1.1i-r0 | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-23841 | MEDIUM5.9 | libssl1.1 1.1.1g-r0 fixed in 1.1.1j-r0 | 7.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-31525 | MEDIUM5.9 | stdlib v1.14.7 fixed in 1.15.12, 1.16.4 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-36221 | MEDIUM5.9 | stdlib v1.14.7 fixed in 1.15.15, 1.16.7 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-24791 | MEDIUM5.9 | stdlib v1.14.7 fixed in 1.21.12, 1.22.5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34158 | MEDIUM5.9 | stdlib v1.14.7 fixed in 1.22.7, 1.23.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-4673 | MEDIUM5.78 | stdlib v1.14.7 fixed in 1.23.10, 1.24.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-24785 | MEDIUM5.52 | stdlib v1.14.7 fixed in 1.21.8, 1.22.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-47906 | MEDIUM5.52 | stdlib v1.14.7 fixed in 1.23.12, 1.24.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61727 | MEDIUM5.52 | stdlib v1.14.7 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39825 | MEDIUM5.52 | stdlib v1.14.7 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-36159 | MEDIUM5.46 | apk-tools 2.10.4-r2 fixed in 2.10.7-r0 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-32282 | MEDIUM5.44 | stdlib v1.14.7 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-24784 | MEDIUM5.4 | stdlib v1.14.7 fixed in 1.21.8, 1.22.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33197 | MEDIUM5.3 | stdlib v1.14.7 fixed in 1.15.13, 1.16.5 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29526 | MEDIUM5.3 | stdlib v1.14.7 fixed in 1.17.10, 1.18.2 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41717 | MEDIUM5.3 | stdlib v1.14.7 fixed in 1.18.9, 1.19.4 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29409 | MEDIUM5.3 | stdlib v1.14.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.14.7 fixed in 1.20.12, 1.21.5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45289 | MEDIUM5.3 | stdlib v1.14.7 fixed in 1.21.8, 1.22.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45290 | MEDIUM5.3 | stdlib v1.14.7 fixed in 1.21.8, 1.22.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39318 | MEDIUM5.18 | stdlib v1.14.7 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-39319 | MEDIUM5.18 | stdlib v1.14.7 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-32289 | MEDIUM5.18 | stdlib v1.14.7 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-24783 | MEDIUM5.02 | stdlib v1.14.7 fixed in 1.21.8, 1.22.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-34155 | MEDIUM5.02 | stdlib v1.14.7 fixed in 1.22.7, 1.23.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-45336 | MEDIUM5.02 | stdlib v1.14.7 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.14.7 fixed in 1.16.12, 1.17.5 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2020-28928 | MEDIUM4.67 | musl 1.1.22-r3 fixed in 1.1.22-r4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-1962 | MEDIUM4.67 | stdlib v1.14.7 fixed in 1.17.12, 1.18.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-24789 | MEDIUM4.67 | stdlib v1.14.7 fixed in 1.21.11, 1.22.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32288 | MEDIUM4.67 | stdlib v1.14.7 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-22871 | MEDIUM4.59 | stdlib v1.14.7 fixed in 1.23.8, 1.24.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-27142 | MEDIUM4.59 | stdlib v1.14.7 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39823 | MEDIUM4.59 | stdlib v1.14.7 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39826 | MEDIUM4.59 | stdlib v1.14.7 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-30139 | MEDIUM4.5 | apk-tools 2.10.4-r2 fixed in 2.10.6-r0 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-28831 | MEDIUM4.5 | busybox 1.30.1-r3 fixed in 1.30.1-r5 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2021-28831 | MEDIUM4.5 | ssl_client 1.30.1-r3 fixed in 1.30.1-r5 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-24532 | MEDIUM4.5 | stdlib v1.14.7 fixed in 1.19.7, 1.20.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-45284 | MEDIUM4.5 | stdlib v1.14.7 fixed in 1.20.11, 1.21.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-22866 | MEDIUM4.5 | stdlib v1.14.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.14.7 fixed in 1.23.9, 1.24.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-47912 | MEDIUM4.5 | stdlib v1.14.7 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58185 | MEDIUM4.5 | stdlib v1.14.7 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58187 | MEDIUM4.5 | stdlib v1.14.7 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58188 | MEDIUM4.5 | stdlib v1.14.7 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58189 | MEDIUM4.5 | stdlib v1.14.7 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61723 | MEDIUM4.5 | stdlib v1.14.7 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61724 | MEDIUM4.5 | stdlib v1.14.7 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61725 | MEDIUM4.5 | stdlib v1.14.7 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61730 | MEDIUM4.5 | stdlib v1.14.7 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42505 | MEDIUM4.5 | stdlib v1.14.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.14.7 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58186 | MEDIUM4.5 | stdlib v1.14.7 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-22870 | LOW3.74 | stdlib v1.14.7 fixed in 1.23.7, 1.24.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-23839 | LOW3.7 | libcrypto1.1 1.1.1g-r0 fixed in 1.1.1j-r0 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-23839 | LOW3.7 | libssl1.1 1.1.1g-r0 fixed in 1.1.1j-r0 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45341 | LOW3.57 | stdlib v1.14.7 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-30629 | LOW2.63 | stdlib v1.14.7 fixed in 1.17.11, 1.18.3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-27139 | LOW2.12 | stdlib v1.14.7 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2020-28928 | NONE0 | musl-utils 1.1.22-r3 fixed in 1.1.22-r4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-0913 | NONE0 | stdlib v1.14.7 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.