Last scanned:
This base/runtime image is a clean foundation for building production images. It is an official Docker image pinned by digest, which supports supply-chain trust for images built on top of it. The provided stats do show 27 exposed-surface and 20 post-exploit-only findings, but none meet the 6.0 severity threshold, and the maximum severities are 5.35 and 2.92 respectively. No top CVE findings are listed in the inputs, so there is no specific inherited vulnerability requiring remediation before production use as a 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-42768 | MEDIUM5.35 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.02 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-72897 | MEDIUM5.02 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.02 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.02 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.02 | libssl3 3.3.7-r0 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-72897 | MEDIUM5.02 | libssl3 3.3.7-r0 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.02 | libssl3 3.3.7-r0 fixed in 3.3.7-r2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.02 | libssl3 3.3.7-r0 fixed in 3.3.7-r2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | MEDIUM4.5 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM4.5 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84784 | MEDIUM4.5 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | MEDIUM4.5 | libssl3 3.3.7-r0 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM4.5 | libssl3 3.3.7-r0 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84784 | MEDIUM4.5 | libssl3 3.3.7-r0 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54875 | MEDIUM4 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54875 | MEDIUM4 | libssl3 3.3.7-r0 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.15 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.15 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.15 | libssl3 3.3.7-r0 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.15 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45447 | LOW2.92 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-34183 | LOW2.7 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63076 | LOW2.7 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34183 | LOW2.7 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63076 | LOW2.7 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34182 | LOW2.66 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34182 | LOW2.66 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63072 | LOW2.29 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-63072 | LOW2.29 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-84782 | LOW2.26 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-84782 | LOW2.26 | libssl3 3.3.7-r0 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-63073 | LOW2.12 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63073 | LOW2.12 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42766 | LOW1.91 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42766 | LOW1.91 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42770 | LOW1.81 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW1.81 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 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.