Last scanned:
This base/runtime image is a clean foundation for building production images. It is an official Docker Hub image pinned by digest, which gives strong provenance for downstream builds. The vulnerability stats do show one exposed-surface item with max severity 0.0 and nine post-exploit-only items with max severity 3.11, but these are low-severity and below the thresholds that would change the verdict. No CVE IDs are listed in the provided top findings, and there are no configuration caveats or full mitigations to flag from those findings. Images built on top inherit this low-risk baseline; continue normal dependency scanning in the final image as part of standard build hygiene. 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-59890 | LOW3.11 | setuptools 79.0.1 fixed in 83.0.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6357 | LOW2.96 | pip 24.0 fixed in 26.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8643 | LOW2.8 | pip 24.0 fixed in 26.1.2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-24049 | LOW2.8 | wheel 0.45.1 fixed in 0.46.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-8869 | LOW2.7 | pip 24.0 fixed in 25.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-23949 | LOW2.63 | jaraco.context 5.3.0 fixed in 6.1.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3219 | LOW2.55 | pip 24.0 fixed in 26.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13346 | LOW1.99 | pip 24.0 fixed in 26.2.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1703 | LOW1.99 | pip 24.0 fixed in 26.0 | 0.4% 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.