Last scanned:
This base/runtime image is a clean foundation for building production images. The supplied stats show 24 exposed findings and 23 post-exploit-only findings, so it is not vulnerability-free. However, exposed_count_ge6 is 0 and exposed_max_severity is 5.02, while post_count_ge6 is 0 and post_max_severity is 3.0. No CVE IDs were included in the supplied top findings, so no specific CVE-driven inherited risk can be cited from these inputs. Images built on top inherit these low-severity issues, but they do not meet the thresholds for an elevated verdict. 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-6791 | MEDIUM5.02 | glibc 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.43 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | glibc 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | glibc 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | glibc-common 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.43 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | glibc-common 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | glibc-common 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | glibc-minimal-langpack 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.43 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | glibc-minimal-langpack 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | glibc-minimal-langpack 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59845 | MEDIUM5.02 | libssh 0.9.6-16.el8_10 fixed in 0.9.6-17.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-59845 | MEDIUM5.02 | libssh-config 0.9.6-16.el8_10 fixed in 0.9.6-17.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | glibc 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.43 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | glibc-common 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.43 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | glibc-minimal-langpack 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.43 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-59848 | MEDIUM4.5 | libssh 0.9.6-16.el8_10 fixed in 0.9.6-17.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59848 | MEDIUM4.5 | libssh-config 0.9.6-16.el8_10 fixed in 0.9.6-17.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | glibc 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | glibc-common 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | glibc-minimal-langpack 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | glibc 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | glibc-common 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | glibc-minimal-langpack 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59846 | LOW3.31 | libssh 0.9.6-16.el8_10 fixed in 0.9.6-17.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-59846 | LOW3.31 | libssh-config 0.9.6-16.el8_10 fixed in 0.9.6-17.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6653 | LOW3 | libxml2 2.9.7-21.el8_10.7 fixed in 2.9.7-21.el8_10.8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-40468 | LOW2.78 | gawk 4.2.1-4.el8 fixed in 4.2.1-5.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-74860 | LOW2.6 | libxml2 2.9.7-21.el8_10.7 fixed in 2.9.7-21.el8_10.9 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-86145 | LOW2.51 | pcre2 10.32-3.el8_6 fixed in 10.32-4.el8_10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-86138 | LOW2.39 | libxml2 2.9.7-21.el8_10.7 fixed in 2.9.7-21.el8_10.9 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86140 | LOW2.39 | libxml2 2.9.7-21.el8_10.7 fixed in 2.9.7-21.el8_10.9 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86142 | LOW2.39 | libxml2 2.9.7-21.el8_10.7 fixed in 2.9.7-21.el8_10.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86144 | LOW2.39 | libxml2 2.9.7-21.el8_10.7 fixed in 2.9.7-21.el8_10.9 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-103111 | LOW2.33 | pcre2 10.32-3.el8_6 fixed in 10.32-4.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-40467 | LOW2.29 | gawk 4.2.1-4.el8 fixed in 4.2.1-5.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59847 | LOW2.29 | libssh 0.9.6-16.el8_10 fixed in 0.9.6-17.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59850 | LOW2.29 | libssh 0.9.6-16.el8_10 fixed in 0.9.6-17.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59847 | LOW2.29 | libssh-config 0.9.6-16.el8_10 fixed in 0.9.6-17.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59850 | LOW2.29 | libssh-config 0.9.6-16.el8_10 fixed in 0.9.6-17.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-89157 | LOW2.26 | pcre2 10.32-3.el8_6 fixed in 10.32-4.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils-single 8.30-20.el8_10 fixed in 8.30-21.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-86143 | LOW2.23 | libxml2 2.9.7-21.el8_10.7 fixed in 2.9.7-21.el8_10.9 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-16118 | LOW2.17 | glib2 2.56.4-177.el8_10 fixed in 2.56.4-178.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59843 | LOW1.99 | libssh 0.9.6-16.el8_10 fixed in 0.9.6-17.el8_10 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-59844 | LOW1.99 | libssh 0.9.6-16.el8_10 fixed in 0.9.6-17.el8_10 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-59843 | LOW1.99 | libssh-config 0.9.6-16.el8_10 fixed in 0.9.6-17.el8_10 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-59844 | LOW1.99 | libssh-config 0.9.6-16.el8_10 fixed in 0.9.6-17.el8_10 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-89158 | LOW1.99 | pcre2 10.32-3.el8_6 fixed in 10.32-4.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
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.