Last scanned:
This image is safe for production use. It does contain 32 exposure-related findings and 136 post-exploit-only findings, but the highest exposed severity is 5.9 and none reach 6.0 or are known to be actively exploited. These findings are low severity in this context and do not change the verdict. The image comes from a verified publisher and is pinned by digest, which supports consistent, trusted deployments. Keep the image updated as new releases become available.
Already in good shape · 3 hardening steps left
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-63073 | MEDIUM5.9 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-111497 | MEDIUM5.59 | brotli-libs 1.2.0-r0 fixed in 1.2.1-r0 | 36.0% High Exploitation Risk | Directly Exposed |
| CVE-2026-85091 | MEDIUM5 | zlib 1.3.2-r0 fixed in 1.3.2-r1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86145 | MEDIUM4.92 | pcre2 10.47-r0 fixed in 10.48-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-60005 | MEDIUM4.92 | nginx 1.31.2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-103111 | MEDIUM4.56 | pcre2 10.47-r0 fixed in 10.49-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-89157 | MEDIUM4.44 | pcre2 10.47-r0 fixed in 10.48-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107891 | MEDIUM4 | musl 1.2.5-r23 fixed in 1.2.5-r24 | — | Directly Exposed |
| CVE-2026-107891 | MEDIUM4 | musl-utils 1.2.5-r23 fixed in 1.2.5-r24 | — | Directly Exposed |
| CVE-2026-89158 | LOW3.9 | pcre2 10.47-r0 fixed in 10.48-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89160 | LOW3.9 | pcre2 10.47-r0 fixed in 10.48-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-89156 | LOW3.54 | pcre2 10.47-r0 fixed in 10.48-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-77214 | LOW2.95 | libexpat 2.8.2-r0 fixed in 2.9.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | LOW2.92 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.92 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8925 | LOW2.92 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-92392 | LOW2.92 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8286 | LOW2.92 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.92 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8925 | LOW2.92 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-92392 | LOW2.92 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | libuuid 2.41.4-r0 fixed in 2.41.6-r1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76957 | LOW2.81 | libexpat 2.8.2-r0 fixed in 2.8.4-r0 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | libuuid 2.41.4-r0 fixed in 2.41.6-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | libuuid 2.41.4-r0 fixed in 2.41.6-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-89161 | LOW2.81 | pcre2 10.47-r0 fixed in 10.48-r0 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4775 | LOW2.81 | tiff 4.7.1-r0 fixed in 4.7.2-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11352 | LOW2.7 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11586 | LOW2.7 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW2.7 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW2.7 | curl 8.19.0-r0 fixed in 8.20.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW2.7 | curl 8.19.0-r0 fixed in 8.20.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW2.7 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW2.7 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9079 | LOW2.7 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-9545 | LOW2.7 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9546 | LOW2.7 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-11352 | LOW2.7 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11586 | LOW2.7 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW2.7 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW2.7 | libcurl 8.19.0-r0 fixed in 8.20.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW2.7 | libcurl 8.19.0-r0 fixed in 8.20.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW2.7 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW2.7 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9079 | LOW2.7 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-9545 | LOW2.7 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9546 | LOW2.7 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-66046 | LOW2.7 | libexpat 2.8.2-r0 fixed in 2.8.4-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-76641 | LOW2.7 | libexpat 2.8.2-r0 fixed in 2.8.4-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-76956 | LOW2.7 | libexpat 2.8.2-r0 fixed in 2.8.4-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-93990 | LOW2.7 | libexpat 2.8.2-r0 fixed in 2.8.5-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW2.66 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW2.66 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW2.63 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW2.63 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53612 | LOW2.52 | libuuid 2.41.4-r0 fixed in 2.41.6-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | libuuid 2.41.4-r0 fixed in 2.41.6-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53614 | LOW2.52 | libuuid 2.41.4-r0 fixed in 2.41.6-r0 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86410 | LOW2.45 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86410 | LOW2.45 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-11564 | LOW2.34 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW2.34 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW2.34 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5545 | LOW2.34 | curl 8.19.0-r0 fixed in 8.20.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW2.34 | curl 8.19.0-r0 fixed in 8.20.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW2.34 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-92388 | LOW2.34 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86414 | LOW2.34 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92390 | LOW2.34 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-11564 | LOW2.34 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW2.34 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW2.34 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5545 | LOW2.34 | libcurl 8.19.0-r0 fixed in 8.20.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW2.34 | libcurl 8.19.0-r0 fixed in 8.20.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW2.34 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-92388 | LOW2.34 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86414 | LOW2.34 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92390 | LOW2.34 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86411 | LOW2.12 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86411 | LOW2.12 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-102633 | LOW2.12 | libexpat 2.8.2-r0 fixed in 2.9.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46675 | LOW2.12 | libpng 1.6.58-r1 fixed in 1.6.59-r0 | — | Post-Exploit |
| CVE-2026-89162 | LOW1.98 | pcre2 10.47-r0 fixed in 10.48-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4873 | LOW1.91 | curl 8.19.0-r0 fixed in 8.20.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW1.91 | curl 8.19.0-r0 fixed in 8.20.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7009 | LOW1.91 | curl 8.19.0-r0 fixed in 8.20.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW1.91 | curl 8.19.0-r0 fixed in 8.20.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-86409 | LOW1.91 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-86412 | LOW1.91 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86413 | LOW1.91 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW1.91 | libcurl 8.19.0-r0 fixed in 8.20.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW1.91 | libcurl 8.19.0-r0 fixed in 8.20.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7009 | LOW1.91 | libcurl 8.19.0-r0 fixed in 8.20.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW1.91 | libcurl 8.19.0-r0 fixed in 8.20.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-86409 | LOW1.91 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-86412 | LOW1.91 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86413 | LOW1.91 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-82208 | LOW1.73 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW1.73 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-107928 | LOW1.73 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-82208 | LOW1.73 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW1.73 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-107928 | LOW1.73 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW1.69 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW1.69 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-92386 | LOW1.55 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92386 | LOW1.55 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-80256 | LOW1.44 | curl 8.19.0-r0 fixed in 8.22.0-r0 | — | Post-Exploit |
| CVE-2026-80256 | LOW1.44 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | — | Post-Exploit |
| CVE-2026-107929 | LOW1.33 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13608 | LOW1.33 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.33 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80229 | LOW1.33 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.33 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-80231 | LOW1.33 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-80255 | LOW1.33 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-86415 | LOW1.33 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-87861 | LOW1.33 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-87862 | LOW1.33 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-87863 | LOW1.33 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-87864 | LOW1.33 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-87865 | LOW1.33 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-87866 | LOW1.33 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92387 | LOW1.33 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-92389 | LOW1.33 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92391 | LOW1.33 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-107929 | LOW1.33 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13608 | LOW1.33 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.33 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80229 | LOW1.33 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.33 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-80231 | LOW1.33 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-80255 | LOW1.33 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-86415 | LOW1.33 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-87861 | LOW1.33 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-87862 | LOW1.33 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-87863 | LOW1.33 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-87864 | LOW1.33 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-87865 | LOW1.33 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-87866 | LOW1.33 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92387 | LOW1.33 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-92389 | LOW1.33 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92391 | LOW1.33 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-94266 | LOW1.19 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-94266 | LOW1.19 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.12 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-94265 | LOW1.12 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.12 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-94265 | LOW1.12 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
Want to check another image? Run a full scan with the Docker Security Scanner.