Last scanned:
AI verdict failed due to an error.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2025-14087 | NONE0 | glib2 2.56.4-168.el8_10 fixed in 2.56.4-169.el8_10 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42010 | NONE0 | gnutls 3.6.16-8.el8_10.5 fixed in 3.6.16-8.el8_10.6 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-58016 | NONE0 | glib2 2.56.4-168.el8_10 fixed in 2.56.4-170.el8_10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-33845 | NONE0 | gnutls 3.6.16-8.el8_10.5 fixed in 3.6.16-8.el8_10.6 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42013 | NONE0 | gnutls 3.6.16-8.el8_10.5 fixed in 3.6.16-8.el8_10.6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5260 | NONE0 | gnutls 3.6.16-8.el8_10.5 fixed in 3.6.16-8.el8_10.6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-45447 | NONE0 | openssl-libs 1:1.1.1k-15.el8_6 fixed in 1:1.1.1k-16.el8_6 | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-48864 | NONE0 | libsolv 0.7.20-6.el8 fixed in 0.7.20-7.el8_10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-33846 | NONE0 | gnutls 3.6.16-8.el8_10.5 fixed in 3.6.16-8.el8_10.6 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-42009 | NONE0 | gnutls 3.6.16-8.el8_10.5 fixed in 3.6.16-8.el8_10.6 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-40355 | NONE0 | krb5-libs 1.18.2-32.el8_10 fixed in 1.18.2-34.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-40356 | NONE0 | krb5-libs 1.18.2-32.el8_10 fixed in 1.18.2-34.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4424 | NONE0 | libarchive 3.3.3-6.el8_10 fixed in 3.3.3-7.el8_10 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-5121 | NONE0 | libarchive 3.3.3-6.el8_10 fixed in 3.3.3-7.el8_10 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-27135 | NONE0 | libnghttp2 1.33.0-6.el8_10.1 fixed in 1.33.0-6.el8_10.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-28390 | NONE0 | openssl-libs 1:1.1.1k-15.el8_6 fixed in 1:1.1.1k-17.el8_6 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-3833 | NONE0 | gnutls 3.6.16-8.el8_10.5 fixed in 3.6.16-8.el8_10.6 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42011 | NONE0 | gnutls 3.6.16-8.el8_10.5 fixed in 3.6.16-8.el8_10.6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-42012 | NONE0 | gnutls 3.6.16-8.el8_10.5 fixed in 3.6.16-8.el8_10.6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-54369 | NONE0 | libacl 2.2.53-3.el8 fixed in 2.4.0-1.el8_10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4878 | NONE0 | libcap 2.48-6.el8_9 fixed in 2.48-6.el8_10.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42014 | NONE0 | gnutls 3.6.16-8.el8_10.5 fixed in 3.6.16-8.el8_10.6 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14512 | NONE0 | glib2 2.56.4-168.el8_10 fixed in 2.56.4-169.el8_10 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | glibc 2.28-251.el8_10.31 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | glibc-common 2.28-251.el8_10.31 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | glibc-minimal-langpack 2.28-251.el8_10.31 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-54370 | NONE0 | libacl 2.2.53-3.el8 fixed in 2.4.0-1.el8_10 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | glibc 2.28-251.el8_10.31 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | glibc-common 2.28-251.el8_10.31 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | glibc-minimal-langpack 2.28-251.el8_10.31 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-13151 | NONE0 | libtasn1 4.13-5.el8_10 fixed in 4.13-6.el8_10 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-4741 | NONE0 | openssl-libs 1:1.1.1k-15.el8_6 fixed in 1:1.1.1k-16.el8_6 | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-9714 | NONE0 | libxml2 2.9.7-21.el8_10.3 fixed in 2.9.7-21.el8_10.4 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-34459 | NONE0 | libxml2 2.9.7-21.el8_10.3 fixed in 2.9.7-21.el8_10.5 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-4046 | NONE0 | glibc 2.28-251.el8_10.31 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | glibc-common 2.28-251.el8_10.31 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | glibc-minimal-langpack 2.28-251.el8_10.31 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42015 | NONE0 | gnutls 3.6.16-8.el8_10.5 fixed in 3.6.16-8.el8_10.6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | glibc 2.28-251.el8_10.31 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | glibc 2.28-251.el8_10.31 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | glibc-common 2.28-251.el8_10.31 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | glibc-common 2.28-251.el8_10.31 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | glibc-minimal-langpack 2.28-251.el8_10.31 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | glibc-minimal-langpack 2.28-251.el8_10.31 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6170 | NONE0 | libxml2 2.9.7-21.el8_10.3 fixed in 2.9.7-21.el8_10.6 | 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.