Last scanned:
This base/runtime image is a reasonable foundation, but it ships vulnerabilities worth remediating in the images built on top of it. The most notable finding is CVE-2026-54369 in libacl, a local symlink traversal vulnerability that could allow privilege escalation; however, it requires local access and is not remotely exploitable. Among the 43 exposed findings, only this one reaches a severity above 6.0, and post-exploit findings are low-severity (max 3.98). Upgrading libacl to version 2.4.0 or later fully mitigates this risk. Overall, the image is a trusted official base, but teams should apply patches before relying on it in production. 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-54369 | MEDIUM6.03 | libacl 2.2.53-3.el8 fixed in 2.4.0-1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM5.95 | libcap 2.48-6.el8_9 fixed in 2.48-6.el8_10.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1 4.13-5.el8_10 fixed in 4.13-6.el8_10 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42010 | MEDIUM5.88 | gnutls 3.6.16-8.el8_10.5 fixed in 3.6.16-8.el8_10.6 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | gnutls 3.6.16-8.el8_10.5 fixed in 3.6.16-8.el8_10.6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | openssl-libs 1:1.1.1k-15.el8_6 fixed in 1:1.1.1k-16.el8_6 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14512 | MEDIUM5.52 | glib2 2.56.4-168.el8_10 fixed in 2.56.4-169.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc 2.28-251.el8_10.31 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc-common 2.28-251.el8_10.31 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc-minimal-langpack 2.28-251.el8_10.31 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-34459 | MEDIUM5.5 | libxml2 2.9.7-21.el8_10.3 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-5435 | MEDIUM5.02 | glibc 2.28-251.el8_10.31 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-common 2.28-251.el8_10.31 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-minimal-langpack 2.28-251.el8_10.31 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14087 | MEDIUM5 | glib2 2.56.4-168.el8_10 fixed in 2.56.4-169.el8_10 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-45447 | MEDIUM4.86 | openssl-libs 1:1.1.1k-15.el8_6 fixed in 1:1.1.1k-16.el8_6 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9714 | MEDIUM4.67 | libxml2 2.9.7-21.el8_10.3 fixed in 2.9.7-21.el8_10.4 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | MEDIUM4.64 | glib2 2.56.4-168.el8_10 fixed in 2.56.4-170.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | MEDIUM4.64 | gnutls 3.6.16-8.el8_10.5 fixed in 3.6.16-8.el8_10.6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33846 | MEDIUM4.5 | gnutls 3.6.16-8.el8_10.5 fixed in 3.6.16-8.el8_10.6 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | MEDIUM4.5 | gnutls 3.6.16-8.el8_10.5 fixed in 3.6.16-8.el8_10.6 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28390 | MEDIUM4.5 | openssl-libs 1:1.1.1k-15.el8_6 fixed in 1:1.1.1k-17.el8_6 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc 2.28-251.el8_10.31 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-common 2.28-251.el8_10.31 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-minimal-langpack 2.28-251.el8_10.31 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | gnutls 3.6.16-8.el8_10.5 fixed in 3.6.16-8.el8_10.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc 2.28-251.el8_10.31 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.31 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.31 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.31 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.31 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.31 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM4.18 | gnutls 3.6.16-8.el8_10.5 fixed in 3.6.16-8.el8_10.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM4.18 | gnutls 3.6.16-8.el8_10.5 fixed in 3.6.16-8.el8_10.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-28421 | LOW3.98 | vim-minimal 2:8.0.1763-22.el8_10 fixed in 2:8.0.1763-22.el8_10.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55693 | LOW3.98 | vim-minimal 2:8.0.1763-22.el8_10 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 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 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 fixed in 2:8.0.1763-31.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45186 | LOW3.83 | expat 2.5.0-1.el8_10 fixed in 2.5.0-2.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | LOW3.83 | krb5-libs 1.18.2-32.el8_10 fixed in 1.18.2-34.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | LOW3.83 | krb5-libs 1.18.2-32.el8_10 fixed in 1.18.2-34.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-27135 | LOW3.83 | libnghttp2 1.33.0-6.el8_10.1 fixed in 1.33.0-6.el8_10.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | LOW3.77 | gnutls 3.6.16-8.el8_10.5 fixed in 3.6.16-8.el8_10.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | LOW3.77 | gnutls 3.6.16-8.el8_10.5 fixed in 3.6.16-8.el8_10.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33412 | LOW3.72 | vim-minimal 2:8.0.1763-22.el8_10 fixed in 2:8.0.1763-22.el8_10.1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-41411 | LOW3.72 | vim-minimal 2:8.0.1763-22.el8_10 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-42012 | LOW3.62 | gnutls 3.6.16-8.el8_10.5 fixed in 3.6.16-8.el8_10.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-35177 | LOW3.62 | vim-minimal 2:8.0.1763-22.el8_10 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-28417 | LOW2.81 | vim-minimal 2:8.0.1763-22.el8_10 fixed in 2:8.0.1763-22.el8_10.1 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5121 | LOW2.7 | libarchive 3.3.3-6.el8_10 fixed in 3.3.3-7.el8_10 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34982 | LOW2.51 | vim-minimal 2:8.0.1763-22.el8_10 fixed in 2:8.0.1763-22.el8_10.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | LOW2.48 | platform-python 3.6.8-75.el8_10.alma.1 fixed in 3.6.8-76.el8_10.alma.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | LOW2.48 | python3-libs 3.6.8-75.el8_10.alma.1 fixed in 3.6.8-76.el8_10.alma.1 | 0.6% Theoretical Threat | 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-4424 | LOW2.29 | libarchive 3.3.3-6.el8_10 fixed in 3.3.3-7.el8_10 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-4786 | LOW2.17 | platform-python 3.6.8-75.el8_10.alma.1 fixed in 3.6.8-76.el8_10.alma.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4786 | LOW2.17 | python3-libs 3.6.8-75.el8_10.alma.1 fixed in 3.6.8-76.el8_10.alma.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-6170 | LOW2.12 | libxml2 2.9.7-21.el8_10.3 fixed in 2.9.7-21.el8_10.6 | 0.2% Theoretical Threat | Directly Exposed |
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.