Last scanned:
This image is acceptable for production, but remediating the identified vulnerabilities is recommended to reduce the attack surface. The image has 132 exposed-surface findings and 18 post-exploitation findings, but only one exposed finding reaches severity 6.0 and none are rated 7.0 or higher. The most notable item, CVE-2026-66046, is an expat denial-of-service flaw that could exhaust CPU only if an application in the container parses untrusted XML, which the default container role does not state it does. Teams should confirm that no XML-consuming workload uses this image in its default form, and should plan to update the expat package in the next maintenance cycle.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-66046 | MEDIUM6 | expat 2.5.0-2.el8_10 fixed in 2.5.0-4.el8_10 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-77117 | MEDIUM5.9 | glibc 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | glibc 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | glibc-common 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | glibc-common 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | glibc-langpack-en 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | glibc-langpack-en 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | glibc-minimal-langpack 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | glibc-minimal-langpack 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-35568 | MEDIUM5.7 | io.modelcontextprotocol.sdk:mcp-core 0.18.4 fixed in 1.0.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.52 | expat 2.5.0-2.el8_10 fixed in 2.5.0-2.el8_10.2 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6368 | MEDIUM5.5 | glibc 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.43 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | glibc-common 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.43 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | glibc-langpack-en 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.43 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | glibc-minimal-langpack 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.43 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-74744 | MEDIUM5.28 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-74752 | MEDIUM5.28 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.176.1.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-90036 | MEDIUM5.28 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.174.1.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0799 | MEDIUM5.22 | libpcap 14:1.9.1-5.el8 fixed in 14:1.9.1-6.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-74860 | MEDIUM5.1 | libxml2 2.9.7-21.el8_10.7 fixed in 2.9.7-21.el8_10.9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86145 | MEDIUM4.92 | pcre2 10.32-3.el8_6 fixed in 10.32-4.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52859 | MEDIUM4.92 | vim-minimal 2:8.0.1763-31.el8_10 fixed in 2:8.0.1763-31.el8_10.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | glibc 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | glibc-common 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | glibc-langpack-en 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | glibc-minimal-langpack 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-72318 | MEDIUM4.86 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.173.1.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-89526 | MEDIUM4.86 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.174.1.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-89631 | MEDIUM4.86 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.176.1.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-19445 | MEDIUM4.86 | python3-libs 3.6.8-78.el8_10.alma.1 fixed in 3.6.8-79.el8_10.alma.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM4.72 | expat 2.5.0-2.el8_10 fixed in 2.5.0-2.el8_10.2 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86138 | MEDIUM4.68 | libxml2 2.9.7-21.el8_10.7 fixed in 2.9.7-21.el8_10.9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86140 | MEDIUM4.68 | libxml2 2.9.7-21.el8_10.7 fixed in 2.9.7-21.el8_10.9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86142 | MEDIUM4.68 | libxml2 2.9.7-21.el8_10.7 fixed in 2.9.7-21.el8_10.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86144 | MEDIUM4.68 | libxml2 2.9.7-21.el8_10.7 fixed in 2.9.7-21.el8_10.9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31678 | MEDIUM4.68 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.173.1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63829 | MEDIUM4.68 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-68108 | MEDIUM4.68 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.173.1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-72052 | MEDIUM4.68 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-72255 | MEDIUM4.68 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-74582 | MEDIUM4.68 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.172.1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-74583 | MEDIUM4.68 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.174.1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-74746 | MEDIUM4.68 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-80536 | MEDIUM4.68 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.177.1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-89972 | MEDIUM4.68 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-93288 | MEDIUM4.68 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.176.1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-93817 | MEDIUM4.68 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.176.1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-73073 | MEDIUM4.68 | vim-minimal 2:8.0.1763-31.el8_10 fixed in 2:8.0.1763-32.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-73076 | MEDIUM4.68 | vim-minimal 2:8.0.1763-31.el8_10 fixed in 2:8.0.1763-31.el8_10.7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-80590 | MEDIUM4.62 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.177.1.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-103111 | MEDIUM4.56 | pcre2 10.32-3.el8_6 fixed in 10.32-4.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93990 | MEDIUM4.5 | expat 2.5.0-2.el8_10 fixed in 2.5.0-4.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-88806 | MEDIUM4.5 | libX11 1.6.8-9.el8_10 fixed in 1.6.8-10.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88806 | MEDIUM4.5 | libX11-common 1.6.8-9.el8_10 fixed in 1.6.8-10.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-97417 | MEDIUM4.5 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78669 | MEDIUM4.5 | golang.org/x/net v0.59.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78659 | MEDIUM4.5 | golang.org/x/net v0.59.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78660 | MEDIUM4.5 | golang.org/x/net v0.59.0 fixed in 0.60.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-89157 | MEDIUM4.44 | pcre2 10.32-3.el8_6 fixed in 10.32-4.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19553 | MEDIUM4.44 | python3-libs 3.6.8-78.el8_10.alma.1 fixed in 3.6.8-79.el8_10.alma.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86143 | MEDIUM4.38 | libxml2 2.9.7-21.el8_10.7 fixed in 2.9.7-21.el8_10.9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-68278 | MEDIUM4.38 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.173.1.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-93262 | MEDIUM4.38 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.174.1.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-73072 | MEDIUM4.38 | vim-minimal 2:8.0.1763-31.el8_10 fixed in 2:8.0.1763-31.el8_10.7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64572 | MEDIUM4.26 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.177.1.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-68409 | MEDIUM4.26 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.173.1.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-89481 | MEDIUM4.26 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45861 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46319 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52935 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.176.1.el8_10 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53049 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53230 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53270 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63920 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.173.1.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63992 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63994 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64102 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.170.1.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64114 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.177.1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64115 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.172.1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64266 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.177.1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-68202 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.177.1.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-68236 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.173.1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-68377 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.174.1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-68432 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-72262 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.174.1.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-74569 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-74641 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.174.1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-80887 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.173.1.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-80921 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-89479 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.176.1.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-89530 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.172.1.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-89777 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.177.1.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89811 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.173.1.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90227 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-98320 | MEDIUM4.2 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.176.1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | glibc 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | glibc-common 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | glibc-langpack-en 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | glibc-minimal-langpack 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40468 | MEDIUM4.14 | gawk 4.2.1-4.el8 fixed in 4.2.1-5.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | MEDIUM4.14 | glib2 2.56.4-177.el8_10 fixed in 2.56.4-178.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6653 | MEDIUM4.14 | libxml2 2.9.7-21.el8_10.7 fixed in 2.9.7-21.el8_10.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | MEDIUM4.14 | openssl 1:1.1.1k-17.el8_6 fixed in 1:1.1.1k-18.el8_6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.14 | openssl-libs 1:1.1.1k-17.el8_6 fixed in 1:1.1.1k-18.el8_6 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | MEDIUM4.14 | openssl-libs 1:1.1.1k-17.el8_6 fixed in 1:1.1.1k-18.el8_6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-45856 | MEDIUM4.14 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63794 | MEDIUM4.14 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-72099 | MEDIUM4.14 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.170.1.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-19953 | MEDIUM4.14 | perl-URI 1.73-3.el8 fixed in 1.73-4.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53196 | MEDIUM4.08 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.176.1.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-89158 | LOW3.9 | pcre2 10.32-3.el8_6 fixed in 10.32-4.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5278 | LOW3.74 | coreutils-single 8.30-20.el8_10 fixed in 8.30-21.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-74515 | LOW3.66 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.179.1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | LOW3.54 | glibc 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.43 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | LOW3.54 | glibc-common 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.43 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | LOW3.54 | glibc-langpack-en 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.43 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | LOW3.54 | glibc-minimal-langpack 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.43 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50756 | LOW3.54 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54048 | LOW3.54 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40242 | LOW3.54 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-97032 | LOW3.54 | golang.org/x/net v0.59.0 fixed in 0.60.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-23105 | LOW3.3 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52972 | LOW3.3 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-93228 | LOW3.3 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.174.1.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-68299 | LOW3.3 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.170.1.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5704 | LOW3.3 | tar 2:1.30-11.el8_10 fixed in 2:1.30-13.el8_10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-55892 | LOW3.3 | vim-minimal 2:8.0.1763-31.el8_10 fixed in 2:8.0.1763-31.el8_10.7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-59857 | LOW3.3 | vim-minimal 2:8.0.1763-31.el8_10 fixed in 2:8.0.1763-31.el8_10.7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | LOW3.18 | golang.org/x/net v0.59.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-74516 | LOW3.17 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-74588 | LOW3.17 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.176.1.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-74669 | LOW3.17 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-74705 | LOW3.17 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.174.1.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-73078 | LOW3.17 | vim-minimal 2:8.0.1763-31.el8_10 fixed in 2:8.0.1763-31.el8_10.7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-39994 | LOW2.96 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.171.1.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19445 | LOW2.92 | platform-python 3.6.8-78.el8_10.alma.1 fixed in 3.6.8-79.el8_10.alma.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-45582 | LOW2.86 | tar 2:1.30-11.el8_10 fixed in 2:1.30-13.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.82 | gzip 1.9-13.el8_5 fixed in 1.9-15.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-72329 | LOW2.82 | perf 4.18.0-553.169.1.el8_10 fixed in 4.18.0-553.170.1.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19553 | LOW2.66 | platform-python 3.6.8-78.el8_10.alma.1 fixed in 3.6.8-79.el8_10.alma.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-18477 | LOW2.64 | tar 2:1.30-11.el8_10 fixed in 2:1.30-13.el8_10 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.64 | tar 2:1.30-11.el8_10 fixed in 2:1.30-13.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28420 | LOW2.64 | vim-minimal 2:8.0.1763-31.el8_10 fixed in 2:8.0.1763-31.el8_10.7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13732 | LOW2.52 | gdb 8.2-20.el8 fixed in 8.2-20.1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-13732 | LOW2.52 | gdb-headless 8.2-20.el8 fixed in 8.2-20.1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-40467 | LOW2.48 | gawk 4.2.1-4.el8 fixed in 4.2.1-5.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW2.48 | gzip 1.9-13.el8_5 fixed in 1.9-15.el8_10 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63072 | LOW2.48 | openssl 1:1.1.1k-17.el8_6 fixed in 1:1.1.1k-18.el8_6 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-12345 | LOW2.27 | platform-python 3.6.8-78.el8_10.alma.1 fixed in 3.6.8-79.el8_10.alma.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12345 | LOW2.27 | python3-libs 3.6.8-78.el8_10.alma.1 fixed in 3.6.8-79.el8_10.alma.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-78667 | NONE0 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78669 | NONE0 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97031 | NONE0 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-114406 | NONE0 | ca-certificates 2025.2.80_v9.0.304-80.2.el8_10 fixed in 2026.2.92_v9.0.319-81.3.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-111943 | NONE0 | stdlib v1.27.0 fixed in 1.26.10, 1.27.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56866 | NONE0 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-94439 | NONE0 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-94448 | NONE0 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97032 | NONE0 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78663 | NONE0 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56857 | NONE0 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.6% 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.
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.