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-2025-26519 | NONE0 | musl 1.2.3-r3 fixed in 1.2.3-r4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-26519 | NONE0 | musl-utils 1.2.3-r3 fixed in 1.2.3-r4 | 0.3% 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 |
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.