Last scanned:
This base/runtime image is a clean foundation for building production images. It is an official Docker Hub image pinned by digest, and the pre-calculated threat score is 0. Although the stats list 13 exposed and 36 post-exploit-only findings, none are at severity 6.0 or higher, with max exposed severity 4.67 and max post-exploit-only severity 2.8. No top exposed-surface or post-exploit-only findings or CVE IDs were provided, so no high-impact inherited risk is identified for images built on top. 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-2025-66382 | MEDIUM4.67 | libexpat1 2.4.7-1ubuntu0.9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc-s1 12.3.0-1ubuntu1~22.04.3 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++6 12.3.0-1ubuntu1~22.04.3 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc-bin 2.35-0ubuntu3.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc6 2.35-0ubuntu3.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc-bin 2.35-0ubuntu3.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc6 2.35-0ubuntu3.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102473 | LOW2.8 | dash 0.5.11+git20210903+057cd650a4ed-3build1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-40228 | LOW2.8 | libsystemd0 249.11-0ubuntu3.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 249.11-0ubuntu3.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | LOW2.7 | libpcre2-8-0 10.39-3ubuntu0.1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-4899 | LOW2.7 | libzstd1 1.4.8+dfsg-3build1 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-86145 | LOW2.51 | libpcre2-8-0 10.39-3ubuntu0.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-89161 | LOW2.39 | libpcre2-8-0 10.39-3ubuntu0.1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86414 | LOW2.34 | curl 7.81.0-1ubuntu1.30 No fix yet | — | Post-Exploit |
| CVE-2026-92388 | LOW2.34 | curl 7.81.0-1ubuntu1.30 No fix yet | — | Post-Exploit |
| CVE-2026-86414 | LOW2.34 | libcurl4 7.81.0-1ubuntu1.30 No fix yet | — | Post-Exploit |
| CVE-2026-92388 | LOW2.34 | libcurl4 7.81.0-1ubuntu1.30 No fix yet | — | Post-Exploit |
| CVE-2026-103111 | LOW2.33 | libpcre2-8-0 10.39-3ubuntu0.1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-107161 | LOW2.29 | libsasl2-2 2.1.27+dfsg2-3ubuntu1.2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-107161 | LOW2.29 | libsasl2-modules-db 2.1.27+dfsg2-3ubuntu1.2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-88647 | LOW2.26 | libgnutls30 3.7.3-4ubuntu1.9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-89157 | LOW2.26 | libpcre2-8-0 10.39-3ubuntu0.1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-18477 | LOW2.24 | tar 1.34+dfsg-1ubuntu0.1.22.04.6 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.24 | tar 1.34+dfsg-1ubuntu0.1.22.04.6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-87862 | LOW2.22 | curl 7.81.0-1ubuntu1.30 No fix yet | — | Post-Exploit |
| CVE-2026-87864 | LOW2.22 | curl 7.81.0-1ubuntu1.30 No fix yet | — | Post-Exploit |
| CVE-2026-92389 | LOW2.22 | curl 7.81.0-1ubuntu1.30 No fix yet | — | Post-Exploit |
| CVE-2026-92391 | LOW2.22 | curl 7.81.0-1ubuntu1.30 No fix yet | — | Post-Exploit |
| CVE-2026-87862 | LOW2.22 | libcurl4 7.81.0-1ubuntu1.30 No fix yet | — | Post-Exploit |
| CVE-2026-87864 | LOW2.22 | libcurl4 7.81.0-1ubuntu1.30 No fix yet | — | Post-Exploit |
| CVE-2026-92389 | LOW2.22 | libcurl4 7.81.0-1ubuntu1.30 No fix yet | — | Post-Exploit |
| CVE-2026-92391 | LOW2.22 | libcurl4 7.81.0-1ubuntu1.30 No fix yet | — | Post-Exploit |
| CVE-2021-31879 | LOW2.2 | wget 1.21.2-2ubuntu1.5 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-102474 | LOW2.04 | dash 0.5.11+git20210903+057cd650a4ed-3build1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-89158 | LOW1.99 | libpcre2-8-0 10.39-3ubuntu0.1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-89160 | LOW1.99 | libpcre2-8-0 10.39-3ubuntu0.1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-94266 | LOW1.98 | curl 7.81.0-1ubuntu1.30 No fix yet | — | Post-Exploit |
| CVE-2026-94266 | LOW1.98 | libcurl4 7.81.0-1ubuntu1.30 No fix yet | — | Post-Exploit |
| CVE-2026-86409 | LOW1.91 | curl 7.81.0-1ubuntu1.30 No fix yet | — | Post-Exploit |
| CVE-2026-86409 | LOW1.91 | libcurl4 7.81.0-1ubuntu1.30 No fix yet | — | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.8.1-2ubuntu2.2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-67693 | LOW1.81 | libgnutls30 3.7.3-4ubuntu1.9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-89156 | LOW1.81 | libpcre2-8-0 10.39-3ubuntu0.1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-29383 | LOW1.68 | passwd 1:4.8.1-2ubuntu2.2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-50495 | NONE0 | libncurses6 6.3-2ubuntu0.3 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | libncursesw6 6.3-2ubuntu0.3 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | libtinfo6 6.3-2ubuntu0.3 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.3-2ubuntu0.3 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-bin 6.3-2ubuntu0.3 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-27943 | NONE0 | gcc-12-base 12.3.0-1ubuntu1~22.04.3 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-18374 | NONE0 | locales 2.35-0ubuntu3.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89092 | NONE0 | locales 2.35-0ubuntu3.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login 1:4.8.1-2ubuntu2.2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-29383 | NONE0 | login 1:4.8.1-2ubuntu2.2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-95184 | NONE0 | libgnutls30 3.7.3-4ubuntu1.9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95209 | NONE0 | libgnutls30 3.7.3-4ubuntu1.9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95210 | NONE0 | libgnutls30 3.7.3-4ubuntu1.9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-85091 | NONE0 | zlib1g 1:1.2.11.dfsg-2ubuntu9.2 No fix yet | 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.