Last scanned:
This base/runtime image is a clean foundation for building production images. The provided stats show 1 exposed-surface entry and 6 post-exploit-only entries, but none are at severity 6.0 or higher; the exposed max severity is 0.0 and the post-exploit max severity is 2.96. Because the threat score is 0, these findings do not change the SAFE verdict for images built on this base. No CVE details were supplied in the top findings, so there are no specific CVE IDs to remediate from this input. 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-6357 | LOW2.96 | pip 25.0.1 fixed in 26.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8643 | LOW2.8 | pip 25.0.1 fixed in 26.1.2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8869 | LOW2.7 | pip 25.0.1 fixed in 25.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3219 | LOW2.55 | pip 25.0.1 fixed in 26.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13346 | LOW1.99 | pip 25.0.1 fixed in 26.2.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1703 | LOW1.99 | pip 25.0.1 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.