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 who sends a crafted Brotli stream to an application running on this base could corrupt memory and possibly execute code, with root as the default user amplifying the impact. CVE-2026-111497 in the node package is the decisive issue, and it is reachable in normal operation without any special configuration. The undici denial-of-service findings, such as CVE-2026-109869, could crash a Node process when it talks to a malicious server, which is a secondary but real availability risk for images built on top. 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 26.5.1 No fix yet | 55.5% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2026-109869 | MEDIUM6 | undici 6.26.0 fixed in 6.29.1, 7.30.1, 8.12.2 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-12151 | MEDIUM6 | undici 6.26.0 fixed in 6.27.0, 7.28.0, 8.5.0 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-19534 | MEDIUM6 | undici 6.26.0 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109924 | MEDIUM6 | undici 6.26.0 fixed in 6.29.1, 7.30.1, 8.12.2 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-63073 | MEDIUM5.9 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-16728 | MEDIUM5.2 | undici 6.26.0 fixed in 6.28.0, 7.29.0, 8.9.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-16729 | MEDIUM5.2 | undici 6.26.0 fixed in 6.28.0, 7.29.0, 8.9.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-85091 | MEDIUM5 | zlib 1.3.2-r0 fixed in 1.3.2-r1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-85024 | MEDIUM4.72 | undici 6.26.0 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-9679 | MEDIUM4.72 | undici 6.26.0 fixed in 6.27.0, 7.28.0, 8.5.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-14456 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15157 | MEDIUM4.32 | undici 6.26.0 fixed in 6.28.0, 7.29.0, 8.9.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107891 | MEDIUM4 | musl 1.2.6-r2 fixed in 1.2.6-r3 | — | Directly Exposed |
| CVE-2026-107891 | MEDIUM4 | musl-utils 1.2.6-r2 fixed in 1.2.6-r3 | — | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-69192 | LOW3.1 | ip-address 10.2.0 fixed in 10.3.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-11525 | LOW2.96 | undici 6.26.0 fixed in 6.27.0, 7.28.0, 8.5.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-18540 | LOW2.96 | undici 6.26.0 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6733 | LOW2.96 | undici 6.26.0 fixed in 6.27.0, 7.28.0, 8.5.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102276 | LOW2.7 | brace-expansion 5.0.6 fixed in 5.0.10, 3.0.7, 2.1.5, 1.1.19 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-102278 | LOW2.7 | brace-expansion 5.0.6 fixed in 5.0.11, 3.0.8, 2.1.6, 1.1.20 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-14257 | LOW2.7 | brace-expansion 5.0.6 fixed in 5.0.8, 3.0.3, 2.1.3, 1.1.17 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-69152 | LOW2.7 | brace-expansion 5.0.6 fixed in 1.1.18, 2.1.4, 3.0.6, 5.0.9 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-93748 | LOW2.7 | http-cache-semantics 4.2.0 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-59873 | LOW2.7 | tar 7.5.16 fixed in 7.5.19 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-59874 | LOW2.7 | tar 7.5.16 fixed in 7.5.18 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-73566 | LOW2.7 | tar 7.5.16 fixed in 7.5.21 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-59871 | LOW2.7 | tar 7.5.16 fixed in 7.5.18 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-54272 | LOW2.59 | ip-address 10.2.0 fixed in 10.2.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-104844 | LOW2.12 | postcss-selector-parser 7.1.4 fixed in 7.1.6, 6.1.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13149 | LOW1.91 | brace-expansion 5.0.6 fixed in 5.0.7, 1.1.16, 2.1.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-102277 | LOW1.91 | brace-expansion 5.0.6 fixed in 5.0.12, 3.0.9, 2.1.7, 1.1.21 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-101910 | LOW1.91 | ip-address 10.2.0 fixed in 10.5.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-101911 | LOW1.91 | ip-address 10.2.0 fixed in 10.7.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-101912 | LOW1.91 | ip-address 10.2.0 fixed in 10.7.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-101913 | LOW1.91 | ip-address 10.2.0 fixed in 10.5.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-111997 | LOW1.91 | ip-address 10.2.0 fixed in 10.7.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-69198 | LOW1.91 | ip-address 10.2.0 fixed in 10.2.2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-59875 | LOW1.91 | tar 7.5.16 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.