Last scanned:
This image is safe for production use. The vulnerability scan shows 8 exposed and 6 post-exploit findings, but all are low severity, with the highest exposed severity at 4.5 and the highest post-exploit at 3.53. None of these findings meet the threshold for concern (severity >= 6.0), and the pre-calculated threat score is 0. The image is also published by a well-regarded community source and pinned by digest, reducing supply-chain risk.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2018-20796 | MEDIUM4.5 | libc6 2.41-12+deb13u2 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | MEDIUM4.5 | libc6 2.41-12+deb13u2 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-4437 | MEDIUM4.42 | libc6 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.41-12+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-1010022 | LOW3.53 | libc6 2.41-12+deb13u2 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4438 | LOW3.4 | libc6 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-1010023 | LOW3.17 | libc6 2.41-12+deb13u2 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4046 | LOW2.7 | libc6 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW2.4 | libc6 2.41-12+deb13u2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-6238 | LOW1.99 | libc6 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-1010024 | LOW1.91 | libc6 2.41-12+deb13u2 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010025 | LOW1.91 | libc6 2.41-12+deb13u2 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5435 | LOW1.81 | libc6 2.41-12+deb13u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
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.