Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. The main practical risk is remote denial of service: issues such as CVE-2026-63074 and CVE-2026-66046 could let an attacker exhaust memory or CPU and disrupt an internet-facing nginx service. CVE-2026-63074 only applies if a CMP server reuses a single context, and CVE-2026-66046 requires parsing untrusted XML, so these paths may not be reachable in a typical nginx deployment. If CMP and untrusted XML parsing are not enabled, those specific risks are fully mitigated; otherwise apply strict compensating controls before production use.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-63074 | MEDIUM6.38 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM6.38 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-66046 | MEDIUM6.38 | libexpat 2.8.2-r0 fixed in 2.8.4-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-76641 | MEDIUM6.38 | libexpat 2.8.2-r0 fixed in 2.8.4-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-76956 | MEDIUM6.38 | libexpat 2.8.2-r0 fixed in 2.8.4-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93990 | MEDIUM6.38 | libexpat 2.8.2-r0 fixed in 2.8.5-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63072 | MEDIUM6.38 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM6.38 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM6.38 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-89157 | MEDIUM6.29 | pcre2 10.47-r1 fixed in 10.48-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM6 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-14457 | MEDIUM6 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-18798 | MEDIUM6 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-14457 | MEDIUM6 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53612 | MEDIUM5.95 | libuuid 2.42.1-r0 fixed in 2.42.3-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libuuid 2.42.1-r0 fixed in 2.42.3-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53614 | MEDIUM5.95 | libuuid 2.42.1-r0 fixed in 2.42.3-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libuuid 2.42.1-r0 fixed in 2.42.3-r0 | 0.2% Theoretical Threat | Directly Exposed |
| 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-46675 | MEDIUM5.9 | libpng 1.6.58-r1 fixed in 1.6.59-r0 | — | 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-89158 | MEDIUM5.52 | pcre2 10.47-r1 fixed in 10.48-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89160 | MEDIUM5.52 | pcre2 10.47-r1 fixed in 10.48-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM5.1 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-14456 | MEDIUM5.1 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102633 | MEDIUM5.02 | libexpat 2.8.2-r0 fixed in 2.9.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-89156 | MEDIUM5.02 | pcre2 10.47-r1 fixed in 10.48-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58055 | MEDIUM4.59 | nghttp2-libs 1.69.0-r0 fixed in 1.70.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86145 | MEDIUM4.18 | pcre2 10.47-r1 fixed in 10.48-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid 2.42.1-r0 fixed in 2.42.3-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-89161 | LOW3.98 | pcre2 10.47-r1 fixed in 10.48-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-103111 | LOW3.88 | pcre2 10.47-r1 fixed in 10.49-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.15 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.15 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89162 | LOW2.8 | pcre2 10.47-r1 fixed in 10.48-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | LOW2.7 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63076 | LOW2.7 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-77214 | LOW2.51 | libexpat 2.8.2-r0 fixed in 2.9.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-82208 | LOW2.45 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-82208 | LOW2.45 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.42 | libuuid 2.42.1-r0 fixed in 2.42.3-r1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76957 | LOW2.39 | libexpat 2.8.2-r0 fixed in 2.8.4-r0 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.39 | libuuid 2.42.1-r0 fixed in 2.42.3-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.39 | libuuid 2.42.1-r0 fixed in 2.42.3-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4775 | LOW2.39 | tiff 4.7.1-r0 fixed in 4.7.2-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63072 | LOW2.29 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-54874 | LOW2.29 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-54874 | LOW2.29 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW1.99 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW1.99 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-13608 | LOW1.89 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.89 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-80231 | LOW1.89 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-80255 | LOW1.89 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13608 | LOW1.89 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.89 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-80231 | LOW1.89 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-80255 | LOW1.89 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.58 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.58 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-88806 | NONE0 | libx11 1.8.13-r0 fixed in 1.8.14-r0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-94283 | NONE0 | libx11 1.8.13-r0 fixed in 1.8.14-r0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-94284 | NONE0 | libx11 1.8.13-r0 fixed in 1.8.14-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-94287 | NONE0 | libxpm 3.5.19-r0 fixed in 3.5.20-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-94285 | NONE0 | libx11 1.8.13-r0 fixed in 1.8.14-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80229 | NONE0 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80256 | NONE0 | curl 8.21.0-r0 fixed in 8.22.0-r0 | — | Not Applicable |
| CVE-2026-80229 | NONE0 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80256 | NONE0 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | — | Not Applicable |
| CVE-2026-85091 | NONE0 | zlib 1.3.2-r0 fixed in 1.3.2-r1 | 0.4% 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.