Last scanned:
This base/runtime image is a clean foundation for building production images. It has no exposed vulnerabilities and the 37 post-exploit findings are all low severity (max 3.82), posing negligible risk in containerized deployments. The image is officially maintained and pinned by digest, ensuring consistency and trust. 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-11586 | LOW3.82 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9546 | LOW3.82 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-11586 | LOW3.82 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9546 | LOW3.82 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-33630 | LOW3.6 | c-ares 1.34.6-r0 fixed in 1.34.8-r0 | — | Post-ExploitContext importance: MEDIUM |
| CVE-2026-11564 | LOW3.31 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11564 | LOW3.31 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8925 | LOW2.92 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8925 | LOW2.92 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11352 | LOW2.7 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-9079 | LOW2.7 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11352 | LOW2.7 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-9079 | LOW2.7 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8286 | LOW2.48 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | LOW2.48 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW2.34 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11856 | LOW2.34 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8458 | NONE0 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.5% 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.