Last scanned:
This image is safe for production use. Vulnerability stats show 2 exposed and 6 post-exploit-only findings, but the maximum severities are 5.17 and 2.51 respectively, and none reach 6.0 severity. The image is an official Docker image pinned by digest, which supports its trust and immutability. No specific CVE details are available in the provided top findings.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-103111 | MEDIUM5.17 | pcre2 10.48-r0 fixed in 10.49-r0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-77214 | LOW2.51 | libexpat 2.8.4-r0 fixed in 2.9.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4775 | LOW2.39 | tiff 4.7.1-r0 fixed in 4.7.2-r0 | 0.6% 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-46675 | LOW2.12 | libpng 1.6.58-r1 fixed in 1.6.59-r0 | — | Post-Exploit |
| CVE-2026-102633 | LOW1.81 | libexpat 2.8.4-r0 fixed in 2.9.0-r0 | 0.3% 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-88806 | NONE0 | libx11 1.8.13-r0 fixed in 1.8.14-r0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-94283 | NONE0 | libx11 1.8.13-r0 fixed in 1.8.14-r0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-94284 | NONE0 | libx11 1.8.13-r0 fixed in 1.8.14-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-94287 | NONE0 | libxpm 3.5.19-r0 fixed in 3.5.20-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-94285 | NONE0 | libx11 1.8.13-r0 fixed in 1.8.14-r0 | 0.1% Theoretical Threat | 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.