Last scanned:
AI verdict failed due to an error.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2023-42366 | LOW2.8 | busybox 1.35.0-r17 fixed in 1.35.0-r18 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-2603 | NONE0 | libcap 2.64-r0 fixed in 2.64-r1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-29491 | NONE0 | ncurses-libs 6.3_p20220521-r0 fixed in 6.3_p20220521-r1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-29491 | NONE0 | ncurses-terminfo-base 6.3_p20220521-r0 fixed in 6.3_p20220521-r1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-47038 | NONE0 | perl 5.34.1-r0 fixed in 5.34.2-r0 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-4450 | NONE0 | libcrypto1.1 1.1.1s-r0 fixed in 1.1.1t-r0 | 20.4% High Exploitation Risk | Not Applicable |
| CVE-2023-0215 | NONE0 | libcrypto1.1 1.1.1s-r0 fixed in 1.1.1t-r0 | 4.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-0464 | NONE0 | libcrypto1.1 1.1.1s-r0 fixed in 1.1.1t-r1 | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-4450 | NONE0 | libssl1.1 1.1.1s-r0 fixed in 1.1.1t-r0 | 20.4% High Exploitation Risk | Not Applicable |
| CVE-2023-0215 | NONE0 | libssl1.1 1.1.1s-r0 fixed in 1.1.1t-r0 | 4.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-0464 | NONE0 | libssl1.1 1.1.1s-r0 fixed in 1.1.1t-r1 | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-0286 | NONE0 | libcrypto1.1 1.1.1s-r0 fixed in 1.1.1t-r0 | 59.5% Actively Exploited | Not Applicable |
| CVE-2023-0286 | NONE0 | libssl1.1 1.1.1s-r0 fixed in 1.1.1t-r0 | 59.5% Actively Exploited | Not Applicable |
| CVE-2025-26519 | NONE0 | musl 1.2.3-r1 fixed in 1.2.3-r4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-26519 | NONE0 | musl-utils 1.2.3-r1 fixed in 1.2.3-r4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-2650 | NONE0 | libcrypto1.1 1.1.1s-r0 fixed in 1.1.1u-r0 | 75.1% Actively Exploited | Not Applicable |
| CVE-2023-2650 | NONE0 | libssl1.1 1.1.1s-r0 fixed in 1.1.1u-r0 | 75.1% Actively Exploited | Not Applicable |
| CVE-2022-4304 | NONE0 | libcrypto1.1 1.1.1s-r0 fixed in 1.1.1t-r0 | 16.2% High Exploitation Risk | Not Applicable |
| CVE-2022-4304 | NONE0 | libssl1.1 1.1.1s-r0 fixed in 1.1.1t-r0 | 16.2% High Exploitation Risk | Not Applicable |
| CVE-2023-24056 | NONE0 | pkgconf 1.8.0-r1 fixed in 1.8.1-r0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-42366 | NONE0 | ssl_client 1.35.0-r17 fixed in 1.35.0-r18 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-0465 | NONE0 | libcrypto1.1 1.1.1s-r0 fixed in 1.1.1t-r2 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-3446 | NONE0 | libcrypto1.1 1.1.1s-r0 fixed in 1.1.1u-r2 | 6.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-3817 | NONE0 | libcrypto1.1 1.1.1s-r0 fixed in 1.1.1v-r0 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-5678 | NONE0 | libcrypto1.1 1.1.1s-r0 fixed in 1.1.1w-r1 | 4.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-0465 | NONE0 | libssl1.1 1.1.1s-r0 fixed in 1.1.1t-r2 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-3446 | NONE0 | libssl1.1 1.1.1s-r0 fixed in 1.1.1u-r2 | 6.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-3817 | NONE0 | libssl1.1 1.1.1s-r0 fixed in 1.1.1v-r0 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-5678 | NONE0 | libssl1.1 1.1.1s-r0 fixed in 1.1.1w-r1 | 4.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-2602 | NONE0 | libcap 2.64-r0 fixed in 2.64-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.
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.