Last scanned:
This image is safe for production use. The scan reported 115 exposed-surface findings and 34 post-exploit-only findings, so these vulnerabilities exist, but none are rated high severity and none are known to be actively exploited. The highest exposed-surface severity is 5.44, and the post-exploit findings top out at 3.21, which keeps the overall risk low for this deployment. The image comes from a verified publisher and is pinned by digest, which supports its integrity. Routine patching and rescanning as new advisories are published remain good hygiene.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-114406 | MEDIUM5.44 | ca-certificates 2025.2.80_v9.0.305-91.el9 fixed in 2026.2.92_v9.0.319-90.3.el9_8 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-8674 | MEDIUM5.3 | glibc 2.34-283.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | glibc-common 2.34-283.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | glibc-langpack-en 2.34-283.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | glibc-minimal-langpack 2.34-283.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54875 | MEDIUM4.7 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | glibc 2.34-283.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | glibc-common 2.34-283.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | glibc-langpack-en 2.34-283.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | glibc-minimal-langpack 2.34-283.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM4.14 | cyrus-sasl-lib 2.1.27-22.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.14 | glibc 2.34-283.el9_8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.14 | glibc 2.34-283.el9_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.14 | glibc-common 2.34-283.el9_8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.14 | glibc-common 2.34-283.el9_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.14 | glibc-langpack-en 2.34-283.el9_8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.14 | glibc-langpack-en 2.34-283.el9_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.14 | glibc-minimal-langpack 2.34-283.el9_8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.14 | glibc-minimal-langpack 2.34-283.el9_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.14 | libgcc 11.5.0-14.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.14 | libgcc 11.5.0-14.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.14 | libstdc++ 11.5.0-14.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.14 | libstdc++ 11.5.0-14.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6429 | LOW3.9 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | krb5-libs 1.21.1-10.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6429 | LOW3.9 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41996 | LOW3.9 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28387 | LOW3.9 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | LOW3.9 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | LOW3.9 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | LOW3.9 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42765 | LOW3.9 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | LOW3.9 | pcre2 10.40-7.el9_8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41409 | LOW3.9 | pcre2-syntax 10.40-7.el9_8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-27171 | LOW3.9 | zlib 1.2.11-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5958 | LOW3.78 | sed 4.8-10.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | glibc 2.34-283.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | glibc-common 2.34-283.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | glibc-langpack-en 2.34-283.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | glibc-minimal-langpack 2.34-283.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.7 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35191 | LOW3.7 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-56391 | LOW3.66 | coreutils-single 8.32-41.el9_8.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-72897 | LOW3.54 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | LOW3.54 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | LOW3.54 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-72897 | LOW3.54 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | LOW3.54 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | LOW3.54 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4156 | LOW3.31 | gawk-all-langpacks 5.1.0-6.el9_8.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | LOW3.31 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-48386 | LOW3.21 | git-core 2.52.0-1.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW3.18 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6253 | LOW3.18 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7168 | LOW3.18 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4873 | LOW3.18 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6253 | LOW3.18 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7168 | LOW3.18 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42772 | LOW3.18 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54873 | LOW3.18 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | LOW3.18 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | LOW3.18 | openssl 1:3.5.8-2.el9_8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-84784 | LOW3.18 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42772 | LOW3.18 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54873 | LOW3.18 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | LOW3.18 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | LOW3.18 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-84784 | LOW3.18 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-9232 | LOW3.1 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW3 | krb5-libs 1.21.1-10.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | krb5-libs 1.21.1-10.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | LOW2.88 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | LOW2.88 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54875 | LOW2.82 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-7264 | LOW2.69 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 20.2% High Exploitation Risk | Directly Exposed |
| CVE-2024-7264 | LOW2.69 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 20.2% High Exploitation Risk | Directly Exposed |
| CVE-2026-18739 | LOW2.5 | popt 1.18-8.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18743 | LOW2.5 | popt 1.18-8.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5773 | LOW2.48 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW2.48 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW2.48 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW2.48 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9546 | LOW2.48 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW2.48 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW2.48 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW2.48 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW2.48 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9546 | LOW2.48 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-13034 | LOW2.45 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-13034 | LOW2.45 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW2.34 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3784 | LOW2.34 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW2.34 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW2.34 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3784 | LOW2.34 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW2.34 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-11053 | LOW2.34 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-9681 | LOW2.34 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14524 | LOW2.34 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | LOW2.34 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | LOW2.34 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6276 | LOW2.34 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86409 | LOW2.34 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW2.34 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW2.34 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-11053 | LOW2.34 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-9681 | LOW2.34 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14524 | LOW2.34 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | LOW2.34 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | LOW2.34 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6276 | LOW2.34 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86409 | LOW2.34 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW2.34 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW2.34 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | LOW2.34 | ncurses-base 6.2-12.20210508.el9 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-50495 | LOW2.34 | ncurses-libs 6.2-12.20210508.el9 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2024-41996 | LOW2.34 | openssl 1:3.5.8-2.el9_8 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28387 | LOW2.34 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-28388 | LOW2.34 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-28389 | LOW2.34 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | LOW2.34 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42765 | LOW2.34 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW2.22 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW2.22 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-35191 | LOW2.22 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-18839 | LOW2.2 | popt 1.18-8.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | LOW2.12 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-75805 | LOW2.12 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-46195 | LOW1.99 | libgcc 11.5.0-14.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | libgcc 11.5.0-14.el9 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | LOW1.99 | libstdc++ 11.5.0-14.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | libstdc++ 11.5.0-14.el9 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | LOW1.99 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-94266 | LOW1.98 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94266 | LOW1.98 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-82209 | LOW1.86 | curl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-82209 | LOW1.86 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-9232 | LOW1.86 | openssl 1:3.5.8-2.el9_8 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-48924 | NONE0 | commons-lang:commons-lang 2.6 No fix yet | 2.6% Low-Moderate Risk | 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.