Last scanned:
This image is safe for production use. While the image contains 48 exposed and 57 post-exploit-only vulnerabilities, none exceed the low-severity threshold (max exposed severity 5.52, max post-exploit severity 3.98). These findings are not exploitable to a significant degree and do not present practical risks for normal deployment. The image is officially endorsed as reliable and packed with a strong community reputation.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-6238 | MEDIUM5.52 | glibc-common 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc-langpack-en 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc-minimal-langpack 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-34459 | MEDIUM5.5 | libxml2 2.9.7-21.el8_10.4 fixed in 2.9.7-21.el8_10.5 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl 2.2.53-3.el8 fixed in 2.4.0-1.el8_10 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-47063 | MEDIUM5.1 | java-17-openjdk 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-47063 | MEDIUM5.1 | java-17-openjdk-headless 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-5435 | MEDIUM5.02 | glibc 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-common 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-langpack-en 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-minimal-langpack 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46968 | MEDIUM5.02 | java-17-openjdk 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46968 | MEDIUM5.02 | java-17-openjdk-devel 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46968 | MEDIUM5.02 | java-17-openjdk-headless 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35568 | MEDIUM4.84 | io.modelcontextprotocol.sdk:mcp-core 0.18.2 fixed in 1.0.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46917 | MEDIUM4.5 | java-17-openjdk 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47021 | MEDIUM4.5 | java-17-openjdk 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47027 | MEDIUM4.5 | java-17-openjdk 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46917 | MEDIUM4.5 | java-17-openjdk-devel 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47021 | MEDIUM4.5 | java-17-openjdk-devel 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47027 | MEDIUM4.5 | java-17-openjdk-devel 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46917 | MEDIUM4.5 | java-17-openjdk-headless 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47021 | MEDIUM4.5 | java-17-openjdk-headless 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47027 | MEDIUM4.5 | java-17-openjdk-headless 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54515 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.21.4 fixed in 3.1.4, 2.18.9, 2.21.5, 2.22.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-60147 | MEDIUM4.42 | java-17-openjdk 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-60147 | MEDIUM4.42 | java-17-openjdk-headless 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-5450 | MEDIUM4.25 | glibc 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-common 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-common 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-langpack-en 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-langpack-en 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-minimal-langpack 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-minimal-langpack 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-71089 | LOW3.98 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.143.1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23216 | LOW3.98 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.139.1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31488 | LOW3.98 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.136.1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43499 | LOW3.98 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.143.1.el8_10 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-45984 | LOW3.98 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.139.1.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46189 | LOW3.98 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.139.1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53059 | LOW3.98 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.147.1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53359 | LOW3.98 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.143.1.el8_10 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-53071 | LOW3.82 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.146.1.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41411 | LOW3.72 | vim-minimal 2:8.0.1763-22.el8_10.3 fixed in 2:8.0.1763-24.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-54369 | LOW3.62 | acl 2.2.53-3.el8 fixed in 2.4.0-1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43056 | LOW3.62 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.136.1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43450 | LOW3.62 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.140.1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46135 | LOW3.62 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.136.1.el8_10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46209 | LOW3.62 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.140.1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46259 | LOW3.62 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.140.1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-35177 | LOW3.62 | vim-minimal 2:8.0.1763-22.el8_10.3 fixed in 2:8.0.1763-23.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31419 | LOW3.57 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.136.1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43198 | LOW3.57 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.140.1.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-46054 | LOW3.57 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.137.1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46090 | LOW3.57 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.136.1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46116 | LOW3.57 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.144.1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46117 | LOW3.57 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.146.1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46145 | LOW3.57 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.136.1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46227 | LOW3.57 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.140.1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52993 | LOW3.57 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.147.1.el8_10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53006 | LOW3.57 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.148.1.el8_10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46331 | LOW3.42 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.136.1.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-54370 | LOW3.21 | acl 2.2.53-3.el8 fixed in 2.4.0-1.el8_10 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71066 | LOW3.16 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.143.1.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-47010 | LOW3.15 | java-17-openjdk 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-47059 | LOW3.15 | java-17-openjdk 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47010 | LOW3.15 | java-17-openjdk-devel 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-47059 | LOW3.15 | java-17-openjdk-devel 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47010 | LOW3.15 | java-17-openjdk-headless 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-47059 | LOW3.15 | java-17-openjdk-headless 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43279 | LOW2.96 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.136.1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46113 | LOW2.96 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.143.1.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl 1:1.1.1k-15.el8_6 fixed in 1:1.1.1k-16.el8_6 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl-libs 1:1.1.1k-15.el8_6 fixed in 1:1.1.1k-16.el8_6 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-40026 | LOW2.8 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.147.1.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31411 | LOW2.8 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.143.1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46086 | LOW2.8 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.144.1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-58016 | LOW2.78 | glib2 2.56.4-169.el8_10 fixed in 2.56.4-170.el8_10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-33416 | LOW2.7 | libpng 2:1.6.34-10.el8_10 fixed in 2:1.6.34-11.el8_10 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28390 | LOW2.7 | openssl 1:1.1.1k-15.el8_6 fixed in 1:1.1.1k-17.el8_6 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28390 | LOW2.7 | openssl-libs 1:1.1.1k-15.el8_6 fixed in 1:1.1.1k-17.el8_6 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-10263 | LOW2.57 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.140.1.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43112 | LOW2.48 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.141.1.el8_10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48864 | LOW2.39 | libsolv 0.7.20-6.el8 fixed in 0.7.20-7.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34980 | LOW2.29 | cups-libs 1:2.2.6-67.el8_10 fixed in 1:2.2.6-68.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-45186 | LOW2.29 | expat 2.5.0-1.el8_10 fixed in 2.5.0-2.el8_10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41254 | LOW2.29 | java-17-openjdk 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41254 | LOW2.29 | java-17-openjdk-devel 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-47063 | LOW2.29 | java-17-openjdk-devel 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41254 | LOW2.29 | java-17-openjdk-headless 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53266 | LOW2.29 | perf 4.18.0-553.134.1.el8_10 fixed in 4.18.0-553.143.1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-54369 | LOW2.17 | libacl 2.2.53-3.el8 fixed in 2.4.0-1.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13151 | LOW2.12 | libtasn1 4.13-5.el8_10 fixed in 4.13-6.el8_10 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-6170 | LOW2.12 | libxml2 2.9.7-21.el8_10.4 fixed in 2.9.7-21.el8_10.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-4741 | LOW2.02 | openssl 1:1.1.1k-15.el8_6 fixed in 1:1.1.1k-16.el8_6 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4741 | LOW2.02 | openssl-libs 1:1.1.1k-15.el8_6 fixed in 1:1.1.1k-16.el8_6 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-6238 | LOW1.99 | glibc 2.28-251.el8_10.37 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-60147 | LOW1.99 | java-17-openjdk-devel 1:17.0.19.0.10-1.el8 fixed in 1:17.0.20.0.8-1.1.el8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-39822 | NONE0 | stdlib v1.26.2 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.26.2 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33811 | NONE0 | stdlib v1.26.2 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | stdlib v1.26.2 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39820 | NONE0 | stdlib v1.26.2 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39836 | NONE0 | stdlib v1.26.2 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42499 | NONE0 | stdlib v1.26.2 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.26.2 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-39825 | NONE0 | stdlib v1.26.2 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-39823 | NONE0 | stdlib v1.26.2 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39826 | NONE0 | stdlib v1.26.2 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.26.2 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42507 | NONE0 | stdlib v1.26.2 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-59949 | NONE0 | at.yawk.lz4:lz4-java 1.11.0 fixed in 1.11.1 | — | Not Applicable |
| CVE-2026-59889 | NONE0 | com.fasterxml.jackson.core:jackson-databind 2.21.4 fixed in 2.21.5, 2.18.9, 2.22.1 | 0.3% Theoretical Threat | Not Applicable |
| GHSA-mhm7-754m-9p8w | NONE0 | com.fasterxml.jackson.core:jackson-databind 2.21.4 fixed in 2.18.9, 2.21.5 | — | Not Applicable |
| CVE-2026-34237 | NONE0 | io.modelcontextprotocol.sdk:mcp-core 0.18.2 fixed in 1.0.1, 1.1.1, 0.18.3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46600 | NONE0 | golang.org/x/net v0.55.0 fixed in 0.56.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56852 | NONE0 | golang.org/x/text v0.37.0 fixed in 0.39.0 | 0.4% 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.