Last scanned:
This image is acceptable for production, but remediating the identified vulnerabilities is recommended to reduce the attack surface. The highest-severity exposed issue is CVE-2026-33630 in the c-ares DNS resolver, which a malicious DNS server could trigger to crash name resolution. Although the image contains many tracked vulnerabilities (108 exposed, 41 post-exploit), none reach high severity, and post-exploit impact is limited. Updating c-ares to a patched version would fully address CVE-2026-33630 and eliminate the associated denial-of-service risk.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-33630 | MEDIUM6 | c-ares 1.34.6-r0 fixed in 1.34.8-r0 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56132 | MEDIUM5.87 | libexpat 2.8.1-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | libexpat 2.8.1-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM5.87 | libexpat 2.8.1-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM5.87 | libexpat 2.8.1-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | libexpat 2.8.1-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56407 | MEDIUM5.87 | libexpat 2.8.1-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56410 | MEDIUM5.87 | libexpat 2.8.1-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56411 | MEDIUM5.87 | libexpat 2.8.1-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53466 | MEDIUM5.52 | imagemagick 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53466 | MEDIUM5.52 | imagemagick-jp2 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53466 | MEDIUM5.52 | imagemagick-jpeg 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53466 | MEDIUM5.52 | imagemagick-libs 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | imagemagick-pdf 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53466 | MEDIUM5.52 | imagemagick-pdf 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | imagemagick-tiff 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53466 | MEDIUM5.52 | imagemagick-tiff 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | imagemagick-webp 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53466 | MEDIUM5.52 | imagemagick-webp 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53465 | MEDIUM5.27 | imagemagick 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53465 | MEDIUM5.27 | imagemagick-jp2 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53465 | MEDIUM5.27 | imagemagick-jpeg 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53465 | MEDIUM5.27 | imagemagick-libs 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53465 | MEDIUM5.27 | imagemagick-pdf 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53465 | MEDIUM5.27 | imagemagick-tiff 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53465 | MEDIUM5.27 | imagemagick-webp 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55628 | MEDIUM5.18 | imagemagick 7.1.2.24-r0 fixed in 7.1.2.27-r0 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55628 | MEDIUM5.18 | imagemagick-jp2 7.1.2.24-r0 fixed in 7.1.2.27-r0 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55628 | MEDIUM5.18 | imagemagick-jpeg 7.1.2.24-r0 fixed in 7.1.2.27-r0 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55628 | MEDIUM5.18 | imagemagick-libs 7.1.2.24-r0 fixed in 7.1.2.27-r0 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55628 | MEDIUM5.18 | imagemagick-pdf 7.1.2.24-r0 fixed in 7.1.2.27-r0 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55628 | MEDIUM5.18 | imagemagick-tiff 7.1.2.24-r0 fixed in 7.1.2.27-r0 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55628 | MEDIUM5.18 | imagemagick-webp 7.1.2.24-r0 fixed in 7.1.2.27-r0 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM5.1 | imagemagick 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53461 | MEDIUM5.1 | imagemagick 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53460 | MEDIUM5.1 | imagemagick-jp2 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53461 | MEDIUM5.1 | imagemagick-jp2 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53460 | MEDIUM5.1 | imagemagick-jpeg 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53461 | MEDIUM5.1 | imagemagick-jpeg 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53460 | MEDIUM5.1 | imagemagick-libs 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53461 | MEDIUM5.1 | imagemagick-libs 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53460 | MEDIUM5.1 | imagemagick-pdf 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53461 | MEDIUM5.1 | imagemagick-pdf 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53460 | MEDIUM5.1 | imagemagick-tiff 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53461 | MEDIUM5.1 | imagemagick-tiff 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53460 | MEDIUM5.1 | imagemagick-webp 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53461 | MEDIUM5.1 | imagemagick-webp 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-55577 | MEDIUM5.02 | imagemagick 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55577 | MEDIUM5.02 | imagemagick-jp2 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55577 | MEDIUM5.02 | imagemagick-jpeg 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55577 | MEDIUM5.02 | imagemagick-libs 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55577 | MEDIUM5.02 | imagemagick-pdf 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55577 | MEDIUM5.02 | imagemagick-tiff 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55577 | MEDIUM5.02 | imagemagick-webp 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | libexpat 2.8.1-r0 fixed in 2.8.2-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | MEDIUM5.02 | libexpat 2.8.1-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55510 | MEDIUM4.67 | imagemagick 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55597 | MEDIUM4.67 | imagemagick 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55510 | MEDIUM4.67 | imagemagick-jp2 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55597 | MEDIUM4.67 | imagemagick-jp2 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55510 | MEDIUM4.67 | imagemagick-jpeg 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55597 | MEDIUM4.67 | imagemagick-jpeg 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55510 | MEDIUM4.67 | imagemagick-libs 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55597 | MEDIUM4.67 | imagemagick-libs 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55510 | MEDIUM4.67 | imagemagick-pdf 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55597 | MEDIUM4.67 | imagemagick-pdf 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55510 | MEDIUM4.67 | imagemagick-tiff 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55597 | MEDIUM4.67 | imagemagick-tiff 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55510 | MEDIUM4.67 | imagemagick-webp 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55597 | MEDIUM4.67 | imagemagick-webp 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53467 | MEDIUM4.5 | imagemagick 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55594 | MEDIUM4.5 | imagemagick 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53467 | MEDIUM4.5 | imagemagick-jp2 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55594 | MEDIUM4.5 | imagemagick-jp2 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53467 | MEDIUM4.5 | imagemagick-jpeg 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55594 | MEDIUM4.5 | imagemagick-jpeg 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53467 | MEDIUM4.5 | imagemagick-libs 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55594 | MEDIUM4.5 | imagemagick-libs 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53467 | MEDIUM4.5 | imagemagick-pdf 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55594 | MEDIUM4.5 | imagemagick-pdf 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53467 | MEDIUM4.5 | imagemagick-tiff 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55594 | MEDIUM4.5 | imagemagick-tiff 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53467 | MEDIUM4.5 | imagemagick-webp 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55594 | MEDIUM4.5 | imagemagick-webp 7.1.2.24-r0 fixed in 7.1.2.27-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55595 | MEDIUM4 | imagemagick 7.1.2.24-r0 fixed in 7.1.2.27-r0 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55595 | MEDIUM4 | imagemagick-jp2 7.1.2.24-r0 fixed in 7.1.2.27-r0 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55595 | MEDIUM4 | imagemagick-jpeg 7.1.2.24-r0 fixed in 7.1.2.27-r0 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55595 | MEDIUM4 | imagemagick-libs 7.1.2.24-r0 fixed in 7.1.2.27-r0 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55595 | MEDIUM4 | imagemagick-pdf 7.1.2.24-r0 fixed in 7.1.2.27-r0 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55595 | MEDIUM4 | imagemagick-tiff 7.1.2.24-r0 fixed in 7.1.2.27-r0 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55595 | MEDIUM4 | imagemagick-webp 7.1.2.24-r0 fixed in 7.1.2.27-r0 | <0.1% Theoretical Threat | Directly Exposed |
| 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-8927 | LOW3.82 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% 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-9079 | LOW3.82 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9546 | LOW3.82 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-56131 | LOW3.82 | libexpat 2.8.1-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW3.77 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl 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-9080 | LOW3.72 | libcurl 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-11564 | LOW3.31 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | 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-53462 | LOW3.15 | imagemagick 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53462 | LOW3.15 | imagemagick-jp2 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53462 | LOW3.15 | imagemagick-jpeg 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53462 | LOW3.15 | imagemagick-libs 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53462 | LOW3.15 | imagemagick-pdf 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53462 | LOW3.15 | imagemagick-tiff 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53462 | LOW3.15 | imagemagick-webp 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53464 | LOW2.8 | imagemagick 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53464 | LOW2.8 | imagemagick-jp2 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53464 | LOW2.8 | imagemagick-jpeg 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53464 | LOW2.8 | imagemagick-libs 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53464 | LOW2.8 | imagemagick-pdf 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53464 | LOW2.8 | imagemagick-tiff 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53464 | LOW2.8 | imagemagick-webp 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-2100 | LOW2.7 | p11-kit 0.25.5-r2 fixed in 0.26.2-r0 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8286 | LOW2.48 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8925 | LOW2.48 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | LOW2.48 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8925 | LOW2.48 | libcurl 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-8926 | LOW2.45 | libcurl 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-10536 | LOW2.4 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-11352 | LOW2.29 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11586 | LOW2.29 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW2.29 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-11352 | LOW2.29 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11586 | LOW2.29 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW2.29 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53463 | LOW1.99 | imagemagick 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53463 | LOW1.99 | imagemagick-jp2 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53463 | LOW1.99 | imagemagick-jpeg 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53463 | LOW1.99 | imagemagick-libs 7.1.2.24-r0 fixed in 7.1.2.25-r0 | 0.2% Theoretical Threat | Post-Exploit |
| 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-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 |
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.