Last scanned:
This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker could cause denial of service via memory exhaustion by sending crafted HTTP requests with many unique query parameters (CVE-2025-61726), or trigger CPU/resource exhaustion via crafted TLS certificates (CVE-2025-61729). Note that CVE-2025-68121 requires non-default TLS config mutation, reducing its immediate impact. Remediation requires upgrading the base image to include patched Go standard library and system packages.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2025-61726 | HIGH7.5 | stdlib v1.23.12 fixed in 1.24.12, 1.25.6 | 1.9% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2025-68121 | MEDIUM6.8 | stdlib v1.23.12 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-58011 | MEDIUM6.38 | glib2 2.68.4-19.el9_8.2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | glib2 2.68.4-19.el9_8.2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-14164 | MEDIUM6.38 | libarchive 3.5.3-9.el9_7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41989 | MEDIUM6.38 | libgcrypt 1.10.0-11.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6732 | MEDIUM6.38 | libxml2 2.9.13-14.el9_8.2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61729 | MEDIUM6.38 | stdlib v1.23.12 fixed in 1.24.11, 1.25.5 | 0.4% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-25679 | MEDIUM6.38 | stdlib v1.23.12 fixed in 1.25.8, 1.26.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-27145 | MEDIUM6.38 | stdlib v1.23.12 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32280 | MEDIUM6.38 | stdlib v1.23.12 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32281 | MEDIUM6.38 | stdlib v1.23.12 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32283 | MEDIUM6.38 | stdlib v1.23.12 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33811 | MEDIUM6.38 | stdlib v1.23.12 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | stdlib v1.23.12 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39820 | MEDIUM6.38 | stdlib v1.23.12 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39836 | MEDIUM6.38 | stdlib v1.23.12 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42499 | MEDIUM6.38 | stdlib v1.23.12 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42504 | MEDIUM6.38 | stdlib v1.23.12 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | MEDIUM6.03 | glib2 2.68.4-19.el9_8.2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-44604 | MEDIUM5.95 | rpm-libs 4.16.1.3-40.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-41996 | MEDIUM5.9 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | openldap 2.6.8-4.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | systemd-libs 252-67.el9_8.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5915 | MEDIUM5.61 | libarchive 3.5.3-9.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5918 | MEDIUM5.61 | libarchive 3.5.3-9.el9_7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4426 | MEDIUM5.52 | libarchive 3.5.3-9.el9_7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9149 | MEDIUM5.52 | libsolv 0.7.24-6.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9150 | MEDIUM5.52 | libsolv 0.7.24-6.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-45322 | MEDIUM5.52 | libxml2 2.9.13-14.el9_8.2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-2673 | MEDIUM5.52 | openssl-fips-provider 3.0.7-11.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2673 | MEDIUM5.52 | openssl-fips-provider-so 3.0.7-11.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2673 | MEDIUM5.52 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61727 | MEDIUM5.52 | stdlib v1.23.12 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39825 | MEDIUM5.52 | stdlib v1.23.12 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44605 | MEDIUM5.5 | rpm-libs 4.16.1.3-40.el9 No fix yet | — | Directly Exposed |
| CVE-2026-32282 | MEDIUM5.44 | stdlib v1.23.12 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM5.35 | libattr 2.5.1-3.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1757 | MEDIUM5.27 | libxml2 2.9.13-14.el9_8.2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | p11-kit 0.26.2-1.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | p11-kit-trust 0.26.2-1.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32289 | MEDIUM5.18 | stdlib v1.23.12 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2 2.9.13-14.el9_8.2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-6653 | MEDIUM5 | libxml2 2.9.13-14.el9_8.2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | MEDIUM5 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5916 | MEDIUM4.76 | libarchive 3.5.3-9.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-60753 | MEDIUM4.67 | libarchive 3.5.3-9.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5745 | MEDIUM4.67 | libarchive 3.5.3-9.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1632 | MEDIUM4.67 | libarchive 3.5.3-9.el9_7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libgcc 11.5.0-14.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc 11.5.0-14.el9 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libstdc++ 11.5.0-14.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++ 11.5.0-14.el9 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-0232 | MEDIUM4.67 | sqlite-libs 3.34.1-10.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib 1.2.11-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32288 | MEDIUM4.67 | stdlib v1.23.12 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1489 | MEDIUM4.59 | glib2 2.68.4-19.el9_8.2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58055 | MEDIUM4.59 | libnghttp2 1.43.0-6.el9_8.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27142 | MEDIUM4.59 | stdlib v1.23.12 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39823 | MEDIUM4.59 | stdlib v1.23.12 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39826 | MEDIUM4.59 | stdlib v1.23.12 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-27113 | MEDIUM4.5 | libxml2 2.9.13-14.el9_8.2 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28388 | MEDIUM4.5 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28389 | MEDIUM4.5 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-15588 | MEDIUM4.5 | glib2 2.68.4-19.el9_8.2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-30571 | MEDIUM4.5 | libarchive 3.5.3-9.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libblkid 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libsmartcols 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libuuid 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | xz-libs 5.2.5-8.el9_0 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-47912 | MEDIUM4.5 | stdlib v1.23.12 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58185 | MEDIUM4.5 | stdlib v1.23.12 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58187 | MEDIUM4.5 | stdlib v1.23.12 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58188 | MEDIUM4.5 | stdlib v1.23.12 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58189 | MEDIUM4.5 | stdlib v1.23.12 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61723 | MEDIUM4.5 | stdlib v1.23.12 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61724 | MEDIUM4.5 | stdlib v1.23.12 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61725 | MEDIUM4.5 | stdlib v1.23.12 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61730 | MEDIUM4.5 | stdlib v1.23.12 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42505 | MEDIUM4.5 | stdlib v1.23.12 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42507 | MEDIUM4.5 | stdlib v1.23.12 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58186 | MEDIUM4.5 | stdlib v1.23.12 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | MEDIUM4.39 | glib2 2.68.4-19.el9_8.2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM4.25 | bzip2-libs 1.0.8-11.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | krb5-libs 1.21.1-10.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5917 | MEDIUM4.25 | libarchive 3.5.3-9.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM4.18 | glib2 2.68.4-19.el9_8.2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM4.18 | glib2 2.68.4-19.el9_8.2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM4.18 | glib2 2.68.4-19.el9_8.2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM4.13 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-9681 | LOW3.9 | libcurl-minimal 7.76.1-40.el9 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-32636 | LOW3.83 | glib2 2.68.4-19.el9_8.2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-58183 | LOW3.83 | stdlib v1.23.12 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61728 | LOW3.83 | stdlib v1.23.12 fixed in 1.24.12, 1.25.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11352 | LOW3.82 | curl-minimal 7.76.1-40.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11586 | LOW3.82 | curl-minimal 7.76.1-40.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | curl-minimal 7.76.1-40.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl-minimal 7.76.1-40.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-11352 | LOW3.82 | libcurl-minimal 7.76.1-40.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11586 | LOW3.82 | libcurl-minimal 7.76.1-40.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl-minimal 7.76.1-40.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl-minimal 7.76.1-40.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59871 | LOW3.82 | tar 2:1.34-11.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | curl-minimal 7.76.1-40.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl-minimal 7.76.1-40.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-4156 | LOW3.62 | gawk 5.1.0-6.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 2:1.34-11.el9 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-44604 | LOW3.57 | rpm 4.16.1.3-40.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1484 | LOW3.57 | glib2 2.68.4-19.el9_8.2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-11053 | LOW3.54 | curl-minimal 7.76.1-40.el9 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-11053 | LOW3.54 | libcurl-minimal 7.76.1-40.el9 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | curl-minimal 7.76.1-40.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | curl-minimal 7.76.1-40.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | libcurl-minimal 7.76.1-40.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl-minimal 7.76.1-40.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | curl-minimal 7.76.1-40.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | curl-minimal 7.76.1-40.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl-minimal 7.76.1-40.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl-minimal 7.76.1-40.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl-minimal 7.76.1-40.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl-minimal 7.76.1-40.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | libcurl-minimal 7.76.1-40.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl-minimal 7.76.1-40.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl-minimal 7.76.1-40.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl-minimal 7.76.1-40.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl-minimal 7.76.1-40.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl-minimal 7.76.1-40.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-33056 | LOW3.31 | tar 2:1.34-11.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-15028 | LOW3.31 | libarchive 3.5.3-9.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44605 | LOW3.3 | rpm 4.16.1.3-40.el9 No fix yet | — | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.8-10.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-3360 | LOW3.15 | glib2 2.68.4-19.el9_8.2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-7039 | LOW3.15 | glib2 2.68.4-19.el9_8.2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0988 | LOW3.15 | glib2 2.68.4-19.el9_8.2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.15 | libxml2 2.9.13-14.el9_8.2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56391 | LOW3.11 | coreutils-single 8.32-41.el9_8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-9232 | LOW3.1 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-3783 | LOW2.91 | curl-minimal 7.76.1-40.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl-minimal 7.76.1-40.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-24883 | LOW2.8 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53655 | LOW2.8 | tar 2:1.34-11.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 2:1.34-11.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41990 | LOW2.8 | libgcrypt 1.10.0-11.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | sqlite-libs 3.34.1-10.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | LOW2.7 | pcre2 10.40-6.el9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-41409 | LOW2.7 | pcre2-syntax 10.40-6.el9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | curl-minimal 7.76.1-40.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl-minimal 7.76.1-40.el9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl-minimal 7.76.1-40.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl-minimal 7.76.1-40.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl-minimal 7.76.1-40.el9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl-minimal 7.76.1-40.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-59875 | LOW2.7 | tar 2:1.34-11.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34743 | LOW2.7 | xz 5.2.5-8.el9_0 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-7264 | LOW2.69 | curl-minimal 7.76.1-40.el9 No fix yet | 17.3% High Exploitation Risk | Post-Exploit |
| CVE-2024-7264 | LOW2.69 | libcurl-minimal 7.76.1-40.el9 No fix yet | 17.3% High Exploitation Risk | Post-Exploit |
| CVE-2026-8286 | LOW2.48 | curl-minimal 7.76.1-40.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8925 | LOW2.48 | curl-minimal 7.76.1-40.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | LOW2.48 | curl-minimal 7.76.1-40.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | LOW2.48 | libcurl-minimal 7.76.1-40.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8925 | LOW2.48 | libcurl-minimal 7.76.1-40.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | LOW2.48 | libcurl-minimal 7.76.1-40.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-16517 | LOW2.46 | libarchive 3.5.3-9.el9_7 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0992 | LOW2.46 | libxml2 2.9.13-14.el9_8.2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | LOW2.45 | curl-minimal 7.76.1-40.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | curl-minimal 7.76.1-40.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl-minimal 7.76.1-40.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | libcurl-minimal 7.76.1-40.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl-minimal 7.76.1-40.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.12-1.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl-minimal 7.76.1-40.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-64118 | LOW2.4 | tar 2:1.34-11.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-11979 | LOW2.39 | libxml2 2.9.13-14.el9_8.2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-39822 | LOW2.39 | stdlib v1.23.12 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1485 | LOW2.38 | glib2 2.68.4-19.el9_8.2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-9681 | LOW2.34 | curl-minimal 7.76.1-40.el9 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-56392 | LOW2.24 | coreutils-single 8.32-41.el9_8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27139 | LOW2.12 | stdlib v1.23.12 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-39804 | LOW1.68 | tar 2:1.34-11.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-50495 | NONE0 | ncurses-base 6.2-12.20210508.el9 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-libs 6.2-12.20210508.el9 No fix yet | 1.0% 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.