Last scanned:
AI verdict failed due to an error.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| 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-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-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-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-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 | libacl 2.3.1-4.el9 fixed in 2.4.0-1.el9_8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | glibc 2.34-270.el9_8 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | glibc-common 2.34-270.el9_8 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | glibc-minimal-langpack 2.34-270.el9_8 fixed in 2.34-274.el9_8 | 0.4% 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-270.el9_8 fixed in 2.34-274.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | glibc-common 2.34-270.el9_8 fixed in 2.34-274.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | glibc-minimal-langpack 2.34-270.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-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-270.el9_8 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | glibc 2.34-270.el9_8 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | glibc-common 2.34-270.el9_8 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | glibc-common 2.34-270.el9_8 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | glibc-minimal-langpack 2.34-270.el9_8 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | glibc-minimal-langpack 2.34-270.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-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.