Last scanned:
This image is safe for production use. It is an official Docker Hub nginx image pinned by digest, which supports trust and immutability. The provided vulnerability data lists 10 exposed-surface findings and 11 post-exploit-only findings, but none are at severity 6.0 or higher; the highest exposed severity is 5.95 and the highest post-exploit severity is 2.51. No top findings or CVE IDs were supplied, so there are no specific high-impact issues to remediate. Continue standard image hygiene and monitor for updates.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-53612 | MEDIUM5.95 | libuuid 2.42.1-r0 fixed in 2.42.3-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libuuid 2.42.1-r0 fixed in 2.42.3-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53614 | MEDIUM5.95 | libuuid 2.42.1-r0 fixed in 2.42.3-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libuuid 2.42.1-r0 fixed in 2.42.3-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46675 | MEDIUM4.72 | libpng 1.6.58-r1 fixed in 1.6.59-r0 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-94284 | MEDIUM4.67 | libx11 1.8.13-r0 fixed in 1.8.14-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94287 | MEDIUM4.67 | libxpm 3.5.19-r0 fixed in 3.5.20-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94285 | MEDIUM4.33 | libx11 1.8.13-r0 fixed in 1.8.14-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid 2.42.1-r0 fixed in 2.42.3-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-77214 | LOW2.51 | libexpat 2.8.4-r0 fixed in 2.9.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.42 | libuuid 2.42.1-r0 fixed in 2.42.3-r1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.39 | libuuid 2.42.1-r0 fixed in 2.42.3-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.39 | libuuid 2.42.1-r0 fixed in 2.42.3-r0 | 0.2% 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-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-88806 | LOW2.29 | libx11 1.8.13-r0 fixed in 1.8.14-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-94283 | LOW1.99 | libx11 1.8.13-r0 fixed in 1.8.14-r0 | 0.2% Theoretical Threat | 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-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.