Last scanned:
This base/runtime image is a clean foundation for building production images. It does contain two lower-severity exposed-surface findings, with a maximum severity of 5.46, and neither is known to be actively exploited. Neither finding reaches the severity or exploitation level that would change the verdict. Images built on this base should still run their normal scanning, and should consider dropping root privileges in the final image, since this base runs as root by default. 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-2026-33210 | MEDIUM5.46 | json 2.18.0 fixed in ~> 2.15.2.1, ~> 2.17.1.2, >= 2.19.2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-54696 | LOW2.22 | json 2.18.0 fixed in >= 2.19.9 | 0.4% Theoretical Threat | Directly Exposed |
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.