Last scanned:
This base/runtime image carries significant vulnerabilities that any image built on it would inherit; remediate them in the final image before production. An attacker could exploit inherited libraries to cause denial of service or, in specific DTLS scenarios, disclose heap memory or crash a process, as seen with CVE-2026-66046 and CVE-2026-84782. Disabling DTLS in services that do not require it would fully eliminate CVE-2026-84782. Some remaining findings are limited by platform-specific conditions or local user-writable MIME paths. Note: this is a general-purpose base/runtime image — many findings live in components that an application built on top may never load, so actual exploitability depends on the final image. For an accurate risk picture, re-scan the final application image with context.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-66046 | MEDIUM6.38 | expat 2.5.0-6.el9_8.1 fixed in 2.5.0-6.el9_8.5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-93990 | MEDIUM6.38 | expat 2.5.0-6.el9_8.1 fixed in 2.5.0-6.el9_8.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63383 | MEDIUM6.38 | libevent 2.1.12-8.el9_4 fixed in 2.1.13-1.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63384 | MEDIUM6.38 | libevent 2.1.12-8.el9_4 fixed in 2.1.13-1.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | MEDIUM6.29 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-2.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-89157 | MEDIUM6.29 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86143 | MEDIUM6.21 | libxml2 2.9.13-14.el9_8.4 fixed in 2.9.13-14.el9_8.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | MEDIUM6.03 | glib2 2.68.4-19.el9_8.9 fixed in 2.68.4-19.el9_8.10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | expat 2.5.0-6.el9_8.1 fixed in 2.5.0-6.el9_8.3 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63381 | MEDIUM5.61 | libevent 2.1.12-8.el9_4 fixed in 2.1.13-1.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63379 | MEDIUM5.52 | libevent 2.1.12-8.el9_4 fixed in 2.1.13-1.el9_8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-89158 | MEDIUM5.52 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89160 | MEDIUM5.52 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | expat 2.5.0-6.el9_8.1 fixed in 2.5.0-6.el9_8.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | glibc 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | glibc 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | glibc 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | glibc-common 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | glibc-common 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | glibc-common 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | glibc-minimal-langpack 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | glibc-minimal-langpack 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | glibc-minimal-langpack 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-89156 | MEDIUM5.02 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | glibc 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | glibc-common 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | glibc-minimal-langpack 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | glibc 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | glibc-common 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | glibc-minimal-langpack 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-73073 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 fixed in 2:8.2.2637-26.el9_8.23 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-73076 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 fixed in 2:8.2.2637-26.el9_8.21 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-73077 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 fixed in 2:8.2.2637-26.el9_8.21 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl-minimal 7.76.1-40.el9_8.5 fixed in 7.76.1-40.el9_8.7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-40553 | LOW3.82 | gawk 5.1.0-6.el9 fixed in 5.1.0-6.el9_8.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl-minimal 7.76.1-40.el9_8.5 fixed in 7.76.1-40.el9_8.7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-54874 | LOW3.82 | openssl 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63074 | LOW3.82 | openssl 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63075 | LOW3.82 | openssl 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-63072 | LOW3.82 | openssl 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-84782 | LOW3.77 | openssl 1:3.5.5-6.el9_8 fixed in 1:3.5.8-2.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-73072 | LOW3.72 | vim-minimal 2:8.2.2637-26.el9_8.13 fixed in 2:8.2.2637-26.el9_8.21 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-19542 | LOW3.57 | glibc 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | glibc-common 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | glibc-minimal-langpack 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63073 | LOW3.54 | openssl 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | curl-minimal 7.76.1-40.el9_8.5 fixed in 7.76.1-40.el9_8.8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl-minimal 7.76.1-40.el9_8.5 fixed in 7.76.1-40.el9_8.8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | libcurl-minimal 7.76.1-40.el9_8.5 fixed in 7.76.1-40.el9_8.8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl-minimal 7.76.1-40.el9_8.5 fixed in 7.76.1-40.el9_8.8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW3.11 | coreutils-single 8.32-41.el9_8 fixed in 8.32-41.el9_8.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55892 | LOW2.8 | vim-minimal 2:8.2.2637-26.el9_8.13 fixed in 2:8.2.2637-26.el9_8.21 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59857 | LOW2.8 | vim-minimal 2:8.2.2637-26.el9_8.13 fixed in 2:8.2.2637-26.el9_8.21 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-40468 | LOW2.78 | gawk 5.1.0-6.el9 fixed in 5.1.0-6.el9_8.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-14457 | LOW2.7 | openssl 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-18798 | LOW2.7 | openssl 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63076 | LOW2.7 | openssl 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-14457 | LOW2.7 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-18798 | LOW2.7 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63076 | LOW2.7 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-73078 | LOW2.69 | vim-minimal 2:8.2.2637-26.el9_8.13 fixed in 2:8.2.2637-26.el9_8.21 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-63387 | LOW2.63 | libevent 2.1.12-8.el9_4 fixed in 2.1.13-1.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-74860 | LOW2.6 | libxml2 2.9.13-14.el9_8.4 fixed in 2.9.13-14.el9_8.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-63388 | LOW2.57 | libevent 2.1.12-8.el9_4 fixed in 2.1.13-1.el9_8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86145 | LOW2.51 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-52859 | LOW2.51 | vim-minimal 2:8.2.2637-26.el9_8.13 fixed in 2:8.2.2637-26.el9_8.21 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.48 | curl-minimal 7.76.1-40.el9_8.5 fixed in 7.76.1-40.el9_8.7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.48 | libcurl-minimal 7.76.1-40.el9_8.5 fixed in 7.76.1-40.el9_8.7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-86138 | LOW2.39 | libxml2 2.9.13-14.el9_8.4 fixed in 2.9.13-14.el9_8.5 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86140 | LOW2.39 | libxml2 2.9.13-14.el9_8.4 fixed in 2.9.13-14.el9_8.5 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86142 | LOW2.39 | libxml2 2.9.13-14.el9_8.4 fixed in 2.9.13-14.el9_8.5 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86144 | LOW2.39 | libxml2 2.9.13-14.el9_8.4 fixed in 2.9.13-14.el9_8.5 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-89161 | LOW2.39 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-63382 | LOW2.36 | libevent 2.1.12-8.el9_4 fixed in 2.1.13-1.el9_8 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-63385 | LOW2.36 | libevent 2.1.12-8.el9_4 fixed in 2.1.13-1.el9_8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-103111 | LOW2.33 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-40467 | LOW2.29 | gawk 5.1.0-6.el9 fixed in 5.1.0-6.el9_8.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-14456 | LOW2.29 | openssl 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-14456 | LOW2.29 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-54874 | LOW2.29 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63074 | LOW2.29 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63075 | LOW2.29 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-63072 | LOW2.29 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-28420 | LOW2.24 | vim-minimal 2:8.2.2637-26.el9_8.13 fixed in 2:8.2.2637-26.el9_8.21 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86145 | NONE0 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89161 | NONE0 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-103111 | NONE0 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89157 | NONE0 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89158 | NONE0 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89160 | NONE0 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89156 | NONE0 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | pam 1.5.1-28.el9 fixed in 1.5.1-28.el9_8.1 | 0.5% 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.