Last scanned:
This image is safe for production use. Vulnerability data shows 2 exposed-surface entries and 4 post-exploit-only entries, but none reach notable severity — the highest recorded score is 2.39 — so they do not create practical exploitation paths for this container. The image is a popular community build pinned by digest, which gives a stable, reproducible deployment. No specific compensating control is required, though keeping the deployment behind your standard network policy remains good practice.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-4775 | LOW2.39 | tiff 4.7.1-r0 fixed in 4.7.2-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-103111 | LOW2.33 | pcre2 10.48-r0 fixed in 10.49-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-93990 | LOW2.29 | libexpat 2.8.4-r0 fixed in 2.8.5-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58055 | LOW1.65 | nghttp2-libs 1.69.0-r0 fixed in 1.70.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-46675 | NONE0 | libpng 1.6.58-r1 fixed in 1.6.59-r0 | — | Not Applicable |
| CVE-2026-85091 | NONE0 | zlib 1.3.2-r0 fixed in 1.3.2-r1 | 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.