Last scanned:
This image is safe for production use. Although the image contains 14 post-exploit findings, they are low severity (maximum 4.32) and none are exposed on the network. The two most notable CVEs (CVE-2021-42385 and CVE-2021-42386) affect busybox in a post-exploit context and pose minimal risk in a typical Vault deployment. The image is from a trusted publisher, pinned by digest, and has no exposed surface findings.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| 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-36159 | LOW3.28 | apk-tools 2.12.5-r0 fixed in 2.12.6-r0 | 2.6% Low-Moderate 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-30065 | LOW2.81 | busybox 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-42374 | LOW2.7 | busybox 1.32.1-r6 fixed in 1.32.1-r7 | 0.6% Theoretical Threat | Post-Exploit |
| 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-42381 | LOW2.59 | busybox 1.32.1-r6 fixed in 1.32.1-r7 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42382 | LOW2.59 | busybox 1.32.1-r6 fixed in 1.32.1-r7 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42383 | LOW2.59 | busybox 1.32.1-r6 fixed in 1.32.1-r7 | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42384 | LOW2.59 | busybox 1.32.1-r6 fixed in 1.32.1-r7 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-68121 | NONE0 | stdlib v1.15.10 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2021-3711 | NONE0 | libcrypto1.1 1.1.1k-r0 fixed in 1.1.1l-r0 | 87.8% Actively Exploited | Not Applicable |
| CVE-2021-3711 | NONE0 | libssl1.1 1.1.1k-r0 fixed in 1.1.1l-r0 | 87.8% Actively Exploited | Not Applicable |
| CVE-2022-37434 | NONE0 | zlib 1.2.11-r3 fixed in 1.2.12-r2 | 15.5% High Exploitation Risk | Not Applicable |
| CVE-2023-24538 | NONE0 | stdlib v1.15.10 fixed in 1.19.8, 1.20.3 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-24540 | NONE0 | stdlib v1.15.10 fixed in 1.19.9, 1.20.4 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-24790 | NONE0 | stdlib v1.15.10 fixed in 1.21.11, 1.22.4 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-23806 | NONE0 | stdlib v1.15.10 fixed in 1.16.14, 1.17.7 | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-28391 | NONE0 | ssl_client 1.32.1-r6 fixed in 1.32.1-r8 | 3.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-30065 | NONE0 | ssl_client 1.32.1-r6 fixed in 1.32.1-r9 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-30580 | NONE0 | stdlib v1.15.10 fixed in 1.17.11, 1.18.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-29403 | NONE0 | stdlib v1.15.10 fixed in 1.19.10, 1.20.5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-39822 | NONE0 | stdlib v1.15.10 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0778 | NONE0 | libcrypto1.1 1.1.1k-r0 fixed in 1.1.1n-r0 | 70.6% Actively Exploited | Not Applicable |
| CVE-2022-0778 | NONE0 | libssl1.1 1.1.1k-r0 fixed in 1.1.1n-r0 | 70.6% Actively Exploited | Not Applicable |
| CVE-2018-25032 | NONE0 | zlib 1.2.11-r3 fixed in 1.2.12-r0 | 52.1% Actively Exploited | Not Applicable |
| CVE-2021-33196 | NONE0 | stdlib v1.15.10 fixed in 1.15.13, 1.16.5 | 3.5% Low-Moderate Risk | Not Applicable |
| CVE-2021-33198 | NONE0 | stdlib v1.15.10 fixed in 1.15.13, 1.16.5 | 3.4% Low-Moderate Risk | Not Applicable |
| CVE-2021-39293 | NONE0 | stdlib v1.15.10 fixed in 1.16.8, 1.17.1 | 6.9% Low-Moderate Risk | Not Applicable |
| CVE-2021-41771 | NONE0 | stdlib v1.15.10 fixed in 1.16.10, 1.17.3 | 4.4% Low-Moderate Risk | Not Applicable |
| CVE-2021-41772 | NONE0 | stdlib v1.15.10 fixed in 1.16.10, 1.17.3 | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-44716 | NONE0 | stdlib v1.15.10 fixed in 1.16.12, 1.17.5 | 4.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-23772 | NONE0 | stdlib v1.15.10 fixed in 1.16.14, 1.17.7 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-24675 | NONE0 | stdlib v1.15.10 fixed in 1.17.9, 1.18.1 | 10.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-24921 | NONE0 | stdlib v1.15.10 fixed in 1.16.15, 1.17.8 | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-27664 | NONE0 | stdlib v1.15.10 fixed in 1.18.6, 1.19.1 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-28131 | NONE0 | stdlib v1.15.10 fixed in 1.17.12, 1.18.4 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-28327 | NONE0 | stdlib v1.15.10 fixed in 1.17.9, 1.18.1 | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-2879 | NONE0 | stdlib v1.15.10 fixed in 1.18.7, 1.19.2 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-2880 | NONE0 | stdlib v1.15.10 fixed in 1.18.7, 1.19.2 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-29804 | NONE0 | stdlib v1.15.10 fixed in 1.17.11, 1.18.3 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-30630 | NONE0 | stdlib v1.15.10 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-30631 | NONE0 | stdlib v1.15.10 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-30632 | NONE0 | stdlib v1.15.10 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-30633 | NONE0 | stdlib v1.15.10 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-30634 | NONE0 | stdlib v1.15.10 fixed in 1.17.11, 1.18.3 | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-30635 | NONE0 | stdlib v1.15.10 fixed in 1.17.12, 1.18.4 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-32189 | NONE0 | stdlib v1.15.10 fixed in 1.17.13, 1.18.5 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-41715 | NONE0 | stdlib v1.15.10 fixed in 1.18.7, 1.19.2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-41716 | NONE0 | stdlib v1.15.10 fixed in 1.18.8, 1.19.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-41720 | NONE0 | stdlib v1.15.10 fixed in 1.18.9, 1.19.4 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-41722 | NONE0 | stdlib v1.15.10 fixed in 1.19.6, 1.20.1 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-41723 | NONE0 | stdlib v1.15.10 fixed in 1.19.6, 1.20.1 | 4.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-41724 | NONE0 | stdlib v1.15.10 fixed in 1.19.6, 1.20.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-41725 | NONE0 | stdlib v1.15.10 fixed in 1.19.6, 1.20.1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-24534 | NONE0 | stdlib v1.15.10 fixed in 1.19.8, 1.20.3 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2023-24536 | NONE0 | stdlib v1.15.10 fixed in 1.19.8, 1.20.3 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-24537 | NONE0 | stdlib v1.15.10 fixed in 1.19.8, 1.20.3 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-39325 | NONE0 | stdlib v1.15.10 fixed in 1.20.10, 1.21.3 | 3.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-45283 | NONE0 | stdlib v1.15.10 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.15.10 fixed in 1.20.0 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-45288 | NONE0 | stdlib v1.15.10 fixed in 1.21.9, 1.22.2 | 92.0% Actively Exploited | Not Applicable |
| CVE-2024-34156 | NONE0 | stdlib v1.15.10 fixed in 1.22.7, 1.23.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-61726 | NONE0 | stdlib v1.15.10 fixed in 1.24.12, 1.25.6 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-61729 | NONE0 | stdlib v1.15.10 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25679 | NONE0 | stdlib v1.15.10 fixed in 1.25.8, 1.26.1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.15.10 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32280 | NONE0 | stdlib v1.15.10 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32281 | NONE0 | stdlib v1.15.10 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32283 | NONE0 | stdlib v1.15.10 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33811 | NONE0 | stdlib v1.15.10 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | stdlib v1.15.10 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39820 | NONE0 | stdlib v1.15.10 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39836 | NONE0 | stdlib v1.15.10 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42499 | NONE0 | stdlib v1.15.10 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.15.10 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58183 | NONE0 | stdlib v1.15.10 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61728 | NONE0 | stdlib v1.15.10 fixed in 1.24.12, 1.25.6 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-3712 | NONE0 | libcrypto1.1 1.1.1k-r0 fixed in 1.1.1l-r0 | 50.4% Actively Exploited | Not Applicable |
| CVE-2021-3712 | NONE0 | libssl1.1 1.1.1k-r0 fixed in 1.1.1l-r0 | 50.4% Actively Exploited | Not Applicable |
| CVE-2021-33195 | NONE0 | stdlib v1.15.10 fixed in 1.15.13, 1.16.5 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-24539 | NONE0 | stdlib v1.15.10 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-29400 | NONE0 | stdlib v1.15.10 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2021-42378 | NONE0 | ssl_client 1.32.1-r6 fixed in 1.32.1-r7 | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2021-42379 | NONE0 | ssl_client 1.32.1-r6 fixed in 1.32.1-r7 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2021-42380 | NONE0 | ssl_client 1.32.1-r6 fixed in 1.32.1-r7 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2021-42381 | NONE0 | ssl_client 1.32.1-r6 fixed in 1.32.1-r7 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2021-42382 | NONE0 | ssl_client 1.32.1-r6 fixed in 1.32.1-r7 | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2021-42383 | NONE0 | ssl_client 1.32.1-r6 fixed in 1.32.1-r7 | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-42384 | NONE0 | ssl_client 1.32.1-r6 fixed in 1.32.1-r7 | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2021-42385 | NONE0 | ssl_client 1.32.1-r6 fixed in 1.32.1-r7 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2021-42386 | NONE0 | ssl_client 1.32.1-r6 fixed in 1.32.1-r7 | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-47907 | NONE0 | stdlib v1.15.10 fixed in 1.23.12, 1.24.6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-4673 | NONE0 | stdlib v1.15.10 fixed in 1.23.10, 1.24.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-34558 | NONE0 | stdlib v1.15.10 fixed in 1.15.14, 1.16.6 | 7.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-1705 | NONE0 | stdlib v1.15.10 fixed in 1.17.12, 1.18.4 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-32148 | NONE0 | stdlib v1.15.10 fixed in 1.17.12, 1.18.4 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-29406 | NONE0 | stdlib v1.15.10 fixed in 1.19.11, 1.20.6 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-24785 | NONE0 | stdlib v1.15.10 fixed in 1.21.8, 1.22.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-47906 | NONE0 | stdlib v1.15.10 fixed in 1.23.12, 1.24.6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61727 | NONE0 | stdlib v1.15.10 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39825 | NONE0 | stdlib v1.15.10 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32282 | NONE0 | stdlib v1.15.10 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-39318 | NONE0 | stdlib v1.15.10 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-39319 | NONE0 | stdlib v1.15.10 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-32289 | NONE0 | stdlib v1.15.10 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-31525 | NONE0 | stdlib v1.15.10 fixed in 1.15.12, 1.16.4 | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-36221 | NONE0 | stdlib v1.15.10 fixed in 1.15.15, 1.16.7 | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-24783 | NONE0 | stdlib v1.15.10 fixed in 1.21.8, 1.22.1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-24791 | NONE0 | stdlib v1.15.10 fixed in 1.21.12, 1.22.5 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-34155 | NONE0 | stdlib v1.15.10 fixed in 1.22.7, 1.23.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-34158 | NONE0 | stdlib v1.15.10 fixed in 1.22.7, 1.23.1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2024-45336 | NONE0 | stdlib v1.15.10 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-42375 | NONE0 | ssl_client 1.32.1-r6 fixed in 1.32.1-r7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-1962 | NONE0 | stdlib v1.15.10 fixed in 1.17.12, 1.18.4 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-24789 | NONE0 | stdlib v1.15.10 fixed in 1.21.11, 1.22.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32288 | NONE0 | stdlib v1.15.10 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-24784 | NONE0 | stdlib v1.15.10 fixed in 1.21.8, 1.22.1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-22871 | NONE0 | stdlib v1.15.10 fixed in 1.23.8, 1.24.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-27142 | NONE0 | stdlib v1.15.10 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39823 | NONE0 | stdlib v1.15.10 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39826 | NONE0 | stdlib v1.15.10 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-2097 | NONE0 | libcrypto1.1 1.1.1k-r0 fixed in 1.1.1q-r0 | 4.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-2097 | NONE0 | libssl1.1 1.1.1k-r0 fixed in 1.1.1q-r0 | 4.4% Low-Moderate Risk | Not Applicable |
| CVE-2021-42374 | NONE0 | ssl_client 1.32.1-r6 fixed in 1.32.1-r7 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-33197 | NONE0 | stdlib v1.15.10 fixed in 1.15.13, 1.16.5 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-29526 | NONE0 | stdlib v1.15.10 fixed in 1.17.10, 1.18.2 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-41717 | NONE0 | stdlib v1.15.10 fixed in 1.18.9, 1.19.4 | 5.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-24532 | NONE0 | stdlib v1.15.10 fixed in 1.19.7, 1.20.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-29409 | NONE0 | stdlib v1.15.10 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.15.10 fixed in 1.20.12, 1.21.5 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-45284 | NONE0 | stdlib v1.15.10 fixed in 1.20.11, 1.21.4 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45289 | NONE0 | stdlib v1.15.10 fixed in 1.21.8, 1.22.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-45290 | NONE0 | stdlib v1.15.10 fixed in 1.21.8, 1.22.1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-22866 | NONE0 | stdlib v1.15.10 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.15.10 fixed in 1.23.9, 1.24.3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-47912 | NONE0 | stdlib v1.15.10 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58185 | NONE0 | stdlib v1.15.10 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58187 | NONE0 | stdlib v1.15.10 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58188 | NONE0 | stdlib v1.15.10 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58189 | NONE0 | stdlib v1.15.10 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61723 | NONE0 | stdlib v1.15.10 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61724 | NONE0 | stdlib v1.15.10 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61725 | NONE0 | stdlib v1.15.10 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61730 | NONE0 | stdlib v1.15.10 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.15.10 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.15.10 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58186 | NONE0 | stdlib v1.15.10 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-44717 | NONE0 | stdlib v1.15.10 fixed in 1.16.12, 1.17.5 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-22870 | NONE0 | stdlib v1.15.10 fixed in 1.23.7, 1.24.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-45341 | NONE0 | stdlib v1.15.10 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-30629 | NONE0 | stdlib v1.15.10 fixed in 1.17.11, 1.18.3 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-27139 | NONE0 | stdlib v1.15.10 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-0913 | NONE0 | stdlib v1.15.10 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.