Last scanned:
This base/runtime image is a clean foundation for building production images. It is an official Docker image pinned by digest and has a threat score of 0. The stats show exposed_total 5 and post_total 16, but the maximum severities are low at 4.0 and 2.26, and no exposed or post-exploit findings are listed with CVE IDs. These inherited items do not change the SAFE verdict for images built on top of this base. 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-54875 | MEDIUM4 | libcrypto3 3.3.7-r1 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54875 | MEDIUM4 | libssl3 3.3.7-r1 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.15 | libcrypto3 3.3.7-r1 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.15 | libssl3 3.3.7-r1 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | LOW2.26 | libcrypto3 3.3.7-r1 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-84782 | LOW2.26 | libssl3 3.3.7-r1 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-54872 | LOW1.81 | libcrypto3 3.3.7-r1 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-72897 | LOW1.81 | libcrypto3 3.3.7-r1 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-75805 | LOW1.81 | libcrypto3 3.3.7-r1 fixed in 3.3.7-r2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-77696 | LOW1.81 | libcrypto3 3.3.7-r1 fixed in 3.3.7-r2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-54872 | LOW1.81 | libssl3 3.3.7-r1 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-72897 | LOW1.81 | libssl3 3.3.7-r1 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-75805 | LOW1.81 | libssl3 3.3.7-r1 fixed in 3.3.7-r2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-77696 | LOW1.81 | libssl3 3.3.7-r1 fixed in 3.3.7-r2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-75804 | LOW1.62 | libcrypto3 3.3.7-r1 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-75806 | LOW1.62 | libcrypto3 3.3.7-r1 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-84784 | LOW1.62 | libcrypto3 3.3.7-r1 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-75804 | LOW1.62 | libssl3 3.3.7-r1 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-75806 | LOW1.62 | libssl3 3.3.7-r1 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-84784 | LOW1.62 | libssl3 3.3.7-r1 fixed in 3.3.7-r2 | 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.