Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. The 37 high-severity kernel vulnerabilities could allow an attacker with local access to escalate privileges or corrupt system memory, though they are not remotely exploitable. The only full mitigation is to update the underlying kernel; no compensating control within the container can address these flaws. The image is official and pinned, which provides supply-chain assurance but does not reduce the inherent vulnerability count.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-53398 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-53399 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | — | Directly Exposed |
| CVE-2026-63794 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63795 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63797 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63824 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63829 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63830 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63831 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63970 | HIGH7 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64017 | HIGH7 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64191 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-53366 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-53381 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-53384 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-53388 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-53391 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-53392 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | — | Directly Exposed |
| CVE-2026-53393 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-53397 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63800 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63801 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63802 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63807 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63808 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63809 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63823 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63826 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63940 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63941 | HIGH7 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-63979 | HIGH7 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64024 | HIGH7 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64068 | HIGH7 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64117 | HIGH7 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64160 | HIGH7 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64189 | HIGH7 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | — | Directly Exposed |
| CVE-2026-64192 | HIGH7 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-54512 | MEDIUM6.88 | com.fasterxml.jackson.core:jackson-databind 2.21.3 fixed in 2.18.8, 3.1.4, 2.21.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-54513 | MEDIUM6.88 | com.fasterxml.jackson.core:jackson-databind 2.21.3 fixed in 2.18.8, 2.21.4, 3.1.4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-3847 | MEDIUM6.63 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-21803 | MEDIUM6.63 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-38137 | MEDIUM6.63 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38187 | MEDIUM6.63 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38206 | MEDIUM6.63 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38421 | MEDIUM6.63 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39859 | MEDIUM6.63 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39862 | MEDIUM6.63 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39958 | MEDIUM6.63 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23208 | MEDIUM6.63 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31493 | MEDIUM6.63 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46279 | MEDIUM6.63 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53157 | MEDIUM6.63 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53359 | MEDIUM6.63 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53362 | MEDIUM6.63 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-12456 | MEDIUM6.63 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-11725 | MEDIUM6.63 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-26934 | MEDIUM6.63 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3238 | MEDIUM6.63 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-26242 | MEDIUM6.63 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-3640 | MEDIUM6.63 | linux-libc-dev 6.12.94-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2008-4609 | MEDIUM6.53 | linux-libc-dev 6.12.94-1 No fix yet | 32.1% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2004-0230 | MEDIUM6.5 | linux-libc-dev 6.12.94-1 No fix yet | 80.9% Actively Exploited | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl1 2.3.2-2+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58015 | MEDIUM6.03 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22104 | MEDIUM6.03 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38204 | MEDIUM6.03 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38636 | MEDIUM6.03 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23102 | MEDIUM6.03 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23327 | MEDIUM6.03 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31568 | MEDIUM6.03 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46130 | MEDIUM6.03 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53179 | MEDIUM6.03 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40064 | MEDIUM6.03 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43414 | MEDIUM6.03 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-3864 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-31419 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43198 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46054 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46181 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46242 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52991 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53000 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53091 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53277 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40158 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40168 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46317 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46324 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46325 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46330 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52953 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52956 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53005 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53009 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53078 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53089 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53224 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53246 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53250 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53260 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53341 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53361 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-1247 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-2961 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45884 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45885 | MEDIUM5.95 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.20.0-2 fixed in 4.20.0-2+deb13u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-1121 | MEDIUM5.9 | linux-libc-dev 6.12.94-1 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3714 | MEDIUM5.9 | linux-libc-dev 6.12.94-1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-40130 | MEDIUM5.78 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2020-36694 | MEDIUM5.7 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-6238 | MEDIUM5.7 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49839 | MEDIUM5.61 | libjq1 1.7.1-6+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6240 | MEDIUM5.52 | linux-libc-dev 6.12.94-1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-68729 | MEDIUM5.52 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-0564 | MEDIUM5.52 | linux-libc-dev 6.12.94-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-54518 | MEDIUM5.52 | com.fasterxml.jackson.core:jackson-databind 2.21.3 fixed in 2.21.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-2193 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-53365 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-53394 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-53400 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-53402 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | — | Directly Exposed |
| CVE-2026-63803 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63804 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63822 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63832 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-63858 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64006 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64036 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64038 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64058 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64067 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64076 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64077 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64079 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64159 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64190 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64205 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64206 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-53385 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-53403 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63810 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63821 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63853 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-63872 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-63998 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-63999 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64060 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64066 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64070 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64078 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64146 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 No fix yet | — | Directly Exposed |
| CVE-2026-64187 | MEDIUM5.5 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | — | Directly Exposed |
| CVE-2025-40074 | MEDIUM5.44 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45932 | MEDIUM5.44 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53090 | MEDIUM5.44 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53092 | MEDIUM5.44 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-44032 | MEDIUM5.44 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-44033 | MEDIUM5.44 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl1 2.3.2-2+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM5.35 | libattr1 1:2.5.2-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-3397 | MEDIUM5.35 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.25.5-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40146 | MEDIUM5.27 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | liblastlog2-2 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40355 | MEDIUM5.18 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68319 | MEDIUM5.18 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43197 | MEDIUM5.18 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2010-4563 | MEDIUM5 | linux-libc-dev 6.12.94-1 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-23039 | MEDIUM4.84 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-0630 | MEDIUM4.7 | linux-libc-dev 6.12.94-1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41256 | MEDIUM4.67 | libjq1 1.7.1-6+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41257 | MEDIUM4.67 | libjq1 1.7.1-6+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43894 | MEDIUM4.67 | libjq1 1.7.1-6+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43896 | MEDIUM4.67 | libjq1 1.7.1-6+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44777 | MEDIUM4.67 | libjq1 1.7.1-6+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-47770 | MEDIUM4.67 | libjq1 1.7.1-6+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54679 | MEDIUM4.67 | libjq1 1.7.1-6+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-9403 | MEDIUM4.67 | libjq1 1.7.1-6+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40612 | MEDIUM4.67 | libjq1 1.7.1-6+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31082 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-37454 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-25740 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-52560 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56709 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58074 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58094 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58095 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21752 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21807 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21949 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22108 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22109 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22127 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23131 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23132 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23135 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37743 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37746 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37880 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38029 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38036 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38041 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38042 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38064 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38132 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38140 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38199 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38203 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38205 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38207 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38237 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38261 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38284 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38311 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38359 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38597 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38605 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38621 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39677 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39762 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39775 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39789 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39822 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39830 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39833 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39834 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39910 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39925 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39933 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40102 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68209 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68236 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68304 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68353 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68368 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68730 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71117 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71141 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71188 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71202 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71227 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71285 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71302 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71313 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71315 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23007 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23017 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23137 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23152 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23217 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23259 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23265 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23371 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23377 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23385 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23472 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31435 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31526 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31537 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31562 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31579 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31591 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31592 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31630 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31692 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31732 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31771 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31777 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43009 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43010 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43022 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43029 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43034 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43042 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43048 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43083 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43101 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43115 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43118 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43127 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43172 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43191 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43204 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43213 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43216 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43234 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43272 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43294 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43298 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43299 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43301 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43308 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43309 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43310 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43311 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43325 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43326 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43337 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43344 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43346 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43352 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43353 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43355 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43416 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43443 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43463 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43464 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43465 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43485 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45897 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45901 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45934 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45940 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45944 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45961 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45963 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46014 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46032 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46044 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46059 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46066 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46071 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46093 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46096 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46147 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46148 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46153 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46171 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46228 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46245 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46252 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46256 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46302 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46314 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52937 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52944 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52975 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52988 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52994 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53017 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53018 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53027 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53070 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53101 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53102 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53103 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53108 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53109 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53118 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53139 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53142 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53151 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53163 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53167 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53226 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53258 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53281 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53285 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53292 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53297 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53313 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53321 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53325 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2008-2544 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2011-4915 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-4916 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2011-4917 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2014-9892 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2014-9900 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2016-10723 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-8660 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-13693 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-13694 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12928 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12378 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12379 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12380 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-12381 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12382 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-12455 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-4543 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-31081 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31085 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40086 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68193 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68359 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53104 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53106 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53113 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53284 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53327 | MEDIUM4.67 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1337 | MEDIUM4.59 | org.neo4j:neo4j 5.26.28 fixed in 2026.01 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libblkid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | liblastlog2-2 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.8.1-1 fixed in 5.8.1-1+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libsmartcols1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libuuid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54514 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.21.3 fixed in 2.18.8, 2.21.4, 3.1.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54515 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.21.3 fixed in 3.1.4, 2.18.9, 2.21.5, 2.22.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54516 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.21.3 fixed in 2.21.4, 3.1.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54517 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.21.3 fixed in 2.21.4, 3.1.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54515 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.22.0 fixed in 3.1.4, 2.18.9, 2.21.5, 2.22.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-40217 | MEDIUM4.42 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40338 | MEDIUM4.42 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2005-3660 | MEDIUM4.17 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | liblastlog2-2 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-20794 | MEDIUM4 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-24864 | MEDIUM4 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37906 | MEDIUM4 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40139 | MEDIUM4 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68745 | MEDIUM4 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71074 | MEDIUM4 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23348 | MEDIUM4 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43053 | MEDIUM4 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46017 | MEDIUM4 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46272 | MEDIUM4 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-16230 | MEDIUM4 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16234 | MEDIUM4 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-69720 | LOW3.98 | ncurses-bin 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2019-15213 | LOW3.91 | linux-libc-dev 6.12.94-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4010 | LOW3.91 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2012-4542 | LOW3.91 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | LOW3.82 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-68360 | LOW3.82 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43895 | LOW3.74 | libjq1 1.7.1-6+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2020-14304 | LOW3.74 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-17977 | LOW3.74 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2011-3374 | LOW3.7 | libapt-pkg7.0 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-31879 | LOW3.66 | wget 1.25.0-2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2010-5321 | LOW3.65 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58471 | LOW3.62 | wget 1.25.0-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-58472 | LOW3.62 | wget 1.25.0-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 1.35+dfsg-3.1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-41848 | LOW3.57 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-16089 | LOW3.48 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16229 | LOW3.48 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16231 | LOW3.48 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16232 | LOW3.48 | linux-libc-dev 6.12.94-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-16233 | LOW3.48 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-49839 | LOW3.37 | jq 1.7.1-6+deb13u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW3.31 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-base 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-58469 | LOW3.31 | wget 1.25.0-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | perl-base 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2019-1010024 | LOW3.18 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010025 | LOW3.18 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-bin 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW3.02 | perl-base 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-5435 | LOW3.01 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15146 | LOW3.01 | wget 1.25.0-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2020-35501 | LOW2.89 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-7445 | LOW2.81 | linux-libc-dev 6.12.94-1 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19449 | LOW2.81 | linux-libc-dev 6.12.94-1 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19814 | LOW2.81 | linux-libc-dev 6.12.94-1 No fix yet | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19378 | LOW2.81 | linux-libc-dev 6.12.94-1 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-25265 | LOW2.81 | linux-libc-dev 6.12.94-1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41256 | LOW2.8 | jq 1.7.1-6+deb13u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41257 | LOW2.8 | jq 1.7.1-6+deb13u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43894 | LOW2.8 | jq 1.7.1-6+deb13u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43896 | LOW2.8 | jq 1.7.1-6+deb13u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-44777 | LOW2.8 | jq 1.7.1-6+deb13u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-47770 | LOW2.8 | jq 1.7.1-6+deb13u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-54679 | LOW2.8 | jq 1.7.1-6+deb13u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-9403 | LOW2.8 | jq 1.7.1-6+deb13u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-40612 | LOW2.8 | jq 1.7.1-6+deb13u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.35+dfsg-3.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-70873 | LOW2.8 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2015-2877 | LOW2.8 | linux-libc-dev 6.12.94-1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-68751 | LOW2.8 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | LOW2.78 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc-bin 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9192 | LOW2.7 | libc-bin 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9192 | LOW2.7 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc6 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9192 | LOW2.7 | libc6 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc6-dev 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9192 | LOW2.7 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19070 | LOW2.7 | linux-libc-dev 6.12.94-1 No fix yet | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-0400 | LOW2.7 | linux-libc-dev 6.12.94-1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | bsdutils 1:2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | mount 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58470 | LOW2.7 | wget 1.25.0-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5450 | LOW2.55 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5928 | LOW2.55 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.7-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.13-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2010-4756 | LOW2.4 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-41992 | LOW2.29 | gzip 1.13-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.7-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43895 | LOW2.24 | jq 1.7.1-6+deb13u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-40113 | LOW2.12 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-11191 | LOW2.12 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2007-3719 | LOW1.78 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | ncurses-bin 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2007-5686 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.37-2+b9 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53010 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40098 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68735 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52983 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | — | Not Applicable |
| CVE-2026-53377 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | — | Not Applicable |
| CVE-2026-53382 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-53383 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-53386 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-53387 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-53389 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-53390 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | — | Not Applicable |
| CVE-2026-63796 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-63798 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | — | Not Applicable |
| CVE-2026-63806 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-63811 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | — | Not Applicable |
| CVE-2026-63812 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-63814 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-63815 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | — | Not Applicable |
| CVE-2026-63816 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | — | Not Applicable |
| CVE-2026-63817 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-63818 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | — | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | — | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | — | Not Applicable |
| CVE-2026-63827 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-63828 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-63833 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-63834 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-63835 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-63836 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-63857 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | — | Not Applicable |
| CVE-2026-63859 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | — | Not Applicable |
| CVE-2026-63879 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | — | Not Applicable |
| CVE-2026-64082 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | — | Not Applicable |
| CVE-2026-64154 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | — | Not Applicable |
| CVE-2026-64188 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | — | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | — | Not Applicable |
| CVE-2026-64600 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | — | Not Applicable |
| CVE-2026-53615 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login.defs 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 3.14-4 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.35+dfsg-3.1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| GHSA-r7wm-3cxj-wff9 | NONE0 | com.fasterxml.jackson.core:jackson-core 2.21.3 fixed in 2.18.8, 2.21.4, 2.22.1 | — | Not Applicable |
| GHSA-r7wm-3cxj-wff9 | NONE0 | com.fasterxml.jackson.core:jackson-core 2.22.0 fixed in 2.18.8, 2.21.4, 2.22.1 | — | Not Applicable |
| CVE-2026-59888 | NONE0 | com.fasterxml.jackson.core:jackson-databind 2.21.3 fixed in 2.18.8, 2.21.4 | — | Not Applicable |
| CVE-2026-59889 | NONE0 | com.fasterxml.jackson.core:jackson-databind 2.21.3 fixed in 2.21.5, 2.18.9, 2.22.1 | — | Not Applicable |
| GHSA-mhm7-754m-9p8w | NONE0 | com.fasterxml.jackson.core:jackson-databind 2.21.3 fixed in 2.18.9, 2.21.5 | — | Not Applicable |
| CVE-2026-59889 | NONE0 | com.fasterxml.jackson.core:jackson-databind 2.22.0 fixed in 2.21.5, 2.18.9, 2.22.1 | — | 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.