Last scanned:
This base/runtime image carries significant vulnerabilities that any image built on it would inherit; remediate them in the final image before production. If a GnuTLS server is built on top of this image, an attacker could bypass its login with a crafted username or read leaked memory and disrupt the service. Note: CVE-2026-42010 only applies if a GnuTLS server configured with RSA-PSK authentication is added, and CVE-2026-33845 only applies if a DTLS-enabled GnuTLS server is enabled. The image itself runs no network service, so the risk depends on what teams build on top of it. Note: this is a general-purpose base/runtime image — many findings live in components that an application built on top may never load, so actual exploitability depends on the final image. For an accurate risk picture, re-scan the final application image with context.
Hardening plan for this image · 4 steps
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-42010 | HIGH7.84 | gnutls 3.8.8-r0 fixed in 3.8.13-r0 | 1.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33845 | HIGH7.28 | gnutls 3.8.8-r0 fixed in 3.8.13-r0 | 2.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2025-15467 | MEDIUM6 | libcrypto3 3.5.4-r0 fixed in 3.5.5-r0 | 74.8% Actively Exploited | Directly Exposed |
| CVE-2025-15467 | MEDIUM6 | libssl3 3.5.4-r0 fixed in 3.5.5-r0 | 74.8% Actively Exploited | Directly Exposed |
| CVE-2026-3833 | MEDIUM5.92 | gnutls 3.8.8-r0 fixed in 3.8.13-r0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42011 | MEDIUM5.92 | gnutls 3.8.8-r0 fixed in 3.8.13-r0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-69419 | MEDIUM5.92 | libcrypto3 3.5.4-r0 fixed in 3.5.5-r0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-69419 | MEDIUM5.92 | libssl3 3.5.4-r0 fixed in 3.5.5-r0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-69419 | MEDIUM5.92 | openssl 3.5.4-r0 fixed in 3.5.5-r0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-31790 | MEDIUM5.9 | libcrypto3 3.5.4-r0 fixed in 3.5.6-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | libcrypto3 3.5.4-r0 fixed in 3.5.7-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-15468 | MEDIUM5.9 | libcrypto3 3.5.4-r0 fixed in 3.5.5-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-66199 | MEDIUM5.9 | libcrypto3 3.5.4-r0 fixed in 3.5.5-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.9 | libcrypto3 3.5.4-r0 fixed in 3.5.5-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.9 | libcrypto3 3.5.4-r0 fixed in 3.5.5-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.9 | libcrypto3 3.5.4-r0 fixed in 3.5.7-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.9 | libcrypto3 3.5.4-r0 fixed in 3.5.7-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | libcrypto3 3.5.4-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.9 | libcrypto3 3.5.4-r0 fixed in 3.5.7-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | libssl3 3.5.4-r0 fixed in 3.5.6-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | libssl3 3.5.4-r0 fixed in 3.5.7-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-15468 | MEDIUM5.9 | libssl3 3.5.4-r0 fixed in 3.5.5-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-66199 | MEDIUM5.9 | libssl3 3.5.4-r0 fixed in 3.5.5-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.9 | libssl3 3.5.4-r0 fixed in 3.5.5-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.9 | libssl3 3.5.4-r0 fixed in 3.5.5-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.9 | libssl3 3.5.4-r0 fixed in 3.5.7-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.9 | libssl3 3.5.4-r0 fixed in 3.5.7-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | libssl3 3.5.4-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.9 | libssl3 3.5.4-r0 fixed in 3.5.7-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | MEDIUM5.88 | libcrypto3 3.5.4-r0 fixed in 3.5.6-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | MEDIUM5.88 | libssl3 3.5.4-r0 fixed in 3.5.6-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM5.68 | gnutls 3.8.8-r0 fixed in 3.8.13-r0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-32990 | MEDIUM5.58 | gnutls 3.8.8-r0 fixed in 3.8.12-r0 | 0.9% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-15469 | MEDIUM5.5 | libcrypto3 3.5.4-r0 fixed in 3.5.5-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM5.5 | libcrypto3 3.5.4-r0 fixed in 3.5.5-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM5.5 | libcrypto3 3.5.4-r0 fixed in 3.5.7-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-15469 | MEDIUM5.5 | libssl3 3.5.4-r0 fixed in 3.5.5-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM5.5 | libssl3 3.5.4-r0 fixed in 3.5.5-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM5.5 | libssl3 3.5.4-r0 fixed in 3.5.7-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-6042 | MEDIUM5.5 | musl 1.2.5-r10 fixed in 1.2.5-r11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6042 | MEDIUM5.5 | musl-utils 1.2.5-r10 fixed in 1.2.5-r11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | MEDIUM5.46 | libcrypto3 3.5.4-r0 fixed in 3.5.7-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | MEDIUM5.46 | libssl3 3.5.4-r0 fixed in 3.5.7-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM5.3 | libcrypto3 3.5.4-r0 fixed in 3.5.7-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42767 | MEDIUM5.3 | libcrypto3 3.5.4-r0 fixed in 3.5.7-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM5.3 | libssl3 3.5.4-r0 fixed in 3.5.7-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42767 | MEDIUM5.3 | libssl3 3.5.4-r0 fixed in 3.5.7-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.28 | gnutls 3.8.8-r0 fixed in 3.8.13-r0 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-34180 | MEDIUM5 | libcrypto3 3.5.4-r0 fixed in 3.5.7-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | libssl3 3.5.4-r0 fixed in 3.5.7-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-32988 | MEDIUM4.92 | gnutls 3.8.8-r0 fixed in 3.8.12-r0 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42013 | MEDIUM4.92 | gnutls 3.8.8-r0 fixed in 3.8.13-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM4.92 | gnutls 3.8.8-r0 fixed in 3.8.13-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-77214 | MEDIUM4.92 | libexpat 2.7.3-r0 fixed in 2.9.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11187 | MEDIUM4.88 | libcrypto3 3.5.4-r0 fixed in 3.5.5-r0 | 5.2% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2025-11187 | MEDIUM4.88 | libssl3 3.5.4-r0 fixed in 3.5.5-r0 | 5.2% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2025-11187 | MEDIUM4.88 | openssl 3.5.4-r0 fixed in 3.5.5-r0 | 5.2% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-28387 | MEDIUM4.86 | libcrypto3 3.5.4-r0 fixed in 3.5.6-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45447 | MEDIUM4.86 | libcrypto3 3.5.4-r0 fixed in 3.5.7-r0 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-25646 | MEDIUM4.86 | libpng 1.6.47-r0 fixed in 1.6.55-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28387 | MEDIUM4.86 | libssl3 3.5.4-r0 fixed in 3.5.6-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45447 | MEDIUM4.86 | libssl3 3.5.4-r0 fixed in 3.5.7-r0 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-68160 | MEDIUM4.7 | libcrypto3 3.5.4-r0 fixed in 3.5.5-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4.7 | libssl3 3.5.4-r0 fixed in 3.5.5-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM4.68 | libexpat 2.7.3-r0 fixed in 2.7.4-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76957 | MEDIUM4.68 | libexpat 2.7.3-r0 fixed in 2.8.4-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22801 | MEDIUM4.68 | libpng 1.6.47-r0 fixed in 1.6.54-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40200 | MEDIUM4.68 | musl 1.2.5-r10 fixed in 1.2.5-r12 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40200 | MEDIUM4.68 | musl-utils 1.2.5-r10 fixed in 1.2.5-r12 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22184 | MEDIUM4.68 | zlib 1.3.1-r2 fixed in 1.3.2-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15467 | MEDIUM4.58 | openssl 3.5.4-r0 fixed in 3.5.5-r0 | 74.8% Actively Exploited | Post-Exploit |
| CVE-2026-33636 | MEDIUM4.56 | libpng 1.6.47-r0 fixed in 1.6.56-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-1584 | MEDIUM4.5 | gnutls 3.8.8-r0 fixed in 3.8.12-r0 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33846 | MEDIUM4.5 | gnutls 3.8.8-r0 fixed in 3.8.13-r0 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | MEDIUM4.5 | gnutls 3.8.8-r0 fixed in 3.8.13-r0 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-69421 | MEDIUM4.5 | libcrypto3 3.5.4-r0 fixed in 3.5.5-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | libcrypto3 3.5.4-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM4.5 | libcrypto3 3.5.4-r0 fixed in 3.5.6-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM4.5 | libcrypto3 3.5.4-r0 fixed in 3.5.6-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM4.5 | libcrypto3 3.5.4-r0 fixed in 3.5.6-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | libcrypto3 3.5.4-r0 fixed in 3.5.8-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34183 | MEDIUM4.5 | libcrypto3 3.5.4-r0 fixed in 3.5.7-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.5 | libcrypto3 3.5.4-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | libcrypto3 3.5.4-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | libcrypto3 3.5.4-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | libcrypto3 3.5.4-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | libcrypto3 3.5.4-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | libcrypto3 3.5.4-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45186 | MEDIUM4.5 | libexpat 2.7.3-r0 fixed in 2.8.1-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-66046 | MEDIUM4.5 | libexpat 2.7.3-r0 fixed in 2.8.4-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-76641 | MEDIUM4.5 | libexpat 2.7.3-r0 fixed in 2.8.4-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-76956 | MEDIUM4.5 | libexpat 2.7.3-r0 fixed in 2.8.4-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93990 | MEDIUM4.5 | libexpat 2.7.3-r0 fixed in 2.8.5-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33416 | MEDIUM4.5 | libpng 1.6.47-r0 fixed in 1.6.56-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-69421 | MEDIUM4.5 | libssl3 3.5.4-r0 fixed in 3.5.5-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | libssl3 3.5.4-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM4.5 | libssl3 3.5.4-r0 fixed in 3.5.6-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM4.5 | libssl3 3.5.4-r0 fixed in 3.5.6-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM4.5 | libssl3 3.5.4-r0 fixed in 3.5.6-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | libssl3 3.5.4-r0 fixed in 3.5.8-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34183 | MEDIUM4.5 | libssl3 3.5.4-r0 fixed in 3.5.7-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.5 | libssl3 3.5.4-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | libssl3 3.5.4-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | libssl3 3.5.4-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | libssl3 3.5.4-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | libssl3 3.5.4-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | libssl3 3.5.4-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | openssl 3.5.4-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM4.5 | openssl 3.5.4-r0 fixed in 3.5.6-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM4.5 | openssl 3.5.4-r0 fixed in 3.5.6-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM4.5 | openssl 3.5.4-r0 fixed in 3.5.6-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | openssl 3.5.4-r0 fixed in 3.5.8-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34183 | MEDIUM4.5 | openssl 3.5.4-r0 fixed in 3.5.7-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.5 | openssl 3.5.4-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | openssl 3.5.4-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | openssl 3.5.4-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | openssl 3.5.4-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | openssl 3.5.4-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | openssl 3.5.4-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-2100 | MEDIUM4.5 | p11-kit 0.25.5-r2 fixed in 0.26.2-r0 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-2100 | MEDIUM4.5 | p11-kit-trust 0.25.5-r2 fixed in 0.26.2-r0 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34182 | MEDIUM4.44 | libcrypto3 3.5.4-r0 fixed in 3.5.7-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34182 | MEDIUM4.44 | libssl3 3.5.4-r0 fixed in 3.5.7-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-6395 | MEDIUM4.42 | gnutls 3.8.8-r0 fixed in 3.8.12-r0 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-64720 | MEDIUM4.26 | libpng 1.6.47-r0 fixed in 1.6.51-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-65018 | MEDIUM4.26 | libpng 1.6.47-r0 fixed in 1.6.51-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66293 | MEDIUM4.26 | libpng 1.6.47-r0 fixed in 1.6.53-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-22695 | MEDIUM4.26 | libpng 1.6.47-r0 fixed in 1.6.54-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-12243 | MEDIUM4.24 | gnutls 3.8.8-r0 fixed in 3.8.12-r0 | 1.3% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2025-14831 | MEDIUM4.24 | gnutls 3.8.8-r0 fixed in 3.8.12-r0 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-32989 | MEDIUM4.24 | gnutls 3.8.8-r0 fixed in 3.8.12-r0 | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42015 | MEDIUM4.24 | gnutls 3.8.8-r0 fixed in 3.8.13-r0 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-68973 | MEDIUM4.2 | gnupg-dirmngr 2.4.7-r0 fixed in 2.4.9-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56132 | MEDIUM4.14 | libexpat 2.7.3-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM4.14 | libexpat 2.7.3-r0 fixed in 2.8.2-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM4.14 | libexpat 2.7.3-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM4.14 | libexpat 2.7.3-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM4.14 | libexpat 2.7.3-r0 fixed in 2.8.2-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56407 | MEDIUM4.14 | libexpat 2.7.3-r0 fixed in 2.8.2-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56408 | MEDIUM4.14 | libexpat 2.7.3-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56410 | MEDIUM4.14 | libexpat 2.7.3-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56411 | MEDIUM4.14 | libexpat 2.7.3-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | MEDIUM4 | libcrypto3 3.5.4-r0 fixed in 3.5.5-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | MEDIUM4 | libssl3 3.5.4-r0 fixed in 3.5.5-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107891 | MEDIUM4 | musl 1.2.5-r10 fixed in 1.2.5-r13 | — | Directly Exposed |
| CVE-2026-107891 | MEDIUM4 | musl-utils 1.2.5-r10 fixed in 1.2.5-r13 | — | Directly Exposed |
| CVE-2026-2673 | LOW3.9 | libcrypto3 3.5.4-r0 fixed in 3.5.6-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56409 | LOW3.9 | libexpat 2.7.3-r0 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-2673 | LOW3.9 | libssl3 3.5.4-r0 fixed in 3.5.6-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-2673 | LOW3.9 | openssl 3.5.4-r0 fixed in 3.5.6-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | LOW3.78 | libcrypto3 3.5.4-r0 fixed in 3.5.7-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | LOW3.78 | libcrypto3 3.5.4-r0 fixed in 3.5.7-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | LOW3.78 | libssl3 3.5.4-r0 fixed in 3.5.7-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | LOW3.78 | libssl3 3.5.4-r0 fixed in 3.5.7-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.7 | libcrypto3 3.5.4-r0 fixed in 3.5.7-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | libcrypto3 3.5.4-r0 fixed in 3.5.8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.7 | libssl3 3.5.4-r0 fixed in 3.5.7-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | libssl3 3.5.4-r0 fixed in 3.5.8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-64506 | LOW3.66 | libpng 1.6.47-r0 fixed in 1.6.51-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-102633 | LOW3.54 | libexpat 2.7.3-r0 fixed in 2.9.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | LOW3.54 | libexpat 2.7.3-r0 fixed in 2.8.2-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | LOW3.54 | libexpat 2.7.3-r0 fixed in 2.8.2-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46675 | LOW3.54 | libpng 1.6.47-r0 fixed in 1.6.59-r0 | — | Directly Exposed |
| CVE-2025-13151 | LOW3.54 | libtasn1 4.20.0-r0 fixed in 4.21.0-r0 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31790 | LOW3.54 | openssl 3.5.4-r0 fixed in 3.5.6-r0 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42764 | LOW3.54 | openssl 3.5.4-r0 fixed in 3.5.7-r0 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-15468 | LOW3.54 | openssl 3.5.4-r0 fixed in 3.5.5-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-66199 | LOW3.54 | openssl 3.5.4-r0 fixed in 3.5.5-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69420 | LOW3.54 | openssl 3.5.4-r0 fixed in 3.5.5-r0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-22796 | LOW3.54 | openssl 3.5.4-r0 fixed in 3.5.5-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42769 | LOW3.54 | openssl 3.5.4-r0 fixed in 3.5.7-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.54 | openssl 3.5.4-r0 fixed in 3.5.7-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63073 | LOW3.54 | openssl 3.5.4-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-9076 | LOW3.54 | openssl 3.5.4-r0 fixed in 3.5.7-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | LOW3.53 | openssl 3.5.4-r0 fixed in 3.5.6-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-32776 | LOW3.3 | libexpat 2.7.3-r0 fixed in 2.7.5-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | LOW3.3 | libexpat 2.7.3-r0 fixed in 2.7.5-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | LOW3.3 | libexpat 2.7.3-r0 fixed in 2.7.5-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15469 | LOW3.3 | openssl 3.5.4-r0 fixed in 3.5.5-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-22795 | LOW3.3 | openssl 3.5.4-r0 fixed in 3.5.5-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW3.3 | openssl 3.5.4-r0 fixed in 3.5.7-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-27171 | LOW3.3 | zlib 1.3.1-r2 fixed in 1.3.2-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | LOW3.28 | openssl 3.5.4-r0 fixed in 3.5.7-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-40930 | LOW3.24 | libpng 1.6.47-r0 fixed in 1.6.59-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9820 | LOW3.2 | gnutls 3.8.8-r0 fixed in 3.8.12-r0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42766 | LOW3.18 | openssl 3.5.4-r0 fixed in 3.5.7-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42767 | LOW3.18 | openssl 3.5.4-r0 fixed in 3.5.7-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW3 | openssl 3.5.4-r0 fixed in 3.5.7-r0 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-85091 | LOW3 | zlib 1.3.1-r2 fixed in 1.3.2-r1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3832 | LOW2.96 | gnutls 3.8.8-r0 fixed in 3.8.13-r0 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-5419 | LOW2.96 | gnutls 3.8.8-r0 fixed in 3.8.13-r0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-28387 | LOW2.92 | openssl 3.5.4-r0 fixed in 3.5.6-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl 3.5.4-r0 fixed in 3.5.7-r0 | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-68972 | LOW2.82 | gnupg 2.4.7-r0 fixed in 2.4.9-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gnupg-dirmngr 2.4.7-r0 fixed in 2.4.9-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gnupg-gpgconf 2.4.7-r0 fixed in 2.4.9-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gnupg-keyboxd 2.4.7-r0 fixed in 2.4.9-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gnupg-utils 2.4.7-r0 fixed in 2.4.9-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gnupg-wks-client 2.4.7-r0 fixed in 2.4.9-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpg 2.4.7-r0 fixed in 2.4.9-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpg-agent 2.4.7-r0 fixed in 2.4.9-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpg-wks-server 2.4.7-r0 fixed in 2.4.9-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpgsm 2.4.7-r0 fixed in 2.4.9-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpgv 2.4.7-r0 fixed in 2.4.9-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | LOW2.82 | openssl 3.5.4-r0 fixed in 3.5.5-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69421 | LOW2.7 | openssl 3.5.4-r0 fixed in 3.5.5-r0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-56131 | LOW2.7 | libexpat 2.7.3-r0 fixed in 2.8.2-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | LOW2.66 | openssl 3.5.4-r0 fixed in 3.5.7-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-64505 | LOW2.64 | libpng 1.6.47-r0 fixed in 1.6.51-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34757 | LOW2.64 | libpng 1.6.47-r0 fixed in 1.6.57-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58251 | LOW2.55 | busybox 1.37.0-r19 fixed in 1.37.0-r20 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58251 | LOW2.55 | busybox-binsh 1.37.0-r19 fixed in 1.37.0-r20 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58251 | LOW2.55 | ssl_client 1.37.0-r19 fixed in 1.37.0-r20 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW2.52 | gnupg 2.4.7-r0 fixed in 2.4.9-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW2.52 | gnupg-gpgconf 2.4.7-r0 fixed in 2.4.9-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW2.52 | gnupg-keyboxd 2.4.7-r0 fixed in 2.4.9-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW2.52 | gnupg-utils 2.4.7-r0 fixed in 2.4.9-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW2.52 | gnupg-wks-client 2.4.7-r0 fixed in 2.4.9-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW2.52 | gpg 2.4.7-r0 fixed in 2.4.9-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW2.52 | gpg-agent 2.4.7-r0 fixed in 2.4.9-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW2.52 | gpg-wks-server 2.4.7-r0 fixed in 2.4.9-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW2.52 | gpgsm 2.4.7-r0 fixed in 2.4.9-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW2.52 | gpgv 2.4.7-r0 fixed in 2.4.9-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69418 | LOW2.4 | openssl 3.5.4-r0 fixed in 3.5.5-r0 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-34181 | LOW2.27 | openssl 3.5.4-r0 fixed in 3.5.7-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42768 | LOW2.27 | openssl 3.5.4-r0 fixed in 3.5.7-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-41080 | LOW2.22 | libexpat 2.7.3-r0 fixed in 2.8.1-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW2.22 | openssl 3.5.4-r0 fixed in 3.5.7-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-75803 | LOW2.22 | openssl 3.5.4-r0 fixed in 3.5.8-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-46394 | LOW1.68 | busybox 1.37.0-r19 fixed in 1.37.0-r20 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-46394 | LOW1.68 | busybox-binsh 1.37.0-r19 fixed in 1.37.0-r20 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-46394 | LOW1.68 | ssl_client 1.37.0-r19 fixed in 1.37.0-r20 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-24515 | LOW1.5 | libexpat 2.7.3-r0 fixed in 2.7.4-r0 | 0.2% Theoretical Threat | Directly Exposed |
Want to check another image? Run a full scan with the Docker Security Scanner.