Last scanned:
This base/runtime image is a clean foundation for building production images. While the scan shows 13 exposed and 20 post-exploit related findings, all have low severity (maximum CVSS score of 5.77) and none are relevant to the official trusted Docker image. There are no practical risks inherited by images built on this base, and no CVE IDs require remediation. Proceed with using this image as a foundation, but continue to monitor upstream security updates. 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-2023-0286 | MEDIUM5.77 | libcrypto1.1 1.1.1q-r0 fixed in 1.1.1t-r0 | 59.5% Actively Exploited | Directly Exposed |
| CVE-2023-0286 | MEDIUM5.77 | libssl1.1 1.1.1q-r0 fixed in 1.1.1t-r0 | 59.5% Actively Exploited | Directly Exposed |
| CVE-2022-4304 | MEDIUM5.43 | libcrypto1.1 1.1.1q-r0 fixed in 1.1.1t-r0 | 16.2% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-4304 | MEDIUM5.43 | libssl1.1 1.1.1q-r0 fixed in 1.1.1t-r0 | 16.2% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-5678 | MEDIUM5.3 | libcrypto1.1 1.1.1q-r0 fixed in 1.1.1w-r1 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | libssl1.1 1.1.1q-r0 fixed in 1.1.1w-r1 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2650 | MEDIUM5.07 | libcrypto1.1 1.1.1q-r0 fixed in 1.1.1u-r0 | 75.1% Actively Exploited | Directly Exposed |
| CVE-2023-2650 | MEDIUM5.07 | libssl1.1 1.1.1q-r0 fixed in 1.1.1u-r0 | 75.1% Actively Exploited | Directly Exposed |
| CVE-2022-43680 | MEDIUM4.5 | expat 2.4.9-r0 fixed in 2.5.0-r0 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0464 | MEDIUM4.5 | libcrypto1.1 1.1.1q-r0 fixed in 1.1.1t-r2 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0464 | MEDIUM4.5 | libssl1.1 1.1.1q-r0 fixed in 1.1.1t-r2 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0465 | LOW3.18 | libcrypto1.1 1.1.1q-r0 fixed in 1.1.1t-r2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0465 | LOW3.18 | libssl1.1 1.1.1q-r0 fixed in 1.1.1t-r2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | LOW3.17 | krb5-libs 1.19.3-r0 fixed in 1.19.4-r0 | 6.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6345 | LOW3.17 | setuptools 65.5.0 fixed in 70.0.0 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-47273 | LOW3.17 | setuptools 65.5.0 fixed in 78.1.1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-59890 | LOW3.11 | setuptools 65.5.0 fixed in 83.0.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-4450 | LOW3.1 | libcrypto1.1 1.1.1q-r0 fixed in 1.1.1t-r0 | 20.4% High Exploitation Risk | Post-Exploit |
| CVE-2022-4450 | LOW3.1 | libssl1.1 1.1.1q-r0 fixed in 1.1.1t-r0 | 20.4% High Exploitation Risk | Post-Exploit |
| CVE-2026-6357 | LOW2.96 | pip 22.3 fixed in 26.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-1304 | LOW2.81 | libcom_err 1.46.4-r0 fixed in 1.46.6-r0 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8643 | LOW2.8 | pip 22.3 fixed in 26.1.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-0215 | LOW2.7 | libcrypto1.1 1.1.1q-r0 fixed in 1.1.1t-r0 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0215 | LOW2.7 | libssl1.1 1.1.1q-r0 fixed in 1.1.1t-r0 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-8869 | LOW2.7 | pip 22.3 fixed in 25.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3219 | LOW2.55 | pip 22.3 fixed in 26.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-40897 | LOW2.12 | setuptools 65.5.0 fixed in 65.5.1 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-1703 | LOW1.99 | pip 22.3 fixed in 26.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-3446 | LOW1.91 | libcrypto1.1 1.1.1q-r0 fixed in 1.1.1u-r2 | 6.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-3817 | LOW1.91 | libcrypto1.1 1.1.1q-r0 fixed in 1.1.1v-r0 | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-3446 | LOW1.91 | libssl1.1 1.1.1q-r0 fixed in 1.1.1u-r2 | 6.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-3817 | LOW1.91 | libssl1.1 1.1.1q-r0 fixed in 1.1.1v-r0 | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5752 | LOW1.68 | pip 22.3 fixed in 23.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-29491 | NONE0 | ncurses-libs 6.3_p20211120-r1 fixed in 6.3_p20211120-r2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-29491 | NONE0 | ncurses-terminfo-base 6.3_p20211120-r1 fixed in 6.3_p20211120-r2 | 0.9% 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.