Last scanned:
This base/runtime image is a clean foundation for building production images. It does carry 63 low-to-moderate exposed-surface findings, but none score 6.0 or higher and none are known to be actively exploited, so they do not drive the verdict. Images built on top of it will inherit these findings, so they should still be tracked and patched in routine rebuilds. The image is pinned by digest and comes from a widely used community publisher, which supports a stable and predictable 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 |
|---|---|---|---|---|
| GHSA-6q48-6c7w-9gw2 | MEDIUM5.46 | certifi 2026.6.17 fixed in 2026.10.18 | — | Directly Exposed |
| CVE-2025-47273 | MEDIUM5.28 | setuptools 70.3.0 fixed in 78.1.1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-39821 | MEDIUM4.92 | golang.org/x/net v0.38.0 fixed in 0.55.0 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97687 | MEDIUM4.86 | urllib3 2.7.0 fixed in 2.8.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25681 | MEDIUM4.86 | golang.org/x/net v0.38.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27136 | MEDIUM4.86 | golang.org/x/net v0.38.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| GHSA-6v7p-g79w-8964 | MEDIUM4.5 | msgpack 1.1.2 fixed in 1.2.1 | — | Directly Exposed |
| CVE-2026-97689 | MEDIUM4.5 | urllib3 2.7.0 fixed in 2.8.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM4.5 | golang.org/x/net v0.38.0 fixed in 0.53.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-46600 | MEDIUM4.5 | golang.org/x/net v0.38.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78669 | MEDIUM4.5 | golang.org/x/net v0.38.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78659 | MEDIUM4.5 | golang.org/x/net v0.38.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78660 | MEDIUM4.5 | golang.org/x/net v0.38.0 fixed in 0.60.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56851 | MEDIUM4.5 | golang.org/x/text v0.23.0 fixed in 0.41.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56852 | MEDIUM4.5 | golang.org/x/text v0.23.0 fixed in 0.39.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78669 | MEDIUM4.5 | golang.org/x/net v0.57.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78659 | MEDIUM4.5 | golang.org/x/net v0.57.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78660 | MEDIUM4.5 | golang.org/x/net v0.57.0 fixed in 0.60.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56851 | MEDIUM4.5 | golang.org/x/text v0.40.0 fixed in 0.41.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78669 | MEDIUM4.5 | golang.org/x/net v0.56.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78659 | MEDIUM4.5 | golang.org/x/net v0.56.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78660 | MEDIUM4.5 | golang.org/x/net v0.56.0 fixed in 0.60.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63209 | MEDIUM4.5 | github.com/klauspost/compress v1.18.1 fixed in 1.18.7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-84304 | MEDIUM4.5 | google.golang.org/grpc v1.82.1 fixed in 1.83.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-84445 | MEDIUM4.5 | google.golang.org/grpc v1.82.1 fixed in 1.82.2, 1.83.2, 1.84.0-dev.0.20260825144003-d5a41119e0e3, 1.85.0-dev.0.20260825072537-93e31b48545e | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56851 | MEDIUM4.5 | golang.org/x/text v0.37.0 fixed in 0.41.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56852 | MEDIUM4.5 | golang.org/x/text v0.37.0 fixed in 0.39.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56851 | MEDIUM4.5 | golang.org/x/text v0.28.0 fixed in 0.41.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56852 | MEDIUM4.5 | golang.org/x/text v0.28.0 fixed in 0.39.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78669 | MEDIUM4.5 | golang.org/x/net v0.58.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78659 | MEDIUM4.5 | golang.org/x/net v0.58.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78660 | MEDIUM4.5 | golang.org/x/net v0.58.0 fixed in 0.60.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56854 | MEDIUM4.08 | golang.org/x/crypto v0.54.0 fixed in 0.55.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-85747 | MEDIUM4.08 | github.com/docker/distribution v2.8.3+incompatible No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39824 | MEDIUM4 | golang.org/x/sys v0.31.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25680 | LOW3.9 | golang.org/x/net v0.38.0 fixed in 0.55.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-84303 | LOW3.78 | google.golang.org/grpc v1.82.1 fixed in 1.83.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59890 | LOW3.66 | setuptools 70.3.0 fixed in 83.0.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42502 | LOW3.66 | golang.org/x/net v0.38.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-97032 | LOW3.54 | golang.org/x/net v0.38.0 fixed in 0.60.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-97032 | LOW3.54 | golang.org/x/net v0.57.0 fixed in 0.60.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-97032 | LOW3.54 | golang.org/x/net v0.56.0 fixed in 0.60.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-97032 | LOW3.54 | golang.org/x/net v0.58.0 fixed in 0.60.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53495 | LOW3.3 | github.com/containerd/containerd v1.7.33 fixed in 1.7.35 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42506 | LOW3.24 | golang.org/x/net v0.38.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-97688 | LOW3.18 | urllib3 2.7.0 fixed in 2.8.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-47911 | LOW3.18 | golang.org/x/net v0.38.0 fixed in 0.45.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-58190 | LOW3.18 | golang.org/x/net v0.38.0 fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | LOW3.18 | golang.org/x/net v0.38.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56855 | LOW3.18 | golang.org/x/crypto v0.55.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78662 | LOW3.18 | golang.org/x/crypto v0.55.0 fixed in 0.56.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | LOW3.18 | golang.org/x/net v0.57.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56855 | LOW3.18 | golang.org/x/crypto v0.54.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78662 | LOW3.18 | golang.org/x/crypto v0.54.0 fixed in 0.56.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | LOW3.18 | golang.org/x/net v0.56.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-53493 | LOW3.18 | github.com/containerd/containerd v1.7.33 fixed in 1.7.36 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | LOW3.18 | golang.org/x/net v0.58.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly Exposed |
| GO-2026-5932 | LOW2.4 | golang.org/x/crypto v0.55.0 No fix yet | — | Directly Exposed |
| GO-2026-5932 | LOW2.4 | golang.org/x/crypto v0.54.0 No fix yet | — | Directly Exposed |
| GO-2026-5932 | LOW2.4 | golang.org/x/crypto v0.56.0 No fix yet | — | Directly Exposed |
| CVE-2026-95838 | LOW1.98 | github.com/containerd/containerd v1.7.33 fixed in 1.7.35 | 0.2% Theoretical Threat | Directly Exposed |
| GHSA-xmj3-9gf7-h52w | LOW0.6 | setuptools 70.3.0 fixed in 84.1.0 | — | Directly Exposed |
| GHSA-xmj3-9gf7-h52w | LOW0.6 | setuptools 84.0.0 fixed in 84.1.0 | — | Directly Exposed |
| CVE-2025-68121 | NONE0 | stdlib v1.24.0 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-22871 | NONE0 | stdlib v1.24.0 fixed in 1.23.8, 1.24.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39821 | NONE0 | stdlib v1.25.7 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-39821 | NONE0 | stdlib v1.26.4 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-39821 | NONE0 | stdlib v1.26.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-39821 | NONE0 | stdlib v1.26.3 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-39821 | NONE0 | stdlib v1.24.0 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-56858 | NONE0 | stdlib v1.25.7 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56858 | NONE0 | stdlib v1.26.4 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56858 | NONE0 | stdlib v1.26.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56858 | NONE0 | stdlib v1.26.3 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56858 | NONE0 | stdlib v1.24.0 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39822 | NONE0 | stdlib v1.25.7 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39822 | NONE0 | stdlib v1.26.4 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39822 | NONE0 | stdlib v1.26.3 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39822 | NONE0 | stdlib v1.24.0 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25679 | NONE0 | stdlib v1.25.7 fixed in 1.25.8, 1.26.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.25.7 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32280 | NONE0 | stdlib v1.25.7 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32281 | NONE0 | stdlib v1.25.7 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32283 | NONE0 | stdlib v1.25.7 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33811 | NONE0 | stdlib v1.25.7 fixed in 1.25.10, 1.26.3 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | stdlib v1.25.7 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-33818 | NONE0 | stdlib v1.25.7 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-39820 | NONE0 | stdlib v1.25.7 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39836 | NONE0 | stdlib v1.25.7 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42499 | NONE0 | stdlib v1.25.7 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.25.7 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56853 | NONE0 | stdlib v1.25.7 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56859 | NONE0 | stdlib v1.25.7 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56860 | NONE0 | stdlib v1.25.7 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-56862 | NONE0 | stdlib v1.25.7 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78667 | NONE0 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78669 | NONE0 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97031 | NONE0 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-33818 | NONE0 | stdlib v1.26.4 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46600 | NONE0 | stdlib v1.26.4 fixed in 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-56853 | NONE0 | stdlib v1.26.4 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56859 | NONE0 | stdlib v1.26.4 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56860 | NONE0 | stdlib v1.26.4 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-56862 | NONE0 | stdlib v1.26.4 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78667 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78669 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97031 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-33818 | NONE0 | stdlib v1.26.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46600 | NONE0 | stdlib v1.26.5 fixed in 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-56853 | NONE0 | stdlib v1.26.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56859 | NONE0 | stdlib v1.26.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56860 | NONE0 | stdlib v1.26.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-56862 | NONE0 | stdlib v1.26.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78667 | NONE0 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78669 | NONE0 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97031 | NONE0 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78667 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78669 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97031 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.26.3 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33818 | NONE0 | stdlib v1.26.3 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.26.3 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46600 | NONE0 | stdlib v1.26.3 fixed in 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-56853 | NONE0 | stdlib v1.26.3 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56859 | NONE0 | stdlib v1.26.3 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56860 | NONE0 | stdlib v1.26.3 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-56862 | NONE0 | stdlib v1.26.3 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78667 | NONE0 | stdlib v1.26.3 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78669 | NONE0 | stdlib v1.26.3 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97031 | NONE0 | stdlib v1.26.3 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.26.3 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.26.3 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.26.3 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78667 | NONE0 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78669 | NONE0 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97031 | NONE0 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-22874 | NONE0 | stdlib v1.24.0 fixed in 1.24.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61726 | NONE0 | stdlib v1.24.0 fixed in 1.24.12, 1.25.6 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-61729 | NONE0 | stdlib v1.24.0 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25679 | NONE0 | stdlib v1.24.0 fixed in 1.25.8, 1.26.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.24.0 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32280 | NONE0 | stdlib v1.24.0 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32281 | NONE0 | stdlib v1.24.0 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32283 | NONE0 | stdlib v1.24.0 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33811 | NONE0 | stdlib v1.24.0 fixed in 1.25.10, 1.26.3 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | stdlib v1.24.0 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-33818 | NONE0 | stdlib v1.24.0 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-39820 | NONE0 | stdlib v1.24.0 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39836 | NONE0 | stdlib v1.24.0 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42499 | NONE0 | stdlib v1.24.0 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.24.0 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56853 | NONE0 | stdlib v1.24.0 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56859 | NONE0 | stdlib v1.24.0 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56860 | NONE0 | stdlib v1.24.0 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-56862 | NONE0 | stdlib v1.24.0 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78667 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78669 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97031 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58183 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58188 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61728 | NONE0 | stdlib v1.24.0 fixed in 1.24.12, 1.25.6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78667 | NONE0 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78669 | NONE0 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97031 | NONE0 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-47907 | NONE0 | stdlib v1.24.0 fixed in 1.23.12, 1.24.6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-111943 | NONE0 | stdlib v1.25.7 fixed in 1.26.10, 1.27.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-111943 | NONE0 | stdlib v1.26.4 fixed in 1.26.10, 1.27.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-111943 | NONE0 | stdlib v1.26.5 fixed in 1.26.10, 1.27.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-111943 | NONE0 | stdlib v1.27.1 fixed in 1.26.10, 1.27.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-111943 | NONE0 | stdlib v1.26.3 fixed in 1.26.10, 1.27.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-111943 | NONE0 | stdlib v1.26.8 fixed in 1.26.10, 1.27.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-111943 | NONE0 | stdlib v1.24.0 fixed in 1.26.10, 1.27.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-4673 | NONE0 | stdlib v1.24.0 fixed in 1.23.10, 1.24.4 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-111943 | NONE0 | stdlib v1.26.6 fixed in 1.26.10, 1.27.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39825 | NONE0 | stdlib v1.25.7 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56866 | NONE0 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-94439 | NONE0 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56866 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-94439 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56866 | NONE0 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-94439 | NONE0 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56866 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-94439 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56866 | NONE0 | stdlib v1.26.3 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-94439 | NONE0 | stdlib v1.26.3 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56866 | NONE0 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-94439 | NONE0 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-47906 | NONE0 | stdlib v1.24.0 fixed in 1.23.12, 1.24.6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61727 | NONE0 | stdlib v1.24.0 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39825 | NONE0 | stdlib v1.24.0 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56866 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-94439 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56866 | NONE0 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-94439 | NONE0 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32282 | NONE0 | stdlib v1.25.7 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32282 | NONE0 | stdlib v1.24.0 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32289 | NONE0 | stdlib v1.25.7 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94448 | NONE0 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94448 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94448 | NONE0 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94448 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94448 | NONE0 | stdlib v1.26.3 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.26.3 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94448 | NONE0 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32289 | NONE0 | stdlib v1.24.0 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94448 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94448 | NONE0 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97032 | NONE0 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97032 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97032 | NONE0 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97032 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97032 | NONE0 | stdlib v1.26.3 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97032 | NONE0 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97032 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97032 | NONE0 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-32288 | NONE0 | stdlib v1.25.7 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-0913 | NONE0 | stdlib v1.24.0 fixed in 1.23.10, 1.24.4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32288 | NONE0 | stdlib v1.24.0 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27142 | NONE0 | stdlib v1.25.7 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39823 | NONE0 | stdlib v1.25.7 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39826 | NONE0 | stdlib v1.25.7 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-27142 | NONE0 | stdlib v1.24.0 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39823 | NONE0 | stdlib v1.24.0 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39826 | NONE0 | stdlib v1.24.0 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.25.7 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42507 | NONE0 | stdlib v1.25.7 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-78663 | NONE0 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.26.4 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-78663 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78663 | NONE0 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78663 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.26.3 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42507 | NONE0 | stdlib v1.26.3 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-78663 | NONE0 | stdlib v1.26.3 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78663 | NONE0 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-22873 | NONE0 | stdlib v1.24.0 fixed in 1.23.9, 1.24.3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-47912 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58185 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58187 | NONE0 | stdlib v1.24.0 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58189 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61723 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-61724 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61725 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61730 | NONE0 | stdlib v1.24.0 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.24.0 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42507 | NONE0 | stdlib v1.24.0 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-78663 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58186 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78663 | NONE0 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-22870 | NONE0 | stdlib v1.24.0 fixed in 1.23.7, 1.24.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56857 | NONE0 | stdlib v1.25.7 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56857 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56857 | NONE0 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56857 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56857 | NONE0 | stdlib v1.26.3 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56857 | NONE0 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56857 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56857 | NONE0 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-27139 | NONE0 | stdlib v1.25.7 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27139 | NONE0 | stdlib v1.24.0 fixed in 1.25.8, 1.26.1 | 0.2% 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.