Last scanned:
AI verdict failed due to an error.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-45447 | MEDIUM4.86 | openssl 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45445 | MEDIUM4.64 | openssl 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-34183 | MEDIUM4.5 | openssl 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28390 | MEDIUM4.5 | openssl 1:3.5.5-2.el9_8 fixed in 1:3.5.5-3.el9_8 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34182 | LOW3.77 | openssl 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42764 | LOW3.54 | openssl 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34181 | LOW3.21 | openssl 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42768 | LOW3.21 | openssl 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42769 | LOW3.01 | openssl 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.01 | openssl 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW3 | openssl 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW1.89 | openssl 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42010 | NONE0 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-58016 | NONE0 | glib2 2.68.4-19.el9_8.1 fixed in 2.68.4-19.el9_8.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-33845 | NONE0 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-45445 | NONE0 | openssl-libs 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42013 | NONE0 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5260 | NONE0 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-45447 | NONE0 | openssl-libs 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-48864 | NONE0 | libsolv 0.7.24-4.el9 fixed in 0.7.24-6.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55693 | NONE0 | vim-minimal 2:8.2.2637-26.el9_8.4 fixed in 2:8.2.2637-26.el9_8.13 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57455 | NONE0 | vim-minimal 2:8.2.2637-26.el9_8.4 fixed in 2:8.2.2637-26.el9_8.13 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57456 | NONE0 | vim-minimal 2:8.2.2637-26.el9_8.4 fixed in 2:8.2.2637-26.el9_8.13 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59856 | NONE0 | vim-minimal 2:8.2.2637-26.el9_8.4 fixed in 2:8.2.2637-26.el9_8.13 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59858 | NONE0 | vim-minimal 2:8.2.2637-26.el9_8.4 fixed in 2:8.2.2637-26.el9_8.13 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45186 | NONE0 | expat 2.5.0-6.el9 fixed in 2.5.0-6.el9_8.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-33846 | NONE0 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-42009 | NONE0 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-34183 | NONE0 | openssl-libs 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-28390 | NONE0 | openssl-libs 1:3.5.5-2.el9_8 fixed in 1:3.5.5-3.el9_8 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-15308 | NONE0 | python3 3.9.25-7.el9_8 fixed in 3.9.25-7.el9_8.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-15308 | NONE0 | python3-libs 3.9.25-7.el9_8 fixed in 3.9.25-7.el9_8.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3833 | NONE0 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42011 | NONE0 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-34182 | NONE0 | openssl-libs 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-54369 | NONE0 | acl 2.3.1-4.el9 fixed in 2.4.0-1.el9_8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42012 | NONE0 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-54369 | NONE0 | libacl 2.3.1-4.el9 fixed in 2.4.0-1.el9_8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35177 | NONE0 | vim-minimal 2:8.2.2637-26.el9_8.4 fixed in 2:8.2.2637-26.el9_8.5 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42014 | NONE0 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4437 | NONE0 | glibc 2.34-266.el9_8 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | glibc 2.34-266.el9_8 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4437 | NONE0 | glibc-common 2.34-266.el9_8 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | glibc-common 2.34-266.el9_8 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4437 | NONE0 | glibc-minimal-langpack 2.34-266.el9_8 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | glibc-minimal-langpack 2.34-266.el9_8 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-54370 | NONE0 | acl 2.3.1-4.el9 fixed in 2.4.0-1.el9_8 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54370 | NONE0 | libacl 2.3.1-4.el9 fixed in 2.4.0-1.el9_8 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34181 | NONE0 | openssl-libs 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42768 | NONE0 | openssl-libs 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | glibc 2.34-266.el9_8 fixed in 2.34-274.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | glibc-common 2.34-266.el9_8 fixed in 2.34-274.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | glibc-minimal-langpack 2.34-266.el9_8 fixed in 2.34-274.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-13151 | NONE0 | libtasn1 4.16.0-9.el9 fixed in 4.16.0-10.el9_8 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-42764 | NONE0 | openssl-libs 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-42769 | NONE0 | openssl-libs 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42770 | NONE0 | openssl-libs 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-9076 | NONE0 | openssl-libs 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-34459 | NONE0 | libxml2 2.9.13-14.el9_7 fixed in 2.9.13-14.el9_8.1 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-7383 | NONE0 | openssl-libs 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | glibc 2.34-266.el9_8 fixed in 2.34-270.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | glibc-common 2.34-266.el9_8 fixed in 2.34-270.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | glibc-minimal-langpack 2.34-266.el9_8 fixed in 2.34-270.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42015 | NONE0 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-42766 | NONE0 | openssl-libs 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-42767 | NONE0 | openssl-libs 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | glibc 2.34-266.el9_8 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | glibc 2.34-266.el9_8 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | glibc-common 2.34-266.el9_8 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | glibc-common 2.34-266.el9_8 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | glibc-minimal-langpack 2.34-266.el9_8 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | glibc-minimal-langpack 2.34-266.el9_8 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-34180 | NONE0 | openssl-libs 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-5278 | NONE0 | coreutils-single 8.32-40.el9 fixed in 8.32-41.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4438 | NONE0 | glibc 2.34-266.el9_8 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-4438 | NONE0 | glibc-common 2.34-266.el9_8 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-4438 | NONE0 | glibc-minimal-langpack 2.34-266.el9_8 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-3832 | NONE0 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-5419 | NONE0 | gnutls 3.8.10-3.el9 fixed in 3.8.10-4.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45446 | NONE0 | openssl-libs 1:3.5.5-2.el9_8 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6170 | NONE0 | libxml2 2.9.13-14.el9_7 fixed in 2.9.13-14.el9_8.2 | 0.2% Theoretical Threat | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
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.