Last scanned:
AI verdict failed due to an error.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-8286 | MEDIUM4.13 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8925 | MEDIUM4.13 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11352 | LOW3.82 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11586 | LOW3.82 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% 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-9079 | LOW3.82 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9546 | LOW3.82 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-11564 | LOW3.31 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | 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-8926 | LOW2.45 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | NONE0 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8925 | NONE0 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-39822 | NONE0 | stdlib v1.25.11 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-33630 | NONE0 | c-ares 1.34.6-r0 fixed in 1.34.8-r0 | — | Not Applicable |
| CVE-2026-11352 | NONE0 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-11586 | NONE0 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12064 | NONE0 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8927 | NONE0 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8932 | NONE0 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9079 | NONE0 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-9545 | NONE0 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-9546 | NONE0 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-50274 | NONE0 | github.com/DataDog/dd-trace-go/v2 v2.7.1 fixed in 2.8.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9547 | NONE0 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-9080 | NONE0 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56132 | NONE0 | libexpat 2.8.1-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56403 | NONE0 | libexpat 2.8.1-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56404 | NONE0 | libexpat 2.8.1-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56405 | NONE0 | libexpat 2.8.1-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56406 | NONE0 | libexpat 2.8.1-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56407 | NONE0 | libexpat 2.8.1-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56410 | NONE0 | libexpat 2.8.1-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56411 | NONE0 | libexpat 2.8.1-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-11564 | NONE0 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-11856 | NONE0 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8924 | NONE0 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-50219 | NONE0 | libexpat 2.8.1-r0 fixed in 2.8.2-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56412 | NONE0 | libexpat 2.8.1-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.25.11 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8926 | NONE0 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-10536 | NONE0 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56131 | NONE0 | libexpat 2.8.1-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56408 | NONE0 | libexpat 2.8.1-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56409 | NONE0 | libexpat 2.8.1-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Not Applicable |
| GO-2026-5932 | NONE0 | golang.org/x/crypto v0.53.0 No fix yet | — | Not Applicable |
| CVE-2026-56852 | NONE0 | golang.org/x/text v0.38.0 fixed in 0.39.0 | 0.4% Theoretical Threat | Not Applicable |
| GHSA-hrxh-6v49-42gf | NONE0 | google.golang.org/grpc v1.81.1 fixed in 1.82.1 | — | 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.