Last scanned:
This base/runtime image is a clean foundation for building production images. It is an official Docker Hub image pinned by digest, and the pre-calculated threat score is 0, which places it in the SAFE band. INPUT 3 does report 14 exposed-surface findings and 37 post-exploit-only findings, but none reach severity 6.0; the maximum exposed severity is 5.87 and the maximum post-exploit-only severity is 3.98. Images built on top inherit those low-severity issues, but no CVE IDs are present in the provided top findings and there are no high-severity exposures to drive a higher 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-56132 | MEDIUM5.87 | expat 2.5.0-2.el8_10 fixed in 2.5.0-2.el8_10.2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | expat 2.5.0-2.el8_10 fixed in 2.5.0-2.el8_10.2 | 0.2% 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-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-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-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-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-73073 | LOW3.98 | vim-minimal 2:8.0.1763-31.el8_10 fixed in 2:8.0.1763-32.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-73076 | LOW3.98 | vim-minimal 2:8.0.1763-31.el8_10 fixed in 2:8.0.1763-31.el8_10.7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-73072 | LOW3.72 | vim-minimal 2:8.0.1763-31.el8_10 fixed in 2:8.0.1763-31.el8_10.7 | 0.1% Theoretical Threat | Post-Exploit |
| 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-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-2025-45582 | LOW2.86 | tar 2:1.30-11.el8_10 fixed in 2:1.30-13.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 2:1.30-11.el8_10 fixed in 2:1.30-13.el8_10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-55892 | LOW2.8 | vim-minimal 2:8.0.1763-31.el8_10 fixed in 2:8.0.1763-31.el8_10.7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59857 | LOW2.8 | vim-minimal 2:8.0.1763-31.el8_10 fixed in 2:8.0.1763-31.el8_10.7 | 0.1% 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-73078 | LOW2.69 | vim-minimal 2:8.0.1763-31.el8_10 fixed in 2:8.0.1763-31.el8_10.7 | 0.3% 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-52859 | LOW2.51 | vim-minimal 2:8.0.1763-31.el8_10 fixed in 2:8.0.1763-31.el8_10.7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.9-13.el8_5 fixed in 1.9-15.el8_10 | 0.1% 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-66046 | LOW2.29 | expat 2.5.0-2.el8_10 fixed in 2.5.0-4.el8_10 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-93990 | LOW2.29 | expat 2.5.0-2.el8_10 fixed in 2.5.0-4.el8_10 | 0.4% 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-41992 | LOW2.29 | gzip 1.9-13.el8_5 fixed in 1.9-15.el8_10 | 0.6% 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-18477 | LOW2.24 | tar 2:1.30-11.el8_10 fixed in 2:1.30-13.el8_10 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.24 | tar 2:1.30-11.el8_10 fixed in 2:1.30-13.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28420 | LOW2.24 | vim-minimal 2:8.0.1763-31.el8_10 fixed in 2:8.0.1763-31.el8_10.7 | 0.2% 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-89158 | LOW1.99 | pcre2 10.32-3.el8_6 fixed in 10.32-4.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6791 | LOW1.81 | glibc 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.43 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-77117 | LOW1.81 | glibc 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6791 | LOW1.81 | glibc-common 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.43 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-77117 | LOW1.81 | glibc-common 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6791 | LOW1.81 | glibc-minimal-langpack 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.43 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-77117 | LOW1.81 | glibc-minimal-langpack 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.4% 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.