Last scanned:
··This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker who reaches the VPN port could exploit CVE-2023-46850 to corrupt memory or run code on the server, gaining a foothold on the host network it serves and potentially disrupting or tapping VPN traffic. The title places this flaw in OpenVPN 2.6.0 to 2.6.6, while the installed package is 2.4.9-r0, so the match must be confirmed, but the scan still flags it as a critical finding and the base OS no longer receives security fixes. Do not deploy this image in production.
Hardening plan for this image · 4 steps
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2023-46850 | CRITICAL9.8 | openvpn 2.4.9-r0 fixed in 2.6.7-r0 | 2.0% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2023-46850 | CRITICAL9.8 | openvpn-auth-pam 2.4.9-r0 fixed in 2.6.7-r0 | 2.0% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2022-0547 | HIGH7.84 | openvpn 2.4.9-r0 fixed in 2.5.6-r0 | 3.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-0547 | HIGH7.84 | openvpn-auth-pam 2.4.9-r0 fixed in 2.5.6-r0 | 3.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-0286 | HIGH7.7 | libcrypto1.1 1.1.1g-r0 fixed in 3.0.8-r0 | 69.3% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-0286 | HIGH7.7 | libssl1.1 1.1.1g-r0 fixed in 3.0.8-r0 | 69.3% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-0286 | HIGH7.7 | openssl 1.1.1g-r0 fixed in 3.0.8-r0 | 69.3% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2020-15078 | HIGH7.5 | openvpn 2.4.9-r0 fixed in 2.5.2-r0 | 4.9% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2023-46849 | HIGH7.5 | openvpn 2.4.9-r0 fixed in 2.6.7-r0 | 1.1% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2025-13086 | HIGH7.5 | openvpn 2.4.9-r0 fixed in 2.6.16-r0 | 0.7% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-11771 | HIGH7.5 | openvpn 2.4.9-r0 fixed in 2.7.5-r0 | 0.4% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-13698 | HIGH7.5 | openvpn 2.4.9-r0 fixed in 2.7.5-r0 | 0.5% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-84732 | HIGH7.5 | openvpn 2.4.9-r0 fixed in 2.7.7-r0 | 0.3% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2020-15078 | HIGH7.5 | openvpn-auth-pam 2.4.9-r0 fixed in 2.5.2-r0 | 4.9% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2023-46849 | HIGH7.5 | openvpn-auth-pam 2.4.9-r0 fixed in 2.6.7-r0 | 1.1% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2025-13086 | HIGH7.5 | openvpn-auth-pam 2.4.9-r0 fixed in 2.6.16-r0 | 0.7% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-11771 | HIGH7.5 | openvpn-auth-pam 2.4.9-r0 fixed in 2.7.5-r0 | 0.4% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-13698 | HIGH7.5 | openvpn-auth-pam 2.4.9-r0 fixed in 2.7.5-r0 | 0.5% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-84732 | HIGH7.5 | openvpn-auth-pam 2.4.9-r0 fixed in 2.7.7-r0 | 0.3% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-40215 | HIGH7.4 | openvpn 2.4.9-r0 fixed in 2.6.20-r0 | 0.4% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-40215 | HIGH7.4 | openvpn-auth-pam 2.4.9-r0 fixed in 2.6.20-r0 | 0.4% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2021-3450 | MEDIUM6.81 | libcrypto1.1 1.1.1g-r0 fixed in 1.1.1k-r0 | 18.3% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2021-3450 | MEDIUM6.81 | libssl1.1 1.1.1g-r0 fixed in 1.1.1k-r0 | 18.3% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2021-3450 | MEDIUM6.81 | openssl 1.1.1g-r0 fixed in 1.1.1k-r0 | 18.3% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-4304 | MEDIUM6.79 | libcrypto1.1 1.1.1g-r0 fixed in 3.0.8-r0 | 23.5% High Exploitation Risk | Directly Exposed |
| CVE-2022-4304 | MEDIUM6.79 | libssl1.1 1.1.1g-r0 fixed in 3.0.8-r0 | 23.5% High Exploitation Risk | Directly Exposed |
| CVE-2023-2650 | MEDIUM6.76 | libcrypto1.1 1.1.1g-r0 fixed in 3.1.1-r0 | 73.7% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-2650 | MEDIUM6.76 | libssl1.1 1.1.1g-r0 fixed in 3.1.1-r0 | 73.7% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-2650 | MEDIUM6.76 | openssl 1.1.1g-r0 fixed in 3.1.1-r0 | 73.7% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-6129 | MEDIUM6.5 | libcrypto1.1 1.1.1g-r0 fixed in 3.1.4-r3 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-2673 | MEDIUM6.5 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.6-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-6129 | MEDIUM6.5 | libssl1.1 1.1.1g-r0 fixed in 3.1.4-r3 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-2673 | MEDIUM6.5 | libssl1.1 1.1.1g-r0 fixed in 3.5.6-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-35058 | MEDIUM6.5 | openvpn 2.4.9-r0 fixed in 2.6.20-r0 | 0.5% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-35058 | MEDIUM6.5 | openvpn-auth-pam 2.4.9-r0 fixed in 2.6.20-r0 | 0.5% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-12932 | MEDIUM6.48 | openvpn 2.4.9-r0 fixed in 2.7.5-r0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-12996 | MEDIUM6.48 | openvpn 2.4.9-r0 fixed in 2.7.5-r0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-13117 | MEDIUM6.48 | openvpn 2.4.9-r0 fixed in 2.7.5-r0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-12932 | MEDIUM6.48 | openvpn-auth-pam 2.4.9-r0 fixed in 2.7.5-r0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-12996 | MEDIUM6.48 | openvpn-auth-pam 2.4.9-r0 fixed in 2.7.5-r0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-13117 | MEDIUM6.48 | openvpn-auth-pam 2.4.9-r0 fixed in 2.7.5-r0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-34181 | MEDIUM6.3 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM6.3 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM6.3 | libssl1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM6.3 | libssl1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-3449 | MEDIUM6.14 | libcrypto1.1 1.1.1g-r0 fixed in 1.1.1k-r0 | 63.5% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2021-3449 | MEDIUM6.14 | libssl1.1 1.1.1g-r0 fixed in 1.1.1k-r0 | 63.5% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2021-3449 | MEDIUM6.14 | openssl 1.1.1g-r0 fixed in 1.1.1k-r0 | 63.5% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2025-11187 | MEDIUM6.1 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.5-r0 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-11187 | MEDIUM6.1 | libssl1.1 1.1.1g-r0 fixed in 3.5.5-r0 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-3094 | MEDIUM6 | xz-libs 5.2.5-r0 fixed in 5.6.1-r2 | 90.9% Actively Exploited | Directly Exposed |
| CVE-2021-3711 | MEDIUM6 | libcrypto1.1 1.1.1g-r0 fixed in 1.1.1l-r0 | 87.8% Actively Exploited | Directly Exposed |
| CVE-2025-15467 | MEDIUM6 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.5-r0 | 74.8% Actively Exploited | Directly Exposed |
| CVE-2021-3711 | MEDIUM6 | libssl1.1 1.1.1g-r0 fixed in 1.1.1l-r0 | 87.8% Actively Exploited | Directly Exposed |
| CVE-2025-15467 | MEDIUM6 | libssl1.1 1.1.1g-r0 fixed in 3.5.5-r0 | 74.8% Actively Exploited | Directly Exposed |
| CVE-2022-37434 | MEDIUM6 | zlib 1.2.11-r3 fixed in 1.2.12-r2 | 19.2% High Exploitation Risk | Directly Exposed |
| CVE-2022-3996 | MEDIUM6 | libcrypto1.1 1.1.1g-r0 fixed in 3.0.7-r2 | 1.3% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-3996 | MEDIUM6 | libssl1.1 1.1.1g-r0 fixed in 3.0.7-r2 | 1.3% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-3996 | MEDIUM6 | openssl 1.1.1g-r0 fixed in 3.0.7-r2 | 1.3% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2025-26519 | MEDIUM5.95 | musl 1.1.24-r9 fixed in 1.2.5-r10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-1971 | MEDIUM5.9 | libcrypto1.1 1.1.1g-r0 fixed in 1.1.1i-r0 | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-23841 | MEDIUM5.9 | libcrypto1.1 1.1.1g-r0 fixed in 1.1.1j-r0 | 7.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1434 | MEDIUM5.9 | libcrypto1.1 1.1.1g-r0 fixed in 3.0.3-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9231 | MEDIUM5.9 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.4-r0 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.6-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6237 | MEDIUM5.9 | libcrypto1.1 1.1.1g-r0 fixed in 3.1.4-r4 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | libcrypto1.1 1.1.1g-r0 fixed in 3.3.1-r1 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-15468 | MEDIUM5.9 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.5-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-66199 | MEDIUM5.9 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.5-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.9 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.5-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.9 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.5-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.9 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.9 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.9 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2020-1971 | MEDIUM5.9 | libssl1.1 1.1.1g-r0 fixed in 1.1.1i-r0 | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-23841 | MEDIUM5.9 | libssl1.1 1.1.1g-r0 fixed in 1.1.1j-r0 | 7.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1434 | MEDIUM5.9 | libssl1.1 1.1.1g-r0 fixed in 3.0.3-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9231 | MEDIUM5.9 | libssl1.1 1.1.1g-r0 fixed in 3.5.4-r0 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | libssl1.1 1.1.1g-r0 fixed in 3.5.6-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | libssl1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6237 | MEDIUM5.9 | libssl1.1 1.1.1g-r0 fixed in 3.1.4-r4 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | libssl1.1 1.1.1g-r0 fixed in 3.3.1-r1 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-15468 | MEDIUM5.9 | libssl1.1 1.1.1g-r0 fixed in 3.5.5-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-66199 | MEDIUM5.9 | libssl1.1 1.1.1g-r0 fixed in 3.5.5-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.9 | libssl1.1 1.1.1g-r0 fixed in 3.5.5-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.9 | libssl1.1 1.1.1g-r0 fixed in 3.5.5-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.9 | libssl1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.9 | libssl1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | libssl1.1 1.1.1g-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.9 | libssl1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | MEDIUM5.88 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.6-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | MEDIUM5.88 | libssl1.1 1.1.1g-r0 fixed in 3.5.6-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2020-27780 | MEDIUM5.88 | linux-pam 1.3.1-r4 fixed in 1.5.1-r0 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-23840 | MEDIUM5.85 | libcrypto1.1 1.1.1g-r0 fixed in 1.1.1j-r0 | 50.7% Actively Exploited | Directly Exposed |
| CVE-2021-4044 | MEDIUM5.85 | libcrypto1.1 1.1.1g-r0 fixed in 3.0.1-r0 | 50.1% Actively Exploited | Directly Exposed |
| CVE-2022-0778 | MEDIUM5.85 | libcrypto1.1 1.1.1g-r0 fixed in 3.0.2-r0 | 73.2% Actively Exploited | Directly Exposed |
| CVE-2022-3602 | MEDIUM5.85 | libcrypto1.1 1.1.1g-r0 fixed in 3.0.7-r0 | 90.8% Actively Exploited | Directly Exposed |
| CVE-2022-3786 | MEDIUM5.85 | libcrypto1.1 1.1.1g-r0 fixed in 3.0.7-r0 | 92.5% Actively Exploited | Directly Exposed |
| CVE-2024-6119 | MEDIUM5.85 | libcrypto1.1 1.1.1g-r0 fixed in 3.3.2-r0 | 66.6% Actively Exploited | Directly Exposed |
| CVE-2021-23840 | MEDIUM5.85 | libssl1.1 1.1.1g-r0 fixed in 1.1.1j-r0 | 50.7% Actively Exploited | Directly Exposed |
| CVE-2021-4044 | MEDIUM5.85 | libssl1.1 1.1.1g-r0 fixed in 3.0.1-r0 | 50.1% Actively Exploited | Directly Exposed |
| CVE-2022-0778 | MEDIUM5.85 | libssl1.1 1.1.1g-r0 fixed in 3.0.2-r0 | 73.2% Actively Exploited | Directly Exposed |
| CVE-2022-3602 | MEDIUM5.85 | libssl1.1 1.1.1g-r0 fixed in 3.0.7-r0 | 90.8% Actively Exploited | Directly Exposed |
| CVE-2022-3786 | MEDIUM5.85 | libssl1.1 1.1.1g-r0 fixed in 3.0.7-r0 | 92.5% Actively Exploited | Directly Exposed |
| CVE-2024-6119 | MEDIUM5.85 | libssl1.1 1.1.1g-r0 fixed in 3.3.2-r0 | 66.6% Actively Exploited | Directly Exposed |
| CVE-2022-3602 | MEDIUM5.85 | openssl 1.1.1g-r0 fixed in 3.0.7-r0 | 90.8% Actively Exploited | Directly Exposed |
| CVE-2022-3786 | MEDIUM5.85 | openssl 1.1.1g-r0 fixed in 3.0.7-r0 | 92.5% Actively Exploited | Directly Exposed |
| CVE-2018-25032 | MEDIUM5.85 | zlib 1.2.11-r3 fixed in 1.2.11-r4 | 51.7% Actively Exploited | Directly Exposed |
| CVE-2021-3712 | MEDIUM5.77 | libcrypto1.1 1.1.1g-r0 fixed in 1.1.1l-r0 | 50.4% Actively Exploited | Directly Exposed |
| CVE-2021-3712 | MEDIUM5.77 | libssl1.1 1.1.1g-r0 fixed in 1.1.1l-r0 | 50.4% Actively Exploited | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.4-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | libcrypto1.1 1.1.1g-r0 fixed in 3.3.0-r3 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | libssl1.1 1.1.1g-r0 fixed in 3.5.4-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | libssl1.1 1.1.1g-r0 fixed in 3.3.0-r3 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-4575 | MEDIUM5.52 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.1-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-4575 | MEDIUM5.52 | libssl1.1 1.1.1g-r0 fixed in 3.5.1-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libcrypto1.1 1.1.1g-r0 fixed in 3.1.4-r5 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-15469 | MEDIUM5.5 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.5-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM5.5 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.5-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM5.5 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libssl1.1 1.1.1g-r0 fixed in 3.1.4-r5 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-15469 | MEDIUM5.5 | libssl1.1 1.1.1g-r0 fixed in 3.5.5-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM5.5 | libssl1.1 1.1.1g-r0 fixed in 3.5.5-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM5.5 | libssl1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-6042 | MEDIUM5.5 | musl 1.1.24-r9 fixed in 1.2.6-r1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | MEDIUM5.46 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | MEDIUM5.46 | libssl1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-1343 | MEDIUM5.3 | libcrypto1.1 1.1.1g-r0 fixed in 3.0.3-r0 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2097 | MEDIUM5.3 | libcrypto1.1 1.1.1g-r0 fixed in 3.0.5-r0 | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0465 | MEDIUM5.3 | libcrypto1.1 1.1.1g-r0 fixed in 3.1.0-r2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3446 | MEDIUM5.3 | libcrypto1.1 1.1.1g-r0 fixed in 3.1.1-r3 | 6.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3817 | MEDIUM5.3 | libcrypto1.1 1.1.1g-r0 fixed in 3.1.2-r0 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | libcrypto1.1 1.1.1g-r0 fixed in 3.1.4-r1 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4603 | MEDIUM5.3 | libcrypto1.1 1.1.1g-r0 fixed in 3.3.0-r2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42766 | MEDIUM5.3 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42767 | MEDIUM5.3 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-1343 | MEDIUM5.3 | libssl1.1 1.1.1g-r0 fixed in 3.0.3-r0 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2097 | MEDIUM5.3 | libssl1.1 1.1.1g-r0 fixed in 3.0.5-r0 | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0465 | MEDIUM5.3 | libssl1.1 1.1.1g-r0 fixed in 3.1.0-r2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3446 | MEDIUM5.3 | libssl1.1 1.1.1g-r0 fixed in 3.1.1-r3 | 6.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3817 | MEDIUM5.3 | libssl1.1 1.1.1g-r0 fixed in 3.1.2-r0 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | libssl1.1 1.1.1g-r0 fixed in 3.1.4-r1 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4603 | MEDIUM5.3 | libssl1.1 1.1.1g-r0 fixed in 3.3.0-r2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42766 | MEDIUM5.3 | libssl1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42767 | MEDIUM5.3 | libssl1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-13122 | MEDIUM5.3 | openvpn 2.4.9-r0 fixed in 2.7.5-r0 | 0.5% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-13122 | MEDIUM5.3 | openvpn-auth-pam 2.4.9-r0 fixed in 2.7.5-r0 | 0.5% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2022-1271 | MEDIUM5.28 | xz-libs 5.2.5-r0 fixed in 5.2.5-r1 | 5.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-1255 | MEDIUM5.02 | libcrypto1.1 1.1.1g-r0 fixed in 3.1.0-r4 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-1255 | MEDIUM5.02 | libssl1.1 1.1.1g-r0 fixed in 3.1.0-r4 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | libssl1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-4203 | MEDIUM4.9 | libcrypto1.1 1.1.1g-r0 fixed in 3.0.8-r0 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-4203 | MEDIUM4.9 | libssl1.1 1.1.1g-r0 fixed in 3.0.8-r0 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-25646 | MEDIUM4.86 | libpng 1.6.37-r1 fixed in 1.6.55-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | libcrypto1.1 1.1.1g-r0 fixed in 3.2.1-r2 | 52.4% Actively Exploited | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | libssl1.1 1.1.1g-r0 fixed in 3.2.1-r2 | 52.4% Actively Exploited | Directly Exposed |
| CVE-2025-68160 | MEDIUM4.7 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.5-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4.7 | libssl1.1 1.1.1g-r0 fixed in 3.5.5-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22801 | MEDIUM4.68 | libpng 1.6.37-r1 fixed in 1.6.54-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40200 | MEDIUM4.68 | musl 1.1.24-r9 fixed in 1.2.6-r2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22184 | MEDIUM4.68 | zlib 1.2.11-r3 fixed in 1.3.2-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-22365 | MEDIUM4.67 | linux-pam 1.3.1-r4 fixed in 1.6.0-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-28928 | MEDIUM4.67 | musl 1.1.24-r9 fixed in 1.2.2_pre2-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-3711 | MEDIUM4.58 | openssl 1.1.1g-r0 fixed in 1.1.1l-r0 | 87.8% Actively Exploited | Post-Exploit |
| CVE-2025-15467 | MEDIUM4.58 | openssl 1.1.1g-r0 fixed in 3.5.5-r0 | 74.8% Actively Exploited | Post-Exploit |
| CVE-2026-33636 | MEDIUM4.56 | libpng 1.6.37-r1 fixed in 1.6.56-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-30139 | MEDIUM4.5 | apk-tools 2.10.5-r1 fixed in 2.12.5-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0464 | MEDIUM4.5 | libcrypto1.1 1.1.1g-r0 fixed in 3.1.0-r1 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-69421 | MEDIUM4.5 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.5-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM4.5 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.6-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.8-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34183 | MEDIUM4.5 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33416 | MEDIUM4.5 | libpng 1.6.37-r1 fixed in 1.6.56-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0464 | MEDIUM4.5 | libssl1.1 1.1.1g-r0 fixed in 3.1.0-r1 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-69421 | MEDIUM4.5 | libssl1.1 1.1.1g-r0 fixed in 3.5.5-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | libssl1.1 1.1.1g-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM4.5 | libssl1.1 1.1.1g-r0 fixed in 3.5.6-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | libssl1.1 1.1.1g-r0 fixed in 3.5.8-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34183 | MEDIUM4.5 | libssl1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | libssl1.1 1.1.1g-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | libssl1.1 1.1.1g-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | libssl1.1 1.1.1g-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | libssl1.1 1.1.1g-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | libssl1.1 1.1.1g-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-0464 | MEDIUM4.5 | openssl 1.1.1g-r0 fixed in 3.1.0-r1 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28388 | MEDIUM4.5 | openssl 1.1.1g-r0 fixed in 3.5.6-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-2975 | MEDIUM4.5 | libcrypto1.1 1.1.1g-r0 fixed in 3.1.1-r2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-2975 | MEDIUM4.5 | libssl1.1 1.1.1g-r0 fixed in 3.1.1-r2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-12797 | MEDIUM4.44 | libcrypto1.1 1.1.1g-r0 fixed in 3.3.3-r0 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-69419 | MEDIUM4.44 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.5-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-12797 | MEDIUM4.44 | libssl1.1 1.1.1g-r0 fixed in 3.3.3-r0 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-69419 | MEDIUM4.44 | libssl1.1 1.1.1g-r0 fixed in 3.5.5-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-42378 | MEDIUM4.32 | busybox 1.31.1-r19 fixed in 1.34.0-r0 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42379 | MEDIUM4.32 | busybox 1.31.1-r19 fixed in 1.34.0-r0 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42380 | MEDIUM4.32 | busybox 1.31.1-r19 fixed in 1.34.0-r0 | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42381 | MEDIUM4.32 | busybox 1.31.1-r19 fixed in 1.34.0-r0 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42382 | MEDIUM4.32 | busybox 1.31.1-r19 fixed in 1.34.0-r0 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42383 | MEDIUM4.32 | busybox 1.31.1-r19 fixed in 1.34.0-r0 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42384 | MEDIUM4.32 | busybox 1.31.1-r19 fixed in 1.34.0-r0 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42385 | MEDIUM4.32 | busybox 1.31.1-r19 fixed in 1.34.0-r0 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42386 | MEDIUM4.32 | busybox 1.31.1-r19 fixed in 1.34.0-r0 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42378 | MEDIUM4.32 | ssl_client 1.31.1-r19 fixed in 1.34.0-r0 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42379 | MEDIUM4.32 | ssl_client 1.31.1-r19 fixed in 1.34.0-r0 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42380 | MEDIUM4.32 | ssl_client 1.31.1-r19 fixed in 1.34.0-r0 | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42381 | MEDIUM4.32 | ssl_client 1.31.1-r19 fixed in 1.34.0-r0 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42382 | MEDIUM4.32 | ssl_client 1.31.1-r19 fixed in 1.34.0-r0 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42383 | MEDIUM4.32 | ssl_client 1.31.1-r19 fixed in 1.34.0-r0 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42384 | MEDIUM4.32 | ssl_client 1.31.1-r19 fixed in 1.34.0-r0 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42385 | MEDIUM4.32 | ssl_client 1.31.1-r19 fixed in 1.34.0-r0 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42386 | MEDIUM4.32 | ssl_client 1.31.1-r19 fixed in 1.34.0-r0 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-64720 | MEDIUM4.26 | libpng 1.6.37-r1 fixed in 1.6.51-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-65018 | MEDIUM4.26 | libpng 1.6.37-r1 fixed in 1.6.51-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66293 | MEDIUM4.26 | libpng 1.6.37-r1 fixed in 1.6.53-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-22695 | MEDIUM4.26 | libpng 1.6.37-r1 fixed in 1.6.54-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-29458 | MEDIUM4.26 | ncurses-libs 6.2_p20200523-r0 fixed in 6.3_p20220416-r0 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29458 | MEDIUM4.26 | ncurses-terminfo-base 6.2_p20200523-r0 fixed in 6.3_p20220416-r0 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28882 | MEDIUM4.25 | openvpn 2.4.9-r0 fixed in 2.6.11-r0 | 0.7% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2024-5594 | MEDIUM4.25 | openvpn 2.4.9-r0 fixed in 2.6.11-r0 | 0.8% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2025-2704 | MEDIUM4.25 | openvpn 2.4.9-r0 fixed in 2.6.14-r0 | 0.8% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2024-28882 | MEDIUM4.25 | openvpn-auth-pam 2.4.9-r0 fixed in 2.6.11-r0 | 0.7% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2024-5594 | MEDIUM4.25 | openvpn-auth-pam 2.4.9-r0 fixed in 2.6.11-r0 | 0.8% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2025-2704 | MEDIUM4.25 | openvpn-auth-pam 2.4.9-r0 fixed in 2.6.14-r0 | 0.8% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2022-4304 | MEDIUM4.07 | openssl 1.1.1g-r0 fixed in 3.0.8-r0 | 23.5% High Exploitation Risk | Post-Exploit |
| CVE-2024-13176 | MEDIUM4 | libcrypto1.1 1.1.1g-r0 fixed in 3.3.2-r5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | libssl1.1 1.1.1g-r0 fixed in 3.3.2-r5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | MEDIUM4 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.5-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | MEDIUM4 | libssl1.1 1.1.1g-r0 fixed in 3.5.5-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107891 | MEDIUM4 | musl 1.1.24-r9 fixed in 1.2.6-r6 | — | Directly Exposed |
| CVE-2023-29491 | LOW3.98 | ncurses-libs 6.2_p20200523-r0 fixed in 6.4_p20230424-r0 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-29491 | LOW3.98 | ncurses-terminfo-base 6.2_p20200523-r0 fixed in 6.4_p20230424-r0 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-6129 | LOW3.9 | openssl 1.1.1g-r0 fixed in 3.1.4-r3 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-2673 | LOW3.9 | openssl 1.1.1g-r0 fixed in 3.5.6-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-31115 | LOW3.83 | xz-libs 5.2.5-r0 fixed in 5.8.1-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | LOW3.78 | openssl 1.1.1g-r0 fixed in 3.5.7-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42768 | LOW3.78 | openssl 1.1.1g-r0 fixed in 3.5.7-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2021-23839 | LOW3.7 | libcrypto1.1 1.1.1g-r0 fixed in 1.1.1j-r0 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-9143 | LOW3.7 | libcrypto1.1 1.1.1g-r0 fixed in 3.3.2-r3 | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45446 | LOW3.7 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-23839 | LOW3.7 | libssl1.1 1.1.1g-r0 fixed in 1.1.1j-r0 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-9143 | LOW3.7 | libssl1.1 1.1.1g-r0 fixed in 3.3.2-r3 | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45446 | LOW3.7 | libssl1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | libssl1.1 1.1.1g-r0 fixed in 3.5.8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-64506 | LOW3.66 | libpng 1.6.37-r1 fixed in 1.6.51-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11187 | LOW3.66 | openssl 1.1.1g-r0 fixed in 3.5.5-r0 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-26519 | LOW3.57 | musl-utils 1.1.24-r9 fixed in 1.2.5-r10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-46675 | LOW3.54 | libpng 1.6.37-r1 fixed in 1.6.59-r0 | — | Directly Exposed |
| CVE-2020-1971 | LOW3.54 | openssl 1.1.1g-r0 fixed in 1.1.1i-r0 | 7.0% Low-Moderate Risk | Post-Exploit |
| CVE-2021-23841 | LOW3.54 | openssl 1.1.1g-r0 fixed in 1.1.1j-r0 | 7.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1434 | LOW3.54 | openssl 1.1.1g-r0 fixed in 3.0.3-r0 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-9231 | LOW3.54 | openssl 1.1.1g-r0 fixed in 3.5.4-r0 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-31790 | LOW3.54 | openssl 1.1.1g-r0 fixed in 3.5.6-r0 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42764 | LOW3.54 | openssl 1.1.1g-r0 fixed in 3.5.7-r0 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6237 | LOW3.54 | openssl 1.1.1g-r0 fixed in 3.1.4-r4 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-5535 | LOW3.54 | openssl 1.1.1g-r0 fixed in 3.3.1-r1 | 5.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-15468 | LOW3.54 | openssl 1.1.1g-r0 fixed in 3.5.5-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-66199 | LOW3.54 | openssl 1.1.1g-r0 fixed in 3.5.5-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69420 | LOW3.54 | openssl 1.1.1g-r0 fixed in 3.5.5-r0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-22796 | LOW3.54 | openssl 1.1.1g-r0 fixed in 3.5.5-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42769 | LOW3.54 | openssl 1.1.1g-r0 fixed in 3.5.7-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.54 | openssl 1.1.1g-r0 fixed in 3.5.7-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63073 | LOW3.54 | openssl 1.1.1g-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-9076 | LOW3.54 | openssl 1.1.1g-r0 fixed in 3.5.7-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2022-48174 | LOW3.53 | busybox 1.31.1-r19 fixed in 1.36.1-r2 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-31789 | LOW3.53 | openssl 1.1.1g-r0 fixed in 3.5.6-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48174 | LOW3.53 | ssl_client 1.31.1-r19 fixed in 1.36.1-r2 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2021-23840 | LOW3.51 | openssl 1.1.1g-r0 fixed in 1.1.1j-r0 | 50.7% Actively Exploited | Post-Exploit |
| CVE-2021-4044 | LOW3.51 | openssl 1.1.1g-r0 fixed in 3.0.1-r0 | 50.1% Actively Exploited | Post-Exploit |
| CVE-2022-0778 | LOW3.51 | openssl 1.1.1g-r0 fixed in 3.0.2-r0 | 73.2% Actively Exploited | Post-Exploit |
| CVE-2024-6119 | LOW3.51 | openssl 1.1.1g-r0 fixed in 3.3.2-r0 | 66.6% Actively Exploited | Post-Exploit |
| CVE-2021-3712 | LOW3.46 | openssl 1.1.1g-r0 fixed in 1.1.1l-r0 | 50.4% Actively Exploited | Post-Exploit |
| CVE-2025-9230 | LOW3.36 | openssl 1.1.1g-r0 fixed in 3.5.4-r0 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4741 | LOW3.36 | openssl 1.1.1g-r0 fixed in 3.3.0-r3 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-4575 | LOW3.31 | openssl 1.1.1g-r0 fixed in 3.5.1-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6042 | LOW3.3 | musl-utils 1.1.24-r9 fixed in 1.2.6-r1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-0727 | LOW3.3 | openssl 1.1.1g-r0 fixed in 3.1.4-r5 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-15469 | LOW3.3 | openssl 1.1.1g-r0 fixed in 3.5.5-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-22795 | LOW3.3 | openssl 1.1.1g-r0 fixed in 3.5.5-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW3.3 | openssl 1.1.1g-r0 fixed in 3.5.7-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-27171 | LOW3.3 | zlib 1.2.11-r3 fixed in 1.3.2-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-36159 | LOW3.28 | apk-tools 2.10.5-r1 fixed in 2.12.6-r0 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45445 | LOW3.28 | openssl 1.1.1g-r0 fixed in 3.5.7-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-40930 | LOW3.24 | libpng 1.6.37-r1 fixed in 1.6.58-r1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-1343 | LOW3.18 | openssl 1.1.1g-r0 fixed in 3.0.3-r0 | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2097 | LOW3.18 | openssl 1.1.1g-r0 fixed in 3.0.5-r0 | 4.9% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0465 | LOW3.18 | openssl 1.1.1g-r0 fixed in 3.1.0-r2 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-3446 | LOW3.18 | openssl 1.1.1g-r0 fixed in 3.1.1-r3 | 6.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-3817 | LOW3.18 | openssl 1.1.1g-r0 fixed in 3.1.2-r0 | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5678 | LOW3.18 | openssl 1.1.1g-r0 fixed in 3.1.4-r1 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4603 | LOW3.18 | openssl 1.1.1g-r0 fixed in 3.3.0-r2 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42766 | LOW3.18 | openssl 1.1.1g-r0 fixed in 3.5.7-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42767 | LOW3.18 | openssl 1.1.1g-r0 fixed in 3.5.7-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-34743 | LOW3.18 | xz-libs 5.2.5-r0 fixed in 5.8.3-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-28391 | LOW3.17 | busybox 1.31.1-r19 fixed in 1.35.0-r7 | 3.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-39537 | LOW3.17 | ncurses-libs 6.2_p20200523-r0 fixed in 6.2_p20200530-r0 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2021-39537 | LOW3.17 | ncurses-terminfo-base 6.2_p20200523-r0 fixed in 6.2_p20200530-r0 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-28391 | LOW3.17 | ssl_client 1.31.1-r19 fixed in 1.35.0-r7 | 3.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-4450 | LOW3.1 | libcrypto1.1 1.1.1g-r0 fixed in 3.0.8-r0 | 28.6% High Exploitation Risk | Post-Exploit |
| CVE-2022-4450 | LOW3.1 | libssl1.1 1.1.1g-r0 fixed in 3.0.8-r0 | 28.6% High Exploitation Risk | Post-Exploit |
| CVE-2022-4450 | LOW3.1 | openssl 1.1.1g-r0 fixed in 3.0.8-r0 | 28.6% High Exploitation Risk | Post-Exploit |
| CVE-2025-9232 | LOW3.1 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.4-r0 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9232 | LOW3.1 | libssl1.1 1.1.1g-r0 fixed in 3.5.4-r0 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-1255 | LOW3.01 | openssl 1.1.1g-r0 fixed in 3.1.0-r4 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW3 | openssl 1.1.1g-r0 fixed in 3.5.7-r0 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-85091 | LOW3 | zlib 1.2.11-r3 fixed in 1.3.2-r1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-4203 | LOW2.94 | openssl 1.1.1g-r0 fixed in 3.0.8-r0 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28387 | LOW2.92 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.6-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28387 | LOW2.92 | libssl1.1 1.1.1g-r0 fixed in 3.5.6-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | libssl1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28387 | LOW2.92 | openssl 1.1.1g-r0 fixed in 3.5.6-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl 1.1.1g-r0 fixed in 3.5.7-r0 | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2511 | LOW2.89 | openssl 1.1.1g-r0 fixed in 3.2.1-r2 | 52.4% Actively Exploited | Post-Exploit |
| CVE-2025-68160 | LOW2.82 | openssl 1.1.1g-r0 fixed in 3.5.5-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-30065 | LOW2.81 | busybox 1.31.1-r19 fixed in 1.35.0-r17 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-40200 | LOW2.81 | musl-utils 1.1.24-r9 fixed in 1.2.6-r2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-30065 | LOW2.81 | ssl_client 1.31.1-r19 fixed in 1.35.0-r17 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42375 | LOW2.8 | busybox 1.31.1-r19 fixed in 1.34.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42363 | LOW2.8 | busybox 1.31.1-r19 fixed in 1.36.1-r27 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42364 | LOW2.8 | busybox 1.31.1-r19 fixed in 1.36.1-r30 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42365 | LOW2.8 | busybox 1.31.1-r19 fixed in 1.36.1-r30 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42366 | LOW2.8 | busybox 1.31.1-r19 fixed in 1.36.1-r25 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2020-28928 | LOW2.8 | musl-utils 1.1.24-r9 fixed in 1.2.2_pre2-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-42375 | LOW2.8 | ssl_client 1.31.1-r19 fixed in 1.34.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42363 | LOW2.8 | ssl_client 1.31.1-r19 fixed in 1.36.1-r27 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42364 | LOW2.8 | ssl_client 1.31.1-r19 fixed in 1.36.1-r30 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42365 | LOW2.8 | ssl_client 1.31.1-r19 fixed in 1.36.1-r30 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42366 | LOW2.8 | ssl_client 1.31.1-r19 fixed in 1.36.1-r25 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-28831 | LOW2.7 | busybox 1.31.1-r19 fixed in 1.33.0-r5 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1473 | LOW2.7 | libcrypto1.1 1.1.1g-r0 fixed in 3.0.3-r0 | 4.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-3358 | LOW2.7 | libcrypto1.1 1.1.1g-r0 fixed in 3.0.6-r0 | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0215 | LOW2.7 | libcrypto1.1 1.1.1g-r0 fixed in 3.0.8-r0 | 5.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0216 | LOW2.7 | libcrypto1.1 1.1.1g-r0 fixed in 3.0.8-r0 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0217 | LOW2.7 | libcrypto1.1 1.1.1g-r0 fixed in 3.0.8-r0 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0401 | LOW2.7 | libcrypto1.1 1.1.1g-r0 fixed in 3.0.8-r0 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5363 | LOW2.7 | libcrypto1.1 1.1.1g-r0 fixed in 3.1.4-r0 | 3.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28389 | LOW2.7 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.6-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | LOW2.7 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.6-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-63072 | LOW2.7 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-1473 | LOW2.7 | libssl1.1 1.1.1g-r0 fixed in 3.0.3-r0 | 4.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-3358 | LOW2.7 | libssl1.1 1.1.1g-r0 fixed in 3.0.6-r0 | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0215 | LOW2.7 | libssl1.1 1.1.1g-r0 fixed in 3.0.8-r0 | 5.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0216 | LOW2.7 | libssl1.1 1.1.1g-r0 fixed in 3.0.8-r0 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0217 | LOW2.7 | libssl1.1 1.1.1g-r0 fixed in 3.0.8-r0 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0401 | LOW2.7 | libssl1.1 1.1.1g-r0 fixed in 3.0.8-r0 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5363 | LOW2.7 | libssl1.1 1.1.1g-r0 fixed in 3.1.4-r0 | 3.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28389 | LOW2.7 | libssl1.1 1.1.1g-r0 fixed in 3.5.6-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | LOW2.7 | libssl1.1 1.1.1g-r0 fixed in 3.5.6-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-63072 | LOW2.7 | libssl1.1 1.1.1g-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-1473 | LOW2.7 | openssl 1.1.1g-r0 fixed in 3.0.3-r0 | 4.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-3358 | LOW2.7 | openssl 1.1.1g-r0 fixed in 3.0.6-r0 | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0215 | LOW2.7 | openssl 1.1.1g-r0 fixed in 3.0.8-r0 | 5.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0216 | LOW2.7 | openssl 1.1.1g-r0 fixed in 3.0.8-r0 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0217 | LOW2.7 | openssl 1.1.1g-r0 fixed in 3.0.8-r0 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0401 | LOW2.7 | openssl 1.1.1g-r0 fixed in 3.0.8-r0 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5363 | LOW2.7 | openssl 1.1.1g-r0 fixed in 3.1.4-r0 | 3.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-69421 | LOW2.7 | openssl 1.1.1g-r0 fixed in 3.5.5-r0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-14456 | LOW2.7 | openssl 1.1.1g-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-28389 | LOW2.7 | openssl 1.1.1g-r0 fixed in 3.5.6-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | LOW2.7 | openssl 1.1.1g-r0 fixed in 3.5.6-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-18798 | LOW2.7 | openssl 1.1.1g-r0 fixed in 3.5.8-r0 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34183 | LOW2.7 | openssl 1.1.1g-r0 fixed in 3.5.7-r0 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63072 | LOW2.7 | openssl 1.1.1g-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-63076 | LOW2.7 | openssl 1.1.1g-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-14457 | LOW2.7 | openssl 1.1.1g-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-54874 | LOW2.7 | openssl 1.1.1g-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63074 | LOW2.7 | openssl 1.1.1g-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63075 | LOW2.7 | openssl 1.1.1g-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2021-28831 | LOW2.7 | ssl_client 1.31.1-r19 fixed in 1.33.0-r5 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42374 | LOW2.7 | busybox 1.31.1-r19 fixed in 1.34.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-2975 | LOW2.7 | openssl 1.1.1g-r0 fixed in 3.1.1-r2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2021-42374 | LOW2.7 | ssl_client 1.31.1-r19 fixed in 1.34.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW2.66 | libcrypto1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34182 | LOW2.66 | libssl1.1 1.1.1g-r0 fixed in 3.5.7-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-12797 | LOW2.66 | openssl 1.1.1g-r0 fixed in 3.3.3-r0 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-69419 | LOW2.66 | openssl 1.1.1g-r0 fixed in 3.5.5-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW2.66 | openssl 1.1.1g-r0 fixed in 3.5.7-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-64505 | LOW2.64 | libpng 1.6.37-r1 fixed in 1.6.51-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34757 | LOW2.64 | libpng 1.6.37-r1 fixed in 1.6.57-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58251 | LOW2.55 | busybox 1.31.1-r19 fixed in 1.37.0-r24 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58251 | LOW2.55 | ssl_client 1.31.1-r19 fixed in 1.37.0-r24 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-13176 | LOW2.4 | openssl 1.1.1g-r0 fixed in 3.3.2-r5 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-107891 | LOW2.4 | musl-utils 1.1.24-r9 fixed in 1.2.6-r6 | — | Post-Exploit |
| CVE-2025-69418 | LOW2.4 | openssl 1.1.1g-r0 fixed in 3.5.5-r0 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-23839 | LOW2.22 | openssl 1.1.1g-r0 fixed in 1.1.1j-r0 | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2024-9143 | LOW2.22 | openssl 1.1.1g-r0 fixed in 3.3.2-r3 | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45446 | LOW2.22 | openssl 1.1.1g-r0 fixed in 3.5.7-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-75803 | LOW2.22 | openssl 1.1.1g-r0 fixed in 3.5.8-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-9232 | LOW1.86 | openssl 1.1.1g-r0 fixed in 3.5.4-r0 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-46394 | LOW1.68 | busybox 1.31.1-r19 fixed in 1.37.0-r27 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-46394 | LOW1.68 | ssl_client 1.31.1-r19 fixed in 1.37.0-r27 | 0.2% Theoretical Threat | Post-Exploit |
Want to check another image? Run a full scan with the Docker Security Scanner.