Last scanned:
This base/runtime image is a clean foundation for building production images. While the image contains 9 exposed vulnerabilities and 22 post-exploit-only findings, all are low severity with maximum scores of 5.5 and 3.98, respectively. Because no finding reaches the 6.0 threshold, they do not present significant inheritable risk to images built on top. The image is official, pinned by digest, and has a perfect trust score, making it a reliable base image for production use. 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-2024-34459 | MEDIUM5.5 | libxml2 2.9.7-21.el8_10.4 fixed in 2.9.7-21.el8_10.5 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl 2.2.53-3.el8 fixed in 2.4.0-1.el8_10 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-common 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-common 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-minimal-langpack 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-minimal-langpack 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-55693 | LOW3.98 | vim-minimal 2:8.0.1763-22.el8_10.3 fixed in 2:8.0.1763-31.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57455 | LOW3.98 | vim-minimal 2:8.0.1763-22.el8_10.3 fixed in 2:8.0.1763-31.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57456 | LOW3.98 | vim-minimal 2:8.0.1763-22.el8_10.3 fixed in 2:8.0.1763-31.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59858 | LOW3.98 | vim-minimal 2:8.0.1763-22.el8_10.3 fixed in 2:8.0.1763-31.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41411 | LOW3.72 | vim-minimal 2:8.0.1763-22.el8_10.3 fixed in 2:8.0.1763-24.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-54369 | LOW3.62 | acl 2.2.53-3.el8 fixed in 2.4.0-1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-35177 | LOW3.62 | vim-minimal 2:8.0.1763-22.el8_10.3 fixed in 2:8.0.1763-23.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-54370 | LOW3.21 | acl 2.2.53-3.el8 fixed in 2.4.0-1.el8_10 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl-libs 1:1.1.1k-15.el8_6 fixed in 1:1.1.1k-16.el8_6 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-58016 | LOW2.78 | glib2 2.56.4-169.el8_10 fixed in 2.56.4-170.el8_10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | LOW2.7 | openssl-libs 1:1.1.1k-15.el8_6 fixed in 1:1.1.1k-17.el8_6 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-48864 | LOW2.39 | libsolv 0.7.20-6.el8 fixed in 0.7.20-7.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45186 | LOW2.29 | expat 2.5.0-1.el8_10 fixed in 2.5.0-2.el8_10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-54369 | LOW2.17 | libacl 2.2.53-3.el8 fixed in 2.4.0-1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13151 | LOW2.12 | libtasn1 4.13-5.el8_10 fixed in 4.13-6.el8_10 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-6170 | LOW2.12 | libxml2 2.9.7-21.el8_10.4 fixed in 2.9.7-21.el8_10.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-4741 | LOW2.02 | openssl-libs 1:1.1.1k-15.el8_6 fixed in 1:1.1.1k-16.el8_6 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-6238 | LOW1.99 | glibc 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW1.99 | glibc-common 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW1.99 | glibc-minimal-langpack 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW1.81 | glibc 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW1.81 | glibc-common 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW1.81 | glibc-minimal-langpack 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.40 | 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.