Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. If an attacker could feed crafted Brotli-compressed data to a decoder in this container, they could corrupt memory and potentially run code inside the nginx worker, and the slice module flaw could expose small pieces of worker memory or disrupt a worker. Both issues depend on non-default configuration: CVE-2026-111497 needs a module or tool that decompresses Brotli input, and CVE-2026-60005 only applies if the slice directive is enabled. Confirm that neither feature is in use before deployment, and keep the image's nginx and Brotli packages under active patch monitoring.
Hardening plan for this image · 5 steps. The first closes an actively exploited CVE.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-111497 | HIGH8 | brotli-libs 1.2.0-r0 fixed in 1.2.1-r0 | 55.5% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2026-60005 | MEDIUM6.56 | nginx 1.30.3 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| 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-85091 | MEDIUM5 | zlib 1.3.2-r0 fixed in 1.3.2-r1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-77214 | MEDIUM4.92 | libexpat 2.8.2-r0 fixed in 2.9.0-r0 | 0.3% 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-78408 | MEDIUM4.74 | libuuid 2.41.4-r0 fixed in 2.41.6-r1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76957 | MEDIUM4.68 | libexpat 2.8.2-r0 fixed in 2.8.4-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libuuid 2.41.4-r0 fixed in 2.41.6-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libuuid 2.41.4-r0 fixed in 2.41.6-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89161 | MEDIUM4.68 | pcre2 10.47-r0 fixed in 10.48-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4775 | MEDIUM4.68 | tiff 4.7.1-r0 fixed in 4.7.2-r0 | 0.6% 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-8932 | MEDIUM4.5 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9079 | MEDIUM4.5 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9545 | MEDIUM4.5 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9546 | MEDIUM4.5 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.7% 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-8932 | MEDIUM4.5 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9079 | MEDIUM4.5 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9545 | MEDIUM4.5 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9546 | MEDIUM4.5 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-66046 | MEDIUM4.5 | libexpat 2.8.2-r0 fixed in 2.8.4-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-76641 | MEDIUM4.5 | libexpat 2.8.2-r0 fixed in 2.8.4-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-76956 | MEDIUM4.5 | libexpat 2.8.2-r0 fixed in 2.8.4-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93990 | MEDIUM4.5 | libexpat 2.8.2-r0 fixed in 2.8.5-r0 | 0.4% 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-9547 | MEDIUM4.44 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | MEDIUM4.44 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% 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-9080 | MEDIUM4.38 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9080 | MEDIUM4.38 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53612 | MEDIUM4.2 | libuuid 2.41.4-r0 fixed in 2.41.6-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libuuid 2.41.4-r0 fixed in 2.41.6-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53614 | MEDIUM4.2 | libuuid 2.41.4-r0 fixed in 2.41.6-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86410 | MEDIUM4.08 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86410 | MEDIUM4.08 | libcurl 8.19.0-r0 fixed in 8.23.0-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-11564 | LOW3.9 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11856 | LOW3.9 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-19931 | LOW3.9 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5545 | LOW3.9 | curl 8.19.0-r0 fixed in 8.20.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6429 | LOW3.9 | curl 8.19.0-r0 fixed in 8.20.0-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8924 | LOW3.9 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW3.9 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW3.9 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11564 | LOW3.9 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11856 | LOW3.9 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-19931 | LOW3.9 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5545 | LOW3.9 | libcurl 8.19.0-r0 fixed in 8.20.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6429 | LOW3.9 | libcurl 8.19.0-r0 fixed in 8.20.0-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8924 | LOW3.9 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW3.9 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW3.9 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | 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-86411 | LOW3.54 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86411 | LOW3.54 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102633 | LOW3.54 | libexpat 2.8.2-r0 fixed in 2.9.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46675 | LOW3.54 | libpng 1.6.58-r1 fixed in 1.6.59-r0 | — | Directly Exposed |
| CVE-2026-89156 | LOW3.54 | pcre2 10.47-r0 fixed in 10.48-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4873 | LOW3.18 | curl 8.19.0-r0 fixed in 8.20.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6253 | LOW3.18 | curl 8.19.0-r0 fixed in 8.20.0-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7009 | LOW3.18 | curl 8.19.0-r0 fixed in 8.20.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-7168 | LOW3.18 | curl 8.19.0-r0 fixed in 8.20.0-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86409 | LOW3.18 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86412 | LOW3.18 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86413 | LOW3.18 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4873 | LOW3.18 | libcurl 8.19.0-r0 fixed in 8.20.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6253 | LOW3.18 | libcurl 8.19.0-r0 fixed in 8.20.0-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7009 | LOW3.18 | libcurl 8.19.0-r0 fixed in 8.20.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-7168 | LOW3.18 | libcurl 8.19.0-r0 fixed in 8.20.0-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86409 | LOW3.18 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86412 | LOW3.18 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86413 | LOW3.18 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| 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-82208 | LOW2.88 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8926 | LOW2.88 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107928 | LOW2.88 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-82208 | LOW2.88 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8926 | LOW2.88 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107928 | LOW2.88 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-10536 | LOW2.82 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-10536 | LOW2.82 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Directly Exposed |
| 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-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-92386 | LOW2.58 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92386 | LOW2.58 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-80256 | LOW2.4 | curl 8.19.0-r0 fixed in 8.22.0-r0 | — | Directly Exposed |
| CVE-2026-80256 | LOW2.4 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | — | Directly Exposed |
| CVE-2026-107929 | LOW2.22 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13608 | LOW2.22 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80229 | LOW2.22 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80231 | LOW2.22 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-80255 | LOW2.22 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86415 | LOW2.22 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87861 | LOW2.22 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87862 | LOW2.22 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87863 | LOW2.22 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87865 | LOW2.22 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87866 | LOW2.22 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92387 | LOW2.22 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107929 | LOW2.22 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13608 | LOW2.22 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80229 | LOW2.22 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80231 | LOW2.22 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-80255 | LOW2.22 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86415 | LOW2.22 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87861 | LOW2.22 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87862 | LOW2.22 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87863 | LOW2.22 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87865 | LOW2.22 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87866 | LOW2.22 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92387 | LOW2.22 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-94266 | LOW1.98 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94266 | LOW1.98 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89162 | LOW1.98 | pcre2 10.47-r0 fixed in 10.48-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-82209 | LOW1.86 | curl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-94265 | LOW1.86 | curl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-82209 | LOW1.86 | libcurl 8.19.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-94265 | LOW1.86 | libcurl 8.19.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
Want to check another image? Run a full scan with the Docker Security Scanner.