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 main inherited risk is CVE-2026-16118 in glib2, a heap-based buffer overflow in xdgmime that can cause an application crash or memory corruption when an application parses an attacker-controlled MIME magic file. There are 20 exposed-surface findings and 47 post-exploit findings, but only one exposed finding is 6.0+ and none reach 7.0, so the risk is limited rather than critical. That finding only applies where MIME type detection processes an attacker-controlled XDG MIME magic file; otherwise the exposure is not exercised. Remediate glib2 in downstream images and avoid parsing untrusted MIME magic files. 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.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-16118 | MEDIUM6.03 | glib2 2.80.4-12.el10_2.21 fixed in 2.80.4-12.el10_2.22 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | openssl-libs 1:3.5.5-6.el10_2.alma.1 fixed in 1:3.5.8-1.el10_2.alma.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-19499 | MEDIUM5.78 | glibc 2.39-128.el10_2.alma.1 fixed in 2.39-142.el10_2.alma.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM5.78 | glibc-common 2.39-128.el10_2.alma.1 fixed in 2.39-142.el10_2.alma.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM5.78 | glibc-minimal-langpack 2.39-128.el10_2.alma.1 fixed in 2.39-142.el10_2.alma.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-89158 | MEDIUM5.52 | pcre2 10.44-1.el10.3 fixed in 10.44-1.5.el10_2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89160 | MEDIUM5.52 | pcre2 10.44-1.el10.3 fixed in 10.44-1.5.el10_2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | glibc 2.39-128.el10_2.alma.1 fixed in 2.39-142.el10_2.alma.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | glibc-common 2.39-128.el10_2.alma.1 fixed in 2.39-142.el10_2.alma.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | glibc-minimal-langpack 2.39-128.el10_2.alma.1 fixed in 2.39-142.el10_2.alma.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89156 | MEDIUM5.02 | pcre2 10.44-1.el10.3 fixed in 10.44-1.5.el10_2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | glibc 2.39-128.el10_2.alma.1 fixed in 2.39-142.el10_2.alma.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | glibc-common 2.39-128.el10_2.alma.1 fixed in 2.39-142.el10_2.alma.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | glibc-minimal-langpack 2.39-128.el10_2.alma.1 fixed in 2.39-142.el10_2.alma.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | xz-libs 1:5.6.2-4.el10_0 fixed in 1:5.6.2-4.el10_2.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | glibc 2.39-128.el10_2.alma.1 fixed in 2.39-142.el10_2.alma.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | glibc-common 2.39-128.el10_2.alma.1 fixed in 2.39-142.el10_2.alma.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | glibc-minimal-langpack 2.39-128.el10_2.alma.1 fixed in 2.39-142.el10_2.alma.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5545 | LOW3.31 | curl 8.12.1-4.el10_2.4 fixed in 8.12.1-4.el10_2.7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl 8.12.1-4.el10_2.4 fixed in 8.12.1-4.el10_2.7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 8.12.1-4.el10_2.4 fixed in 8.12.1-4.el10_2.6 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | libcurl-minimal 8.12.1-4.el10_2.4 fixed in 8.12.1-4.el10_2.6 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl-minimal 8.12.1-4.el10_2.4 fixed in 8.12.1-4.el10_2.7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl-minimal 8.12.1-4.el10_2.4 fixed in 8.12.1-4.el10_2.7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl-minimal 8.12.1-4.el10_2.4 fixed in 8.12.1-4.el10_2.6 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-15028 | LOW3.31 | libarchive 3.7.7-10.el10_2 fixed in 3.7.7-11.el10_2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56391 | LOW3.11 | coreutils-single 9.5-8.el10_2 fixed in 9.5-8.el10_2.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW3.11 | coreutils-single 9.5-8.el10_2 fixed in 9.5-8.el10_2.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-40468 | LOW2.78 | gawk 5.3.0-6.el10 fixed in 5.3.0-6.el10_2.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-14457 | LOW2.7 | openssl-libs 1:3.5.5-6.el10_2.alma.1 fixed in 1:3.5.8-1.el10_2.alma.1 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-18798 | LOW2.7 | openssl-libs 1:3.5.5-6.el10_2.alma.1 fixed in 1:3.5.8-1.el10_2.alma.1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63076 | LOW2.7 | openssl-libs 1:3.5.5-6.el10_2.alma.1 fixed in 1:3.5.8-1.el10_2.alma.1 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl 8.12.1-4.el10_2.4 fixed in 8.12.1-4.el10_2.7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl 8.12.1-4.el10_2.4 fixed in 8.12.1-4.el10_2.7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl-minimal 8.12.1-4.el10_2.4 fixed in 8.12.1-4.el10_2.7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl-minimal 8.12.1-4.el10_2.4 fixed in 8.12.1-4.el10_2.7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-74860 | LOW2.6 | libxml2 2.12.5-10.el10_2.3 fixed in 2.12.5-10.el10_2.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-86145 | LOW2.51 | pcre2 10.44-1.el10.3 fixed in 10.44-1.5.el10_2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.48 | curl 8.12.1-4.el10_2.4 fixed in 8.12.1-4.el10_2.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.48 | libcurl-minimal 8.12.1-4.el10_2.4 fixed in 8.12.1-4.el10_2.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-16517 | LOW2.46 | libarchive 3.7.7-10.el10_2 fixed in 3.7.7-11.el10_2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-8926 | LOW2.45 | curl 8.12.1-4.el10_2.4 fixed in 8.12.1-4.el10_2.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | libcurl-minimal 8.12.1-4.el10_2.4 fixed in 8.12.1-4.el10_2.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | curl 8.12.1-4.el10_2.4 fixed in 8.12.1-4.el10_2.7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl-minimal 8.12.1-4.el10_2.4 fixed in 8.12.1-4.el10_2.7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-86138 | LOW2.39 | libxml2 2.12.5-10.el10_2.3 fixed in 2.12.5-10.el10_2.4 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86140 | LOW2.39 | libxml2 2.12.5-10.el10_2.3 fixed in 2.12.5-10.el10_2.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86142 | LOW2.39 | libxml2 2.12.5-10.el10_2.3 fixed in 2.12.5-10.el10_2.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86144 | LOW2.39 | libxml2 2.12.5-10.el10_2.3 fixed in 2.12.5-10.el10_2.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-89161 | LOW2.39 | pcre2 10.44-1.el10.3 fixed in 10.44-1.5.el10_2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-103111 | LOW2.33 | pcre2 10.44-1.el10.3 fixed in 10.44-1.5.el10_2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW2.29 | curl 8.12.1-4.el10_2.4 fixed in 8.12.1-4.el10_2.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9079 | LOW2.29 | curl 8.12.1-4.el10_2.4 fixed in 8.12.1-4.el10_2.6 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-40467 | LOW2.29 | gawk 5.3.0-6.el10 fixed in 5.3.0-6.el10_2.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-40553 | LOW2.29 | gawk 5.3.0-6.el10 fixed in 5.3.0-6.el10_2.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW2.29 | libcurl-minimal 8.12.1-4.el10_2.4 fixed in 8.12.1-4.el10_2.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9079 | LOW2.29 | libcurl-minimal 8.12.1-4.el10_2.4 fixed in 8.12.1-4.el10_2.6 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-14456 | LOW2.29 | openssl-libs 1:3.5.5-6.el10_2.alma.1 fixed in 1:3.5.8-1.el10_2.alma.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-54874 | LOW2.29 | openssl-libs 1:3.5.5-6.el10_2.alma.1 fixed in 1:3.5.8-1.el10_2.alma.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63074 | LOW2.29 | openssl-libs 1:3.5.5-6.el10_2.alma.1 fixed in 1:3.5.8-1.el10_2.alma.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63075 | LOW2.29 | openssl-libs 1:3.5.5-6.el10_2.alma.1 fixed in 1:3.5.8-1.el10_2.alma.1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-63072 | LOW2.29 | openssl-libs 1:3.5.5-6.el10_2.alma.1 fixed in 1:3.5.8-1.el10_2.alma.1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-84782 | LOW2.26 | openssl-libs 1:3.5.5-6.el10_2.alma.1 fixed in 1:3.5.8-2.el10_2.alma.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-89157 | LOW2.26 | pcre2 10.44-1.el10.3 fixed in 10.44-1.5.el10_2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42784 | LOW2.26 | rpm-sequoia 1.10.1.1-2.el10 fixed in 1.10.2.1-1.el10_2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-86143 | LOW2.23 | libxml2 2.12.5-10.el10_2.3 fixed in 2.12.5-10.el10_2.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW1.99 | curl 8.12.1-4.el10_2.4 fixed in 8.12.1-4.el10_2.6 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-86145 | NONE0 | pcre2-syntax 10.44-1.el10.3 fixed in 10.44-1.5.el10_2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89161 | NONE0 | pcre2-syntax 10.44-1.el10.3 fixed in 10.44-1.5.el10_2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-103111 | NONE0 | pcre2-syntax 10.44-1.el10.3 fixed in 10.44-1.5.el10_2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89157 | NONE0 | pcre2-syntax 10.44-1.el10.3 fixed in 10.44-1.5.el10_2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89158 | NONE0 | pcre2-syntax 10.44-1.el10.3 fixed in 10.44-1.5.el10_2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89160 | NONE0 | pcre2-syntax 10.44-1.el10.3 fixed in 10.44-1.5.el10_2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89156 | NONE0 | pcre2-syntax 10.44-1.el10.3 fixed in 10.44-1.5.el10_2 | 0.3% 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.