Last scanned:
··This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker who can reach port 8080 could send crafted HTTP requests that exhaust container memory, making the watchtower service unresponsive and disrupting the container updates it manages. Note: CVE-2023-45288 only applies if the HTTP API is enabled and reached over HTTP/2 with TLS, and it causes denial of service only. The container runs as root by default, so the impact of a compromise is not limited by a non-root user, although the scan found no findings flagged as actively exploited in the wild. The data does not show a single compensating control that fully removes CVE-2023-24534, so strict access controls around port 8080 are needed.
Hardening plan for this image · 3 steps
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2023-45288 | HIGH7.8 | golang.org/x/net v0.17.0 fixed in 0.23.0 | 92.0% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-45288 | HIGH7.8 | stdlib v1.18.10 fixed in 1.21.9, 1.22.2 | 92.0% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-24534 | HIGH7.5 | stdlib v1.18.10 fixed in 1.19.8, 1.20.3 | 1.9% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2023-24539 | HIGH7.3 | stdlib v1.18.10 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29400 | HIGH7.3 | stdlib v1.18.10 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-111943 | MEDIUM6.8 | stdlib v1.18.10 fixed in 1.26.10, 1.27.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-29403 | MEDIUM6.63 | stdlib v1.18.10 fixed in 1.19.10, 1.20.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-29406 | MEDIUM6.5 | stdlib v1.18.10 fixed in 1.19.11, 1.20.6 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-61727 | MEDIUM6.5 | stdlib v1.18.10 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39825 | MEDIUM6.5 | stdlib v1.18.10 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56866 | MEDIUM6.5 | stdlib v1.18.10 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-94439 | MEDIUM6.5 | stdlib v1.18.10 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32282 | MEDIUM6.4 | stdlib v1.18.10 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-58183 | MEDIUM6.38 | stdlib v1.18.10 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58188 | MEDIUM6.38 | stdlib v1.18.10 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-22871 | MEDIUM6.18 | stdlib v1.18.10 fixed in 1.23.8, 1.24.2 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-32289 | MEDIUM6.1 | stdlib v1.18.10 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-94448 | MEDIUM6.1 | stdlib v1.18.10 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97030 | MEDIUM6.1 | stdlib v1.18.10 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68121 | MEDIUM6 | stdlib v1.18.10 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-45338 | MEDIUM6 | golang.org/x/net v0.17.0 fixed in 0.33.0 | 1.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33814 | MEDIUM6 | golang.org/x/net v0.17.0 fixed in 0.53.0 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-46600 | MEDIUM6 | golang.org/x/net v0.17.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78669 | MEDIUM6 | golang.org/x/net v0.17.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78659 | MEDIUM6 | golang.org/x/net v0.17.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78660 | MEDIUM6 | golang.org/x/net v0.17.0 fixed in 0.60.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2022-41723 | MEDIUM6 | stdlib v1.18.10 fixed in 1.19.6, 1.20.1 | 4.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-41725 | MEDIUM6 | stdlib v1.18.10 fixed in 1.19.6, 1.20.1 | 1.2% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-24536 | MEDIUM6 | stdlib v1.18.10 fixed in 1.19.8, 1.20.3 | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-39325 | MEDIUM6 | stdlib v1.18.10 fixed in 1.20.10, 1.21.3 | 3.8% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2025-61726 | MEDIUM6 | stdlib v1.18.10 fixed in 1.24.12, 1.25.6 | 2.3% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33814 | MEDIUM6 | stdlib v1.18.10 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56853 | MEDIUM6 | stdlib v1.18.10 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56862 | MEDIUM6 | stdlib v1.18.10 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78669 | MEDIUM6 | stdlib v1.18.10 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78659 | MEDIUM6 | stdlib v1.18.10 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-47907 | MEDIUM5.95 | stdlib v1.18.10 fixed in 1.23.12, 1.24.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-24791 | MEDIUM5.9 | stdlib v1.18.10 fixed in 1.21.12, 1.22.5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34158 | MEDIUM5.9 | stdlib v1.18.10 fixed in 1.22.7, 1.23.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97032 | MEDIUM5.9 | stdlib v1.18.10 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4673 | MEDIUM5.78 | stdlib v1.18.10 fixed in 1.23.10, 1.24.4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-24785 | MEDIUM5.52 | stdlib v1.18.10 fixed in 1.21.8, 1.22.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-47906 | MEDIUM5.52 | stdlib v1.18.10 fixed in 1.23.12, 1.24.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-32288 | MEDIUM5.5 | stdlib v1.18.10 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85747 | MEDIUM5.44 | github.com/docker/distribution v2.8.3+incompatible No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2024-24784 | MEDIUM5.4 | stdlib v1.18.10 fixed in 1.21.8, 1.22.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-27142 | MEDIUM5.4 | stdlib v1.18.10 fixed in 1.25.8, 1.26.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39823 | MEDIUM5.4 | stdlib v1.18.10 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39826 | MEDIUM5.4 | stdlib v1.18.10 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-29409 | MEDIUM5.3 | stdlib v1.18.10 fixed in 1.19.12, 1.20.7, 1.21.0-rc.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39326 | MEDIUM5.3 | stdlib v1.18.10 fixed in 1.20.12, 1.21.5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45284 | MEDIUM5.3 | stdlib v1.18.10 fixed in 1.20.11, 1.21.4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45289 | MEDIUM5.3 | stdlib v1.18.10 fixed in 1.21.8, 1.22.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45290 | MEDIUM5.3 | stdlib v1.18.10 fixed in 1.21.8, 1.22.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-22873 | MEDIUM5.3 | stdlib v1.18.10 fixed in 1.23.9, 1.24.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-61730 | MEDIUM5.3 | stdlib v1.18.10 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42505 | MEDIUM5.3 | stdlib v1.18.10 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42507 | MEDIUM5.3 | stdlib v1.18.10 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | MEDIUM5.3 | stdlib v1.18.10 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-25680 | MEDIUM5.2 | golang.org/x/net v0.17.0 fixed in 0.55.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2023-39318 | MEDIUM5.18 | stdlib v1.18.10 fixed in 1.20.8, 1.21.1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-39319 | MEDIUM5.18 | stdlib v1.18.10 fixed in 1.20.8, 1.21.1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-24783 | MEDIUM5.02 | stdlib v1.18.10 fixed in 1.21.8, 1.22.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-34155 | MEDIUM5.02 | stdlib v1.18.10 fixed in 1.22.7, 1.23.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-45336 | MEDIUM5.02 | stdlib v1.18.10 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42502 | MEDIUM4.88 | golang.org/x/net v0.17.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97032 | MEDIUM4.72 | golang.org/x/net v0.17.0 fixed in 0.60.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2024-24789 | MEDIUM4.67 | stdlib v1.18.10 fixed in 1.21.11, 1.22.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-0913 | MEDIUM4.67 | stdlib v1.18.10 fixed in 1.23.10, 1.24.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56851 | MEDIUM4.5 | golang.org/x/text v0.14.0 fixed in 0.41.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56852 | MEDIUM4.5 | golang.org/x/text v0.14.0 fixed in 0.39.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-24786 | MEDIUM4.5 | google.golang.org/protobuf v1.31.0 fixed in 1.33.0 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41724 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.19.6, 1.20.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24537 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.19.8, 1.20.3 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45283 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.20.11, 1.21.4, 1.20.12, 1.21.5 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45287 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.20.0 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34156 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.22.7, 1.23.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-61729 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25679 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.25.8, 1.26.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-27145 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32280 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32281 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32283 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33811 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.25.10, 1.26.3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-33818 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-39820 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39836 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42499 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42504 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56859 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56860 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78667 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-97031 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61728 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.24.12, 1.25.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-78660 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-94440 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-24532 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.19.7, 1.20.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-22866 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.22.12, 1.23.6, 1.24.0-rc.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-47912 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58185 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-58187 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58189 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61723 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.24.8, 1.25.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-61724 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61725 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-58186 | MEDIUM4.5 | stdlib v1.18.10 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-22872 | MEDIUM4.42 | golang.org/x/net v0.17.0 fixed in 0.38.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42506 | MEDIUM4.32 | golang.org/x/net v0.17.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-47911 | MEDIUM4.24 | golang.org/x/net v0.17.0 fixed in 0.45.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-58190 | MEDIUM4.24 | golang.org/x/net v0.17.0 fixed in 0.45.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78663 | MEDIUM4.24 | golang.org/x/net v0.17.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2024-41110 | MEDIUM4.14 | github.com/docker/docker v24.0.7+incompatible fixed in 23.0.15, 26.1.5, 27.1.1, 25.0.6 | 16.5% High Exploitation Risk | Post-Exploit |
| CVE-2026-39824 | MEDIUM4 | golang.org/x/sys v0.13.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22870 | LOW3.74 | stdlib v1.18.10 fixed in 1.23.7, 1.24.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-45341 | LOW3.57 | stdlib v1.18.10 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-24538 | LOW3.53 | stdlib v1.18.10 fixed in 1.19.8, 1.20.3 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-24540 | LOW3.53 | stdlib v1.18.10 fixed in 1.19.9, 1.20.4 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2024-24790 | LOW3.53 | stdlib v1.18.10 fixed in 1.21.11, 1.22.4 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-56857 | LOW3.3 | stdlib v1.18.10 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-22870 | LOW2.99 | golang.org/x/net v0.17.0 fixed in 0.36.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-39821 | LOW2.95 | golang.org/x/net v0.17.0 fixed in 0.55.0 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-39821 | LOW2.95 | stdlib v1.18.10 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-33997 | LOW2.92 | github.com/docker/docker v24.0.7+incompatible fixed in 29.3.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-25681 | LOW2.92 | golang.org/x/net v0.17.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27136 | LOW2.92 | golang.org/x/net v0.17.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56858 | LOW2.92 | stdlib v1.18.10 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15558 | LOW2.88 | github.com/docker/cli v24.0.7+incompatible fixed in 29.2.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-39822 | LOW2.81 | stdlib v1.18.10 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-41722 | LOW2.7 | stdlib v1.18.10 fixed in 1.19.6, 1.20.1 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-41567 | LOW2.59 | github.com/docker/docker v24.0.7+incompatible No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42306 | LOW2.59 | github.com/docker/docker v24.0.7+incompatible No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27139 | LOW2.5 | stdlib v1.18.10 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-24557 | LOW2.39 | github.com/docker/docker v24.0.7+incompatible fixed in 24.0.9, 25.0.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41568 | LOW2.16 | github.com/docker/docker v24.0.7+incompatible No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-54410 | LOW1.59 | github.com/docker/docker v24.0.7+incompatible fixed in 25.0.13, 28.0.0 | 0.2% Theoretical Threat | Post-Exploit |
Want to check another image? Run a full scan with the Docker Security Scanner.