Last scanned:
This base/runtime image ships critical vulnerabilities that any image built on it would inherit; they must be remediated before the final image goes to production. An attacker reaching the Node process could exploit CVE-2026-111497 to execute code or read process memory, and the scan found it is already being exploited in the wild. Because the image runs as root by default and its Alpine base is past end of support, the consequences are amplified for every derived service. Note: CVE-2025-15467 only applies if the application parses untrusted S/MIME or CMS data, and the CVE-2026-21710 crash only occurs if the app reads headersDistinct. The practical remediation is to rebuild on a supported base with a patched Node runtime and update the affected OpenSSL libraries in the final image. Note: this is a general-purpose base/runtime image — many findings live in components that an application built on top may never load, so actual exploitability depends on the final image. For an accurate risk picture, re-scan the final application image with context.
Hardening plan for this image · 5 steps. The first closes an actively exploited CVE.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-111497 | CRITICAL10 | node 16.19.1 No fix yet | 88.0% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2026-21710 | HIGH8.62 | node 16.19.1 No fix yet | 25.4% High Exploitation Risk | Directly ExposedContext importance: HIGH |
| CVE-2025-15467 | HIGH8 | libcrypto3 3.0.8-r0 fixed in 3.0.19-r0 | 74.8% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2025-15467 | HIGH8 | libssl3 3.0.8-r0 fixed in 3.0.19-r0 | 74.8% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-42282 | HIGH7.84 | ip 2.0.0 fixed in 2.0.1, 1.1.9 | 1.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2024-6119 | HIGH7.8 | libcrypto3 3.0.8-r0 fixed in 3.0.15-r0 | 66.6% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2024-6119 | HIGH7.8 | libssl3 3.0.8-r0 fixed in 3.0.15-r0 | 66.6% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-2650 | MEDIUM6.76 | libcrypto3 3.0.8-r0 fixed in 3.0.9-r0 | 75.4% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-2650 | MEDIUM6.76 | libssl3 3.0.8-r0 fixed in 3.0.9-r0 | 75.4% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2024-29415 | MEDIUM6.48 | ip 2.0.0 No fix yet | 8.3% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-0464 | MEDIUM6 | libcrypto3 3.0.8-r0 fixed in 3.0.8-r1 | 4.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-5363 | MEDIUM6 | libcrypto3 3.0.8-r0 fixed in 3.0.12-r0 | 3.9% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-0464 | MEDIUM6 | libssl3 3.0.8-r0 fixed in 3.0.8-r1 | 4.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-5363 | MEDIUM6 | libssl3 3.0.8-r0 fixed in 3.0.12-r0 | 3.9% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102276 | MEDIUM6 | brace-expansion 1.1.11 fixed in 5.0.10, 3.0.7, 2.1.5, 1.1.19 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102278 | MEDIUM6 | brace-expansion 1.1.11 fixed in 5.0.11, 3.0.8, 2.1.6, 1.1.20 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-14257 | MEDIUM6 | brace-expansion 1.1.11 fixed in 5.0.8, 3.0.3, 2.1.3, 1.1.17 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-69152 | MEDIUM6 | brace-expansion 1.1.11 fixed in 1.1.18, 2.1.4, 3.0.6, 5.0.9 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102276 | MEDIUM6 | brace-expansion 2.0.1 fixed in 5.0.10, 3.0.7, 2.1.5, 1.1.19 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102278 | MEDIUM6 | brace-expansion 2.0.1 fixed in 5.0.11, 3.0.8, 2.1.6, 1.1.20 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-14257 | MEDIUM6 | brace-expansion 2.0.1 fixed in 5.0.8, 3.0.3, 2.1.3, 1.1.17 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-69152 | MEDIUM6 | brace-expansion 2.0.1 fixed in 1.1.18, 2.1.4, 3.0.6, 5.0.9 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-24001 | MEDIUM6 | diff 5.1.0 fixed in 8.0.3, 5.2.2, 4.0.4, 3.5.1 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2022-25881 | MEDIUM6 | http-cache-semantics 4.1.0 fixed in 4.1.1 | 1.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93748 | MEDIUM6 | http-cache-semantics 4.1.0 No fix yet | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-26996 | MEDIUM6 | minimatch 3.1.2 fixed in 10.2.1, 9.0.6, 8.0.5, 7.4.7, 6.2.1, 5.1.7, 4.2.4, 3.1.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-27903 | MEDIUM6 | minimatch 3.1.2 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-27904 | MEDIUM6 | minimatch 3.1.2 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.4 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-26996 | MEDIUM6 | minimatch 5.1.0 fixed in 10.2.1, 9.0.6, 8.0.5, 7.4.7, 6.2.1, 5.1.7, 4.2.4, 3.1.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-27903 | MEDIUM6 | minimatch 5.1.0 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-27904 | MEDIUM6 | minimatch 5.1.0 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.4 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2022-25883 | MEDIUM6 | semver 7.3.7 fixed in 7.5.2, 6.3.1, 5.7.2 | 2.8% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-30589 | MEDIUM6 | node 16.19.1 No fix yet | 3.9% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-21637 | MEDIUM6 | node 16.19.1 No fix yet | 1.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2025-26519 | MEDIUM5.95 | musl 1.2.3-r4 fixed in 1.2.3-r6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-26519 | MEDIUM5.95 | musl-utils 1.2.3-r4 fixed in 1.2.3-r6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6237 | MEDIUM5.9 | libcrypto3 3.0.8-r0 fixed in 3.0.12-r3 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | libcrypto3 3.0.8-r0 fixed in 3.0.14-r0 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.9 | libcrypto3 3.0.8-r0 fixed in 3.0.19-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.9 | libcrypto3 3.0.8-r0 fixed in 3.0.19-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-6237 | MEDIUM5.9 | libssl3 3.0.8-r0 fixed in 3.0.12-r3 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | libssl3 3.0.8-r0 fixed in 3.0.14-r0 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.9 | libssl3 3.0.8-r0 fixed in 3.0.19-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.9 | libssl3 3.0.8-r0 fixed in 3.0.19-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-21713 | MEDIUM5.9 | node 16.19.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-21717 | MEDIUM5.9 | node 16.19.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-32002 | MEDIUM5.88 | node 16.19.1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | libcrypto3 3.0.8-r0 fixed in 3.0.19-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | libcrypto3 3.0.8-r0 fixed in 3.0.14-r0 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | libssl3 3.0.8-r0 fixed in 3.0.19-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | libssl3 3.0.8-r0 fixed in 3.0.14-r0 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libcrypto3 3.0.8-r0 fixed in 3.0.12-r4 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-22795 | MEDIUM5.5 | libcrypto3 3.0.8-r0 fixed in 3.0.19-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libssl3 3.0.8-r0 fixed in 3.0.12-r4 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-22795 | MEDIUM5.5 | libssl3 3.0.8-r0 fixed in 3.0.19-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-0465 | MEDIUM5.3 | libcrypto3 3.0.8-r0 fixed in 3.0.8-r2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0466 | MEDIUM5.3 | libcrypto3 3.0.8-r0 fixed in 3.0.8-r3 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3446 | MEDIUM5.3 | libcrypto3 3.0.8-r0 fixed in 3.0.9-r3 | 6.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3817 | MEDIUM5.3 | libcrypto3 3.0.8-r0 fixed in 3.0.10-r0 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | libcrypto3 3.0.8-r0 fixed in 3.0.12-r1 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4603 | MEDIUM5.3 | libcrypto3 3.0.8-r0 fixed in 3.0.13-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0465 | MEDIUM5.3 | libssl3 3.0.8-r0 fixed in 3.0.8-r2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0466 | MEDIUM5.3 | libssl3 3.0.8-r0 fixed in 3.0.8-r3 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3446 | MEDIUM5.3 | libssl3 3.0.8-r0 fixed in 3.0.9-r3 | 6.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3817 | MEDIUM5.3 | libssl3 3.0.8-r0 fixed in 3.0.10-r0 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | libssl3 3.0.8-r0 fixed in 3.0.12-r1 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4603 | MEDIUM5.3 | libssl3 3.0.8-r0 fixed in 3.0.13-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-30588 | MEDIUM5.3 | node 16.19.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-21711 | MEDIUM5.3 | node 16.19.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-21714 | MEDIUM5.3 | node 16.19.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-32006 | MEDIUM5.28 | node 16.19.1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-1255 | MEDIUM5.02 | libcrypto3 3.0.8-r0 fixed in 3.0.8-r4 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-1255 | MEDIUM5.02 | libssl3 3.0.8-r0 fixed in 3.0.8-r4 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | libcrypto3 3.0.8-r0 fixed in 3.0.12-r5 | 52.4% Actively Exploited | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | libssl3 3.0.8-r0 fixed in 3.0.12-r5 | 52.4% Actively Exploited | Directly Exposed |
| CVE-2025-68160 | MEDIUM4.7 | libcrypto3 3.0.8-r0 fixed in 3.0.19-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4.7 | libssl3 3.0.8-r0 fixed in 3.0.19-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM4.5 | libcrypto3 3.0.8-r0 fixed in 3.0.19-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM4.5 | libssl3 3.0.8-r0 fixed in 3.0.19-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-33750 | MEDIUM4.5 | brace-expansion 1.1.11 fixed in 5.0.5, 3.0.2, 2.0.3, 1.1.13 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33750 | MEDIUM4.5 | brace-expansion 2.0.1 fixed in 5.0.5, 3.0.2, 2.0.3, 1.1.13 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-2975 | MEDIUM4.5 | libcrypto3 3.0.8-r0 fixed in 3.0.9-r2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-2975 | MEDIUM4.5 | libssl3 3.0.8-r0 fixed in 3.0.9-r2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-32559 | MEDIUM4.5 | node 16.19.1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-30581 | MEDIUM4.5 | node 16.19.1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-30585 | MEDIUM4.5 | node 16.19.1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-30590 | MEDIUM4.5 | node 16.19.1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-69419 | MEDIUM4.44 | libcrypto3 3.0.8-r0 fixed in 3.0.19-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM4.44 | libssl3 3.0.8-r0 fixed in 3.0.19-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-13149 | MEDIUM4.24 | brace-expansion 1.1.11 fixed in 5.0.7, 1.1.16, 2.1.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102277 | MEDIUM4.24 | brace-expansion 1.1.11 fixed in 5.0.12, 3.0.9, 2.1.7, 1.1.21 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-13149 | MEDIUM4.24 | brace-expansion 2.0.1 fixed in 5.0.7, 1.1.16, 2.1.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102277 | MEDIUM4.24 | brace-expansion 2.0.1 fixed in 5.0.12, 3.0.9, 2.1.7, 1.1.21 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2024-13176 | MEDIUM4 | libcrypto3 3.0.8-r0 fixed in 3.0.19-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | libssl3 3.0.8-r0 fixed in 3.0.19-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | MEDIUM4 | libcrypto3 3.0.8-r0 fixed in 3.0.19-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | MEDIUM4 | libssl3 3.0.8-r0 fixed in 3.0.19-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-6129 | LOW3.9 | libcrypto3 3.0.8-r0 fixed in 3.0.12-r2 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6129 | LOW3.9 | libssl3 3.0.8-r0 fixed in 3.0.12-r2 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-29786 | LOW3.78 | tar 6.1.11 fixed in 7.5.10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-9143 | LOW3.7 | libcrypto3 3.0.8-r0 fixed in 3.0.15-r1 | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-9143 | LOW3.7 | libssl3 3.0.8-r0 fixed in 3.0.15-r1 | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-23745 | LOW3.66 | tar 6.1.11 fixed in 7.5.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-104844 | LOW3.54 | postcss-selector-parser 6.0.10 fixed in 7.1.6, 6.1.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31802 | LOW3.3 | tar 6.1.11 fixed in 7.5.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53655 | LOW3.3 | tar 6.1.11 fixed in 7.5.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3449 | LOW3.3 | @tootallnate/once 2.0.0 fixed in 3.0.1, 2.0.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-21715 | LOW3.3 | node 16.19.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-21716 | LOW3.3 | node 16.19.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-9232 | LOW3.1 | libcrypto3 3.0.8-r0 fixed in 3.0.19-r0 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9232 | LOW3.1 | libssl3 3.0.8-r0 fixed in 3.0.19-r0 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-24842 | LOW2.95 | tar 6.1.11 fixed in 7.5.7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-42363 | LOW2.8 | busybox 1.35.0-r29 fixed in 1.35.0-r31 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42364 | LOW2.8 | busybox 1.35.0-r29 fixed in 1.35.0-r31 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42365 | LOW2.8 | busybox 1.35.0-r29 fixed in 1.35.0-r31 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42366 | LOW2.8 | busybox 1.35.0-r29 fixed in 1.35.0-r30 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42363 | LOW2.8 | busybox-binsh 1.35.0-r29 fixed in 1.35.0-r31 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42364 | LOW2.8 | busybox-binsh 1.35.0-r29 fixed in 1.35.0-r31 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42365 | LOW2.8 | busybox-binsh 1.35.0-r29 fixed in 1.35.0-r31 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42366 | LOW2.8 | busybox-binsh 1.35.0-r29 fixed in 1.35.0-r30 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42363 | LOW2.8 | ssl_client 1.35.0-r29 fixed in 1.35.0-r31 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42364 | LOW2.8 | ssl_client 1.35.0-r29 fixed in 1.35.0-r31 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42365 | LOW2.8 | ssl_client 1.35.0-r29 fixed in 1.35.0-r31 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42366 | LOW2.8 | ssl_client 1.35.0-r29 fixed in 1.35.0-r30 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9496 | LOW2.7 | pacote 13.6.2 fixed in 21.5.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59873 | LOW2.7 | tar 6.1.11 fixed in 7.5.19 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-59874 | LOW2.7 | tar 6.1.11 fixed in 7.5.18 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-73566 | LOW2.7 | tar 6.1.11 fixed in 7.5.21 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-59871 | LOW2.7 | tar 6.1.11 fixed in 7.5.18 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-26960 | LOW2.56 | tar 6.1.11 fixed in 7.5.8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-23950 | LOW2.12 | tar 6.1.11 fixed in 7.5.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5889 | LOW2.1 | brace-expansion 1.1.11 fixed in 2.0.2, 1.1.12, 3.0.1, 4.0.1 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-5889 | LOW2.1 | brace-expansion 2.0.1 fixed in 2.0.2, 1.1.12, 3.0.1, 4.0.1 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2024-28863 | LOW1.99 | tar 6.1.11 fixed in 6.2.1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-59875 | LOW1.91 | tar 6.1.11 fixed in 7.5.17 | 0.4% Theoretical Threat | Post-Exploit |
Want to check another image? Run a full scan with the Docker Security Scanner.