Last scanned:
This image is safe for production use. The 17 exposed and 15 post-exploitation vulnerability records are all low severity (max 5.87 for exposed, 2.8 for post) and do not indicate any practical exploitation paths. The image is pinned by digest and comes from a reputable community publisher with a high trust score. No specific CVE mitigations are required.
Already in good shape · 2 hardening steps left
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-56132 | MEDIUM5.87 | libexpat1 2.8.1-r1 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | libexpat1 2.8.1-r1 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM5.87 | libexpat1 2.8.1-r1 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM5.87 | libexpat1 2.8.1-r1 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | libexpat1 2.8.1-r1 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56407 | MEDIUM5.87 | libexpat1 2.8.1-r1 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56410 | MEDIUM5.87 | libexpat1 2.8.1-r1 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56411 | MEDIUM5.87 | libexpat1 2.8.1-r1 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | libexpat1 2.8.1-r1 fixed in 2.8.2-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | MEDIUM5.02 | libexpat1 2.8.1-r1 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56131 | LOW3.82 | libexpat1 2.8.1-r1 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53655 | LOW2.8 | npm 11.17.0-r0 fixed in 11.17.0-r2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59875 | LOW2.7 | npm 11.17.0-r0 fixed in 12.0.0-r1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12151 | LOW2.29 | node-gyp 13.0.0-r0 fixed in 13.0.0-r1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-12151 | LOW2.29 | npm 11.17.0-r0 fixed in 11.17.0-r1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-59871 | LOW2.29 | npm 11.17.0-r0 fixed in 12.0.0-r1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59873 | LOW2.29 | npm 11.17.0-r0 fixed in 12.0.0-r1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59874 | LOW2.29 | npm 11.17.0-r0 fixed in 12.0.0-r1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11525 | LOW1.89 | node-gyp 13.0.0-r0 fixed in 13.0.0-r1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6733 | LOW1.89 | node-gyp 13.0.0-r0 fixed in 13.0.0-r1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-11525 | LOW1.89 | npm 11.17.0-r0 fixed in 11.17.0-r1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6733 | LOW1.89 | npm 11.17.0-r0 fixed in 11.17.0-r1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-9679 | LOW1.81 | node-gyp 13.0.0-r0 fixed in 13.0.0-r1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9679 | LOW1.81 | npm 11.17.0-r0 fixed in 11.17.0-r1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58055 | LOW1.65 | libnghttp2-14 1.69.0-r0 fixed in 1.70.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6791 | NONE0 | glibc 2.43-r8 fixed in 2.43-r10 | — | Not Applicable |
| CVE-2026-6791 | NONE0 | glibc-locale-posix 2.43-r8 fixed in 2.43-r10 | — | Not Applicable |
| CVE-2026-6791 | NONE0 | ld-linux 2.43-r8 fixed in 2.43-r10 | — | Not Applicable |
| CVE-2026-6791 | NONE0 | libcrypt1 2.43-r8 fixed in 2.43-r10 | — | Not Applicable |
| CVE-2026-56408 | NONE0 | libexpat1 2.8.1-r1 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56409 | NONE0 | libexpat1 2.8.1-r1 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-14257 | NONE0 | npm 11.17.0-r0 fixed in 12.0.1-r2 | 0.3% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.