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 47 exposed findings include four at severity 6.0–6.9, mainly in gnutls (CVE-2026-3833, CVE-2026-42011) that could compromise certificate validation, and a local symlink issue. Because none reach severity 7 and post-exploit issues are negligible, it does not block production use, but you should update the gnutls and libacl packages in your final image. 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.
Hardening plan for this image · 2 steps
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-3833 | MEDIUM6.29 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl 2.3.1-4.el9 fixed in 2.4.0-1.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM5.95 | libcap 2.48-10.el9_7.1 fixed in 2.48-10.el9_8.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1 4.16.0-9.el9 fixed in 4.16.0-10.el9_8 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-2.el9_8 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14512 | MEDIUM5.52 | glib2 2.68.4-18.el9_7.1 fixed in 2.68.4-19.el9_8.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc 2.34-231.el9_7.10 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc 2.34-231.el9_7.10 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc-common 2.34-231.el9_7.10 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc-common 2.34-231.el9_7.10 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc-minimal-langpack 2.34-231.el9_7.10 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc-minimal-langpack 2.34-231.el9_7.10 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-34459 | MEDIUM5.5 | libxml2 2.9.13-14.el9_7 fixed in 2.9.13-14.el9_8.1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl 2.3.1-4.el9 fixed in 2.4.0-1.el9_8 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc 2.34-231.el9_7.10 fixed in 2.34-274.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-common 2.34-231.el9_7.10 fixed in 2.34-274.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-minimal-langpack 2.34-231.el9_7.10 fixed in 2.34-274.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc 2.34-231.el9_7.10 fixed in 2.34-270.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-common 2.34-231.el9_7.10 fixed in 2.34-270.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-minimal-langpack 2.34-231.el9_7.10 fixed in 2.34-270.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc 2.34-231.el9_7.10 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc 2.34-231.el9_7.10 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-common 2.34-231.el9_7.10 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-common 2.34-231.el9_7.10 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-minimal-langpack 2.34-231.el9_7.10 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-minimal-langpack 2.34-231.el9_7.10 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-55693 | LOW3.98 | vim-minimal 2:8.2.2637-23.el9_7.3 fixed in 2:8.2.2637-26.el9_8.13 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57455 | LOW3.98 | vim-minimal 2:8.2.2637-23.el9_7.3 fixed in 2:8.2.2637-26.el9_8.13 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57456 | LOW3.98 | vim-minimal 2:8.2.2637-23.el9_7.3 fixed in 2:8.2.2637-26.el9_8.13 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59856 | LOW3.98 | vim-minimal 2:8.2.2637-23.el9_7.3 fixed in 2:8.2.2637-26.el9_8.13 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59858 | LOW3.98 | vim-minimal 2:8.2.2637-23.el9_7.3 fixed in 2:8.2.2637-26.el9_8.13 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-54369 | LOW3.62 | acl 2.3.1-4.el9 fixed in 2.4.0-1.el9_8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4786 | LOW3.62 | python3 3.9.25-3.el9_7.3 fixed in 3.9.25-7.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4786 | LOW3.62 | python3-libs 3.9.25-3.el9_7.3 fixed in 3.9.25-7.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-35177 | LOW3.62 | vim-minimal 2:8.2.2637-23.el9_7.3 fixed in 2:8.2.2637-26.el9_8.5 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42764 | LOW3.54 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-31790 | LOW3.54 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-2.el9_8 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42010 | LOW3.53 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4438 | LOW3.4 | glibc 2.34-231.el9_7.10 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc-common 2.34-231.el9_7.10 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc-minimal-langpack 2.34-231.el9_7.10 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54370 | LOW3.21 | acl 2.3.1-4.el9 fixed in 2.4.0-1.el9_8 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-34181 | LOW3.21 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42768 | LOW3.21 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3832 | LOW3.15 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW3.15 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | LOW3.01 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.01 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14087 | LOW3 | glib2 2.68.4-18.el9_7.1 fixed in 2.68.4-19.el9_8.1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW3 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-58016 | LOW2.78 | glib2 2.68.4-18.el9_7.1 fixed in 2.68.4-19.el9_8.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-33845 | LOW2.78 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-33846 | LOW2.7 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42009 | LOW2.7 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34183 | LOW2.7 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28390 | LOW2.7 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-3.el9_8 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34183 | LOW2.7 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28390 | LOW2.7 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-3.el9_8 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-2100 | LOW2.7 | p11-kit 0.25.3-3.el9_5 fixed in 0.26.2-1.el9 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-2100 | LOW2.7 | p11-kit-trust 0.25.3-3.el9_5 fixed in 0.26.2-1.el9 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42013 | LOW2.51 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5260 | LOW2.51 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-34982 | LOW2.51 | vim-minimal 2:8.2.2637-23.el9_7.3 fixed in 2:8.2.2637-26.el9_8.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | LOW2.48 | python3 3.9.25-3.el9_7.3 fixed in 3.9.25-7.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | LOW2.48 | python3-libs 3.9.25-3.el9_7.3 fixed in 3.9.25-7.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-48864 | LOW2.39 | libsolv 0.7.24-3.el9 fixed in 0.7.24-6.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-29111 | LOW2.39 | systemd-libs 252-55.el9_7.8.alma.1 fixed in 252-67.el9_8.2.alma.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45186 | LOW2.29 | expat 2.5.0-5.el9_7.1 fixed in 2.5.0-6.el9_8.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-40355 | LOW2.29 | krb5-libs 1.21.1-9.el9_7 fixed in 1.21.1-10.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-40356 | LOW2.29 | krb5-libs 1.21.1-9.el9_7 fixed in 1.21.1-10.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-15308 | LOW2.29 | python3 3.9.25-3.el9_7.3 fixed in 3.9.25-7.el9_8.2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-15308 | LOW2.29 | python3-libs 3.9.25-3.el9_7.3 fixed in 3.9.25-7.el9_8.2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW2.26 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW2.26 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils-single 8.32-39.el9 fixed in 8.32-41.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6170 | LOW2.12 | libxml2 2.9.13-14.el9_7 fixed in 2.9.13-14.el9_8.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW1.89 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-29111 | NONE0 | systemd 252-55.el9_7.8.alma.1 fixed in 252-67.el9_8.2.alma.1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | systemd-pam 252-55.el9_7.8.alma.1 fixed in 252-67.el9_8.2.alma.1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | systemd-rpm-macros 252-55.el9_7.8.alma.1 fixed in 252-67.el9_8.2.alma.1 | 0.1% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.