Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker controlling a malicious server that the CLI contacts could send a crafted compressed response that crashes the CLI or corrupts its memory during a scan, potentially leading to code execution in the scanning environment. The main concern is CVE-2026-111497, which the analysis does not tie to any special configuration, so it should be assumed to apply in normal operation. The image's exposed-surface findings include several high-severity items, so they cannot be dismissed, even though none are known to be actively exploited. Because the container exposes no ports and runs as a nonroot user, the practical exposure depends on the trust placed in the servers it connects to.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-111497 | HIGH7.45 | libbrotlicommon1 1.2.0-r6 fixed in 1.2.0-r7 | 36.0% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-111497 | HIGH7.45 | libbrotlidec1 1.2.0-r6 fixed in 1.2.0-r7 | 36.0% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-111497 | HIGH7.45 | libbrotlienc1 1.2.0-r6 fixed in 1.2.0-r7 | 36.0% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-111943 | MEDIUM5.44 | ca-certificates-bundle 20260909-r2 fixed in 20260909-r3 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-11579 | MEDIUM4.42 | github.com/nwaples/rardecode v1.1.3 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| GO-2026-5932 | MEDIUM4 | golang.org/x/crypto v0.58.0 No fix yet | — | Directly Exposed |
| CVE-2026-33481 | LOW3.18 | github.com/anchore/syft v1.21.0 fixed in 1.42.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33997 | LOW2.92 | github.com/docker/docker v28.0.3+incompatible fixed in 29.3.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41567 | LOW2.59 | github.com/docker/docker v28.0.3+incompatible No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42306 | LOW2.59 | github.com/docker/docker v28.0.3+incompatible No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41568 | LOW2.16 | github.com/docker/docker v28.0.3+incompatible No fix yet | 0.1% Theoretical Threat | Post-Exploit |
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.