Last scanned:
This base/runtime image is a clean foundation for building production images. It does carry 2 exposed and 20 post-exploit findings, but their maximum severities are only 3.65 and 2.63, and none reach the 6.0 threshold that would materially affect images built on top of it. The image is an official Docker Hub image pinned by digest, which reduces supply-chain drift risk. Any residual risk should be handled in the final image you build on top, not by avoiding this base 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.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-9358 | LOW3.65 | postcss-selector-parser 7.1.1 fixed in 6.1.3, 7.1.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-69192 | LOW2.63 | ip-address 10.1.0 fixed in 10.3.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-102276 | LOW2.29 | brace-expansion 2.0.2 fixed in 5.0.10, 3.0.7, 2.1.5, 1.1.19 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13149 | LOW2.29 | brace-expansion 2.0.2 fixed in 5.0.7, 1.1.16, 2.1.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-14257 | LOW2.29 | brace-expansion 2.0.2 fixed in 5.0.8, 3.0.3, 2.1.3, 1.1.17 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-69152 | LOW2.29 | brace-expansion 2.0.2 fixed in 1.1.18, 2.1.4, 3.0.6, 5.0.9 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-33750 | LOW2.29 | brace-expansion 2.0.2 fixed in 5.0.5, 3.0.2, 2.0.3, 1.1.13 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-93748 | LOW2.29 | http-cache-semantics 4.2.0 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9496 | LOW2.29 | pacote 19.0.2 fixed in 21.5.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9496 | LOW2.29 | pacote 20.0.1 fixed in 21.5.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102278 | LOW1.99 | brace-expansion 2.0.2 fixed in 5.0.11, 3.0.8, 2.1.6, 1.1.20 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-33671 | LOW1.99 | picomatch 4.0.3 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42338 | LOW1.87 | ip-address 10.1.0 fixed in 10.1.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-104844 | LOW1.81 | postcss-selector-parser 7.1.1 fixed in 7.1.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48815 | LOW1.81 | sigstore 3.1.0 fixed in 4.1.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-48758 | LOW1.65 | @sigstore/core 2.0.0 fixed in 3.2.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102277 | LOW1.62 | brace-expansion 2.0.2 fixed in 5.0.12, 3.0.9, 2.1.7, 1.1.21 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-101911 | LOW1.62 | ip-address 10.1.0 fixed in 10.7.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-101912 | LOW1.62 | ip-address 10.1.0 fixed in 10.7.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-101913 | LOW1.62 | ip-address 10.1.0 fixed in 10.5.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-33672 | LOW1.62 | picomatch 4.0.3 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-85091 | NONE0 | zlib 1.3.2-r0 fixed in 1.3.2-r1 | 0.4% 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.