Last scanned:
This base/runtime image is a clean foundation for building production images. It carries a modest number of low-severity findings (17 exposed and 21 post-exploit), with a maximum exposed severity of 5.5 and a post-exploit maximum of 2.92. No high-severity or exploitable vulnerabilities are present in the supplied findin findings, so images built on top inherit minimal additional risk. The image's official status and pinned digest further support its safe use as a base. 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-2024-34459 | MEDIUM5.5 | libxml2 2.12.5-10.el10 fixed in 2.12.5-10.el10_2.1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl 2.3.2-4.el10 fixed in 2.4.0-1.el10_2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | openssl-libs 1:3.5.5-2.el10_2.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | openssl-libs 1:3.5.5-2.el10_2.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | openssl-libs 1:3.5.5-2.el10_2.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | openssl-libs 1:3.5.5-2.el10_2.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-libs 1:3.5.5-2.el10_2.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | openssl-libs 1:3.5.5-2.el10_2.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | openssl-libs 1:3.5.5-2.el10_2.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc 2.39-124.el10_2.alma.1 fixed in 2.39-126.el10_2.alma.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc 2.39-124.el10_2.alma.1 fixed in 2.39-128.el10_2.alma.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-common 2.39-124.el10_2.alma.1 fixed in 2.39-126.el10_2.alma.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-common 2.39-124.el10_2.alma.1 fixed in 2.39-128.el10_2.alma.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-minimal-langpack 2.39-124.el10_2.alma.1 fixed in 2.39-126.el10_2.alma.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-minimal-langpack 2.39-124.el10_2.alma.1 fixed in 2.39-128.el10_2.alma.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | openssl-libs 1:3.5.5-2.el10_2.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45447 | LOW2.92 | openssl-libs 1:3.5.5-2.el10_2.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-58016 | LOW2.78 | glib2 2.80.4-12.el10_2.13 fixed in 2.80.4-12.el10_2.14 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | openssl-libs 1:3.5.5-2.el10_2.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-34183 | LOW2.7 | openssl-libs 1:3.5.5-2.el10_2.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28390 | LOW2.7 | openssl-libs 1:3.5.5-2.el10_2.alma.1 fixed in 1:3.5.5-3.el10_2.alma.1 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-48864 | LOW2.39 | libsolv 0.7.33-2.el10.alma.2 fixed in 0.7.33-5.el10_2.alma.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW2.26 | openssl-libs 1:3.5.5-2.el10_2.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils-single 9.5-7.el10 fixed in 9.5-8.el10_2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-54369 | LOW2.17 | libacl 2.3.2-4.el10 fixed in 2.4.0-1.el10_2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13151 | LOW2.12 | libtasn1 4.20.0-1.el10 fixed in 4.20.0-5.el10_2 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42764 | LOW2.12 | openssl-libs 1:3.5.5-2.el10_2.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-6170 | LOW2.12 | libxml2 2.12.5-10.el10 fixed in 2.12.5-10.el10_2.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | LOW1.99 | glibc 2.39-124.el10_2.alma.1 fixed in 2.39-128.el10_2.alma.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW1.99 | glibc-common 2.39-124.el10_2.alma.1 fixed in 2.39-128.el10_2.alma.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW1.99 | glibc-minimal-langpack 2.39-124.el10_2.alma.1 fixed in 2.39-128.el10_2.alma.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9149 | LOW1.99 | libsolv 0.7.33-2.el10.alma.2 fixed in 0.7.33-5.el10_2.alma.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9150 | LOW1.99 | libsolv 0.7.33-2.el10.alma.2 fixed in 0.7.33-5.el10_2.alma.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW1.81 | glibc 2.39-124.el10_2.alma.1 fixed in 2.39-128.el10_2.alma.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW1.81 | glibc-common 2.39-124.el10_2.alma.1 fixed in 2.39-128.el10_2.alma.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW1.81 | glibc-minimal-langpack 2.39-124.el10_2.alma.1 fixed in 2.39-128.el10_2.alma.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42769 | LOW1.81 | openssl-libs 1:3.5.5-2.el10_2.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW1.81 | openssl-libs 1:3.5.5-2.el10_2.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 0.5% Theoretical Threat | Post-Exploit |
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.