Last scanned:
This image is acceptable for production, but remediating the identified vulnerabilities is recommended to reduce the attack surface. The main exposed-surface concerns are CVE-2026-27820 and CVE-2026-41316, both moderate-severity issues rather than high-severity findings. CVE-2026-27820 could allow memory corruption when the framework decompresses gzip data from a malicious target, while CVE-2026-41316 only becomes code execution if untrusted data is deserialized with Marshal.load while ERB is loaded, which is a non-default path. The 55 post-exploit findings are present but none reach the 6.0 severity threshold, so they are lower priority. Because the image is community-published and unverified, validate the publisher and apply remediation guidance before relying on it in production.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-27820 | MEDIUM6.66 | zlib 3.1.1 fixed in ~> 3.0.1, ~> 3.1.2, >= 3.2.3 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-41316 | MEDIUM6.48 | erb 4.0.3 fixed in ~> 4.0.3.1, ~> 4.0.4.1, ~> 6.0.1.1, >= 6.0.4 | 1.3% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-77214 | MEDIUM5.58 | libexpat 2.8.4-r0 fixed in 2.9.0-r0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42258 | MEDIUM5.3 | net-imap 0.4.19 fixed in ~> 0.4.24, ~> 0.5.14, >= 0.6.4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-47240 | MEDIUM5.18 | net-imap 0.4.19 fixed in ~> 0.5.15, >= 0.6.4.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-93990 | MEDIUM5.1 | libexpat 2.8.4-r0 fixed in 2.8.5-r0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-80212 | MEDIUM5.1 | resolv 0.3.0 fixed in ~> 0.3.2, >= 0.7.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-27171 | MEDIUM4.67 | zlib 1.3.1-r2 fixed in 1.3.2-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-61594 | LOW3.83 | uri 0.13.2 fixed in ~> 0.12.5, ~> 0.13.3, >= 1.0.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-13034 | LOW3.47 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-80213 | LOW3.4 | resolv 0.3.0 fixed in ~> 0.3.2, >= 0.7.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3784 | LOW3.31 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-102633 | LOW3.01 | libexpat 2.8.4-r0 fixed in 2.9.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42257 | LOW3 | net-imap 0.4.19 fixed in ~> 0.4.24, ~> 0.5.14, >= 0.6.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-58767 | LOW2.7 | rexml 3.3.9 fixed in >= 3.4.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-58767 | LOW2.7 | rexml 3.4.1 fixed in >= 3.4.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-8286 | LOW2.48 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-92392 | LOW2.48 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | LOW2.48 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-92392 | LOW2.48 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-22184 | LOW2.39 | zlib 1.3.1-r2 fixed in 1.3.2-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW2.29 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW2.29 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW2.29 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW2.29 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW2.29 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW2.29 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42245 | LOW2.29 | net-imap 0.4.19 fixed in ~> 0.4.24, ~> 0.5.14, >= 0.6.4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-42246 | LOW2.26 | net-imap 0.4.19 fixed in ~> 0.3.10, ~> 0.4.24, ~> 0.5.14, >= 0.6.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-47242 | LOW2.23 | net-imap 0.4.19 fixed in ~> 0.5.15, >= 0.6.4.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-43857 | LOW1.99 | net-imap 0.4.19 fixed in ~> 0.2.5, ~> 0.3.9, ~> 0.4.20, >= 0.5.7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42256 | LOW1.99 | net-imap 0.4.19 fixed in ~> 0.4.24, ~> 0.5.14, >= 0.6.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-47241 | LOW1.81 | net-imap 0.4.19 fixed in ~> 0.5.15, >= 0.6.4.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-46394 | LOW1.68 | busybox 1.37.0-r12 fixed in 1.37.0-r14 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-46394 | LOW1.68 | busybox-binsh 1.37.0-r12 fixed in 1.37.0-r14 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-46394 | LOW1.68 | ssl_client 1.37.0-r12 fixed in 1.37.0-r14 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-73648 | LOW1.65 | rails-html-sanitizer 1.6.2 fixed in >= 1.7.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14762 | LOW1.62 | aws-sdk-s3 1.182.0 fixed in >= 1.208.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-73490 | LOW1.44 | loofah 2.24.1 fixed in >= 2.25.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-68121 | NONE0 | stdlib v1.24.0 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-54906 | NONE0 | concurrent-ruby 1.3.5 fixed in >= 1.3.7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39821 | NONE0 | stdlib v1.24.0 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-56858 | NONE0 | stdlib v1.24.0 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-40200 | NONE0 | musl-utils 1.2.5-r9 fixed in 1.2.5-r11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39822 | NONE0 | stdlib v1.24.0 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-54904 | NONE0 | concurrent-ruby 1.3.5 fixed in >= 1.3.7 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-22874 | NONE0 | stdlib v1.24.0 fixed in 1.24.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61726 | NONE0 | stdlib v1.24.0 fixed in 1.24.12, 1.25.6 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-61729 | NONE0 | stdlib v1.24.0 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25679 | NONE0 | stdlib v1.24.0 fixed in 1.25.8, 1.26.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.24.0 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32280 | NONE0 | stdlib v1.24.0 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32281 | NONE0 | stdlib v1.24.0 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32283 | NONE0 | stdlib v1.24.0 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33811 | NONE0 | stdlib v1.24.0 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | stdlib v1.24.0 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-33818 | NONE0 | stdlib v1.24.0 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-39820 | NONE0 | stdlib v1.24.0 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39836 | NONE0 | stdlib v1.24.0 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42499 | NONE0 | stdlib v1.24.0 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.24.0 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56853 | NONE0 | stdlib v1.24.0 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56859 | NONE0 | stdlib v1.24.0 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56860 | NONE0 | stdlib v1.24.0 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-56862 | NONE0 | stdlib v1.24.0 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78667 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-78669 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97031 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58183 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61728 | NONE0 | stdlib v1.24.0 fixed in 1.24.12, 1.25.6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-47907 | NONE0 | stdlib v1.24.0 fixed in 1.23.12, 1.24.6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-4673 | NONE0 | stdlib v1.24.0 fixed in 1.23.10, 1.24.4 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-47906 | NONE0 | stdlib v1.24.0 fixed in 1.23.12, 1.24.6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61727 | NONE0 | stdlib v1.24.0 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39825 | NONE0 | stdlib v1.24.0 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56866 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94439 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32282 | NONE0 | stdlib v1.24.0 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32289 | NONE0 | stdlib v1.24.0 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94448 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97032 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6042 | NONE0 | musl-utils 1.2.5-r9 fixed in 1.2.5-r10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-54905 | NONE0 | concurrent-ruby 1.3.5 fixed in >= 1.3.7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32288 | NONE0 | stdlib v1.24.0 fixed in 1.25.9, 1.26.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22871 | NONE0 | stdlib v1.24.0 fixed in 1.23.8, 1.24.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-27142 | NONE0 | stdlib v1.24.0 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39823 | NONE0 | stdlib v1.24.0 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39826 | NONE0 | stdlib v1.24.0 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22873 | NONE0 | stdlib v1.24.0 fixed in 1.23.9, 1.24.3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-47912 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58185 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58187 | NONE0 | stdlib v1.24.0 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58189 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61723 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-61724 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61725 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61730 | NONE0 | stdlib v1.24.0 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.24.0 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42507 | NONE0 | stdlib v1.24.0 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-78663 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58186 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-54619 | NONE0 | sqlite3 2.9.4 fixed in >= 2.9.5 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54620 | NONE0 | sqlite3 2.9.4 fixed in >= 2.9.5 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22870 | NONE0 | stdlib v1.24.0 fixed in 1.23.7, 1.24.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56857 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-27139 | NONE0 | stdlib v1.24.0 fixed in 1.25.8, 1.26.1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58251 | NONE0 | busybox 1.37.0-r12 fixed in 1.37.0-r14 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58251 | NONE0 | busybox-binsh 1.37.0-r12 fixed in 1.37.0-r14 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-1965_1 | NONE0 | curl 8.14.1-r2 fixed in 8.14.1-r3 | — | Not Applicable |
| CVE-2026-1965_2 | NONE0 | curl 8.14.1-r2 fixed in 8.14.1-r3 | — | Not Applicable |
| CVE-2026-1965_1 | NONE0 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | — | Not Applicable |
| CVE-2026-1965_2 | NONE0 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | — | Not Applicable |
| CVE-2024-58251 | NONE0 | ssl_client 1.37.0-r12 fixed in 1.37.0-r14 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-85091 | NONE0 | zlib 1.3.1-r2 fixed in 1.3.2-r1 | 0.4% Theoretical Threat | Not Applicable |
| GHSA-mwm8-39rw-8826 | NONE0 | sqlite3 2.9.4 fixed in >= 2.9.6 | — | Not Applicable |
| CVE-2025-0913 | NONE0 | stdlib v1.24.0 fixed in 1.23.10, 1.24.4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-58188 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 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.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
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.