This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker could exploit request smuggling to poison caches or bypass security controls, and cause denial of service via decompression bomb attacks. The post-exploit findings are low severity and do not add practical risk in this context. Applying network segmentation and using a Web Application Firewall that normalizes HTTP headers can mitigate the request smuggling risks.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-42581 | HIGH8.33 | io.netty:netty-codec-http 4.1.127.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.4% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.31-13+deb11u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.31-13+deb11u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33560 | HIGH7.5 | libgcrypt20 1.8.7-6 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20838 | HIGH7.5 | libpcre3 2:8.39-13 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-4899 | HIGH7.5 | libzstd1 1.4.8+dfsg-2.1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-44249 | MEDIUM6.88 | io.netty:netty-handler 4.1.127.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | MEDIUM6.38 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-33870 | MEDIUM6.38 | io.netty:netty-codec-http 4.1.127.Final fixed in 4.1.132.Final, 4.2.10.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42587 | MEDIUM6.38 | io.netty:netty-codec-http 4.1.127.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42585 | MEDIUM6.38 | io.netty:netty-codec-http 4.1.127.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45416 | MEDIUM6.38 | io.netty:netty-handler 4.1.127.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-50010 | MEDIUM6.38 | io.netty:netty-handler 4.1.127.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34480 | MEDIUM6.38 | org.apache.logging.log4j:log4j-core 2.17.1 fixed in 2.25.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-5588 | MEDIUM6.38 | org.bouncycastle:bcpkix-jdk18on 1.78 fixed in 1.84 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5598 | MEDIUM6.38 | org.bouncycastle:bcprov-jdk18on 1.78 fixed in 1.84 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-7245 | MEDIUM6.24 | libpcre3 2:8.39-13 No fix yet | 2.2% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-7246 | MEDIUM6.24 | libpcre3 2:8.39-13 No fix yet | 2.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2020-13529 | MEDIUM6.1 | libsystemd0 247.3-7+deb11u8 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-13529 | MEDIUM6.1 | libudev1 247.3-7+deb11u8 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | MEDIUM6 | libgssapi-krb5-2 1.18.3-6+deb11u8 No fix yet | 2.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2018-5709 | MEDIUM6 | libk5crypto3 1.18.3-6+deb11u8 No fix yet | 2.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2018-5709 | MEDIUM6 | libkrb5-3 1.18.3-6+deb11u8 No fix yet | 2.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2018-5709 | MEDIUM6 | libkrb5support0 1.18.3-6+deb11u8 No fix yet | 2.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11164 | MEDIUM6 | libpcre3 2:8.39-13 No fix yet | 3.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-4806 | MEDIUM5.9 | libc-bin 2.31-13+deb11u14 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc-bin 2.31-13+deb11u14 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc6 2.31-13+deb11u14 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc6 2.31-13+deb11u14 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.8.7-6 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssapi-krb5-2 1.18.3-6+deb11u8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libk5crypto3 1.18.3-6+deb11u8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-3 1.18.3-6+deb11u8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5support0 1.18.3-6+deb11u8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.16.0-2+deb11u2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30 3.7.1-5+deb11u10 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.31-13+deb11u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.31-13+deb11u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-67735 | MEDIUM5.52 | io.netty:netty-codec-http 4.1.127.Final fixed in 4.2.8.Final, 4.1.129.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41417 | MEDIUM5.52 | io.netty:netty-codec-http 4.1.127.Final fixed in 4.1.133.Final, 4.2.13.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42580 | MEDIUM5.52 | io.netty:netty-codec-http 4.1.127.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0636 | MEDIUM5.52 | org.bouncycastle:bcprov-jdk18on 1.78 fixed in 1.84 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-11143 | MEDIUM5.52 | org.eclipse.jetty:jetty-http 9.4.57.v20241219 fixed in 12.0.31, 12.1.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.31-13+deb11u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.31-13+deb11u14 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.31-13+deb11u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.31-13+deb11u14 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.31-13+deb11u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.31-13+deb11u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.18.3-6+deb11u8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.18.3-6+deb11u8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.18.3-6+deb11u8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.18.3-6+deb11u8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl1.1 1.1.1w-0+deb11u7 fixed in 1.1.1w-0+deb11u8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34477 | MEDIUM5.02 | org.apache.logging.log4j:log4j-core 2.17.1 fixed in 2.25.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-16231 | MEDIUM4.67 | libpcre3 2:8.39-13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl1.1 1.1.1w-0+deb11u7 fixed in 1.1.1w-0+deb11u8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.2.11.dfsg-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1622 | MEDIUM4.67 | org.neo4j:neo4j 4.4.48 fixed in 5.26.21, 2026.01.3 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1337 | MEDIUM4.59 | org.neo4j:neo4j 4.4.48 fixed in 2026.01 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.2.5-2.1~deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | libssl1.1 1.1.1w-0+deb11u7 fixed in 1.1.1w-0+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 247.3-7+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 247.3-7+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 247.3-7+deb11u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 247.3-7+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 247.3-7+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 247.3-7+deb11u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-50020 | MEDIUM4.5 | io.netty:netty-codec-http 4.1.127.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8916 | MEDIUM4.5 | org.bouncycastle:bcpkix-jdk18on 1.78 fixed in 1.79 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-6763 | MEDIUM4.5 | org.eclipse.jetty:jetty-http 9.4.57.v20241219 fixed in 12.0.12 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.31-13+deb11u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.31-13+deb11u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.31-13+deb11u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.31-13+deb11u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssapi-krb5-2 1.18.3-6+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libk5crypto3 1.18.3-6+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-3 1.18.3-6+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5support0 1.18.3-6+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM4.25 | libssl1.1 1.1.1w-0+deb11u7 fixed in 1.1.1w-0+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libgcc-s1 10.2.1-6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libstdc++6 10.2.1-6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-68161 | MEDIUM4.08 | org.apache.logging.log4j:log4j-core 2.17.1 fixed in 2.25.3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2019-8457 | MEDIUM4.06 | libdb5.3 5.3.28+dfsg1-0.8 No fix yet | 45.4% High Exploitation Risk | Post-Exploit |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.31-13+deb11u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.31-13+deb11u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3715 | LOW3.98 | bash 5.1-2+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW3.7 | libapt-pkg6.0 2.2.4 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2005-2541 | LOW3.6 | tar 1.34+dfsg-1+deb11u1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.31-13+deb11u14 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.31-13+deb11u14 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-45853 | LOW3.53 | zlib1g 1:1.2.11.dfsg-2+deb11u2 No fix yet | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45536 | LOW3.4 | io.netty:netty-transport-native-epoll 4.1.127.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2016-2781 | LOW3.31 | coreutils 8.32-4+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.7-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-bin 2.31-13+deb11u14 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6 2.31-13+deb11u14 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 1.1.1w-0+deb11u7 fixed in 1.1.1w-0+deb11u8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | libssl1.1 1.1.1w-0+deb11u7 fixed in 1.1.1w-0+deb11u8 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl 1.1.1w-0+deb11u7 fixed in 1.1.1w-0+deb11u8 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | LOW2.92 | perl-base 5.32.1-4+deb11u5 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43894 | LOW2.8 | jq 1.6-2.1+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-9403 | LOW2.8 | jq 1.6-2.1+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-40612 | LOW2.8 | jq 1.6-2.1+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 1.1.1w-0+deb11u7 fixed in 1.1.1w-0+deb11u8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.34+dfsg-1+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-4016 | LOW2.8 | libprocps8 2:3.3.17-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 247.3-7+deb11u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 247.3-7+deb11u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 247.3-7+deb11u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 247.3-7+deb11u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | LOW2.78 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42584 | LOW2.78 | io.netty:netty-codec-http 4.1.127.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-2332 | LOW2.78 | org.eclipse.jetty:jetty-http 9.4.57.v20241219 fixed in 12.1.7, 12.0.33 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc-bin 2.31-13+deb11u14 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc6 2.31-13+deb11u14 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6829 | LOW2.7 | libgcrypt20 1.8.7-6 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 1.1.1w-0+deb11u7 fixed in 1.1.1w-0+deb11u8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW2.55 | openssl 1.1.1w-0+deb11u7 fixed in 1.1.1w-0+deb11u8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | login 1:4.8.1-1+deb11u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.8.1-1+deb11u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 8.32-4+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2013-4235 | LOW2.4 | login 1:4.8.1-1+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2013-4235 | LOW2.4 | passwd 1:4.8.1-1+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-10524 | LOW2.34 | wget 1.21-1+deb11u2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42497 | LOW2.29 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW2.29 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 8.32-4+b1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 2.2.4 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2021-31879 | LOW2.2 | wget 1.21-1+deb11u2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-23901 | LOW2.12 | org.apache.shiro:shiro-core 1.13.0 fixed in 2.1.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-23337 | LOW1.99 | jq 1.6-2.1+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | login 1:4.8.1-1+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.8.1-1+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4016 | LOW1.68 | procps 2:3.3.17-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2019-1010022 | NONE0 | libc-dev-bin 2.31-13+deb11u14 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc6-dev 2.31-13+deb11u14 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc-dev-bin 2.31-13+deb11u14 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc6-dev 2.31-13+deb11u14 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-47659 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-8805 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-69720 | NONE0 | libncurses6 6.2+20201114-2+deb11u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncursesw6 6.2+20201114-2+deb11u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.2+20201114-2+deb11u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-19449 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-12362 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-3847 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-47014 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47028 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47200 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47653 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0500 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48626 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48674 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49359 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49470 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49635 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49722 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49935 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49980 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50050 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50070 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50151 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50163 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50256 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50300 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50378 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50406 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50492 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50518 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50552 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52452 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52494 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52531 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52624 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52664 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52916 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53039 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53072 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53111 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53218 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53282 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53432 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53473 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53510 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53544 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53577 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53596 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53673 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-21803 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-23307 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-26589 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26792 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26865 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26913 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26914 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26996 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35863 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35864 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35868 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35887 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35932 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36880 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36898 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36914 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38545 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38556 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38570 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38581 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38630 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38667 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40927 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41069 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42118 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42147 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42160 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42271 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43900 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44934 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44941 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44942 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44949 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44986 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45026 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46729 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46811 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46813 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46830 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46859 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46871 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47691 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47695 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47745 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49924 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49950 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49989 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49991 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49992 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50051 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50063 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50067 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50125 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50217 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50282 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53068 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53165 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53168 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53179 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53213 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53218 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56538 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56551 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56604 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56609 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56614 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56640 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56651 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56775 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57798 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57849 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58034 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58093 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58240 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21734 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21780 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21812 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21855 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21863 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21927 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22083 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37786 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37849 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37903 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37928 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-37991 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38068 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38069 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38117 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38129 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38250 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38257 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38259 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38280 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38361 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38369 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38422 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38527 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38584 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38585 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38595 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38685 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38702 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38734 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39686 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39790 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39797 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39810 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39863 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39873 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39952 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40149 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71073 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71078 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71082 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71089 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71152 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23068 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23111 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23221 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23231 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-23361 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23378 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23447 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23448 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31489 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31500 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31527 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31532 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31576 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31578 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31580 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31581 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31583 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31686 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31688 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31696 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31702 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31715 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31729 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43049 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43250 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46004 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46047 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46163 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46180 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46189 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46219 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46234 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46241 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46267 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46274 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-12456 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-11725 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-25265 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-22995 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3640 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.2+20201114-2+deb11u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.2+20201114-2+deb11u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-20796 | NONE0 | libc-dev-bin 2.31-13+deb11u14 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc-dev-bin 2.31-13+deb11u14 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20796 | NONE0 | libc6-dev 2.31-13+deb11u14 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc6-dev 2.31-13+deb11u14 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-32256 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-42225 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-49997 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-43501 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43110 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-19070 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-40170 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31607 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-53781 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-4204 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2021-47101 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3566 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49172 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49218 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49234 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49289 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49444 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49509 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49623 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49961 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50026 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50255 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50306 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-52588 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52682 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52766 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53254 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-26669 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35939 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36915 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41013 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41014 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41935 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46774 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49861 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53147 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57945 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57982 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21985 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22104 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22107 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37879 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38159 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38502 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38679 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38728 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39685 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39744 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39901 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40082 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23099 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23204 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23315 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43052 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43281 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45957 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45994 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46022 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46033 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46191 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53751 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-25742 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-25743 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36013 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-53216 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40064 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68324 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31685 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43126 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46056 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46120 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46135 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46150 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46209 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-4609 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 32.1% High Exploitation Risk | Not Applicable |
| CVE-2021-32078 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-47094 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-6610 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-39686 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-52586 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42162 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47747 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50061 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57876 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39759 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39826 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71221 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23191 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31419 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31663 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43125 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43198 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43329 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43494 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45858 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46053 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46054 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46090 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46099 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46116 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46227 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46319 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49328 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57984 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40135 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40158 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40168 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23050 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23392 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31408 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31586 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31694 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43116 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43491 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43493 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45840 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45892 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45894 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45942 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46043 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46052 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46069 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46119 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46132 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46133 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46149 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46266 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46275 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46294 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45884 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23054 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-24023 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-15794 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2020-36694 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-50616 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53095 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57795 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21714 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26828 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-50851 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21759 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 7.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-45991 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc-dev-bin 2.31-13+deb11u14 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc6-dev 2.31-13+deb11u14 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-23337 | NONE0 | libjq1 1.6-2.1+deb11u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libncurses6 6.2+20201114-2+deb11u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libncursesw6 6.2+20201114-2+deb11u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libtinfo6 6.2+20201114-2+deb11u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-1192 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-6240 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-36968 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47693 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-31588 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.2+20201114-2+deb11u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-bin 6.2+20201114-2+deb11u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-3567 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-21823 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40074 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31502 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31516 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-44032 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44033 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44034 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-1280 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-3397 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26830 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57893 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40307 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40918 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-50764 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54081 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53840 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53850 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40080 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40279 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68342 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68343 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31449 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31464 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31700 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31708 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52481 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4806 | NONE0 | libc-dev-bin 2.31-13+deb11u14 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-4813 | NONE0 | libc-dev-bin 2.31-13+deb11u14 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-5435 | NONE0 | libc-dev-bin 2.31-13+deb11u14 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-4806 | NONE0 | libc6-dev 2.31-13+deb11u14 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-4813 | NONE0 | libc6-dev 2.31-13+deb11u14 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-5435 | NONE0 | libc6-dev 2.31-13+deb11u14 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50666 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-32253 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-54048 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35870 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40242 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-50635 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40323 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68742 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23239 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23240 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23271 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31392 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31414 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31426 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43279 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46065 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46113 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49138 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-49569 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46024 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-23039 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54251 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43894 | NONE0 | libjq1 1.6-2.1+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-9403 | NONE0 | libjq1 1.6-2.1+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40612 | NONE0 | libjq1 1.6-2.1+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40347 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68307 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-12363 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-12364 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-24504 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-33061 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-4023 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-4149 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-46926 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46937 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47036 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47105 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47182 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47188 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47199 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47205 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47211 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47212 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47265 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47275 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47366 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47381 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47410 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47448 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47452 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47504 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47508 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47552 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47558 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47582 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47610 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47618 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47622 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47658 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0480 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3108 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3114 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3344 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-38457 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-40133 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-48628 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48633 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48645 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48673 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48703 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48721 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48765 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48811 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48814 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48833 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48859 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48862 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48887 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48901 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48902 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48920 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48944 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48952 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48961 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48975 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48979 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49004 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49034 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49069 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49096 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49102 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49106 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49109 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49110 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49112 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49123 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49124 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49128 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49132 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49134 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49135 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49142 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49157 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49158 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49160 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49161 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49164 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49169 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49173 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49178 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49182 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49183 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49214 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49226 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49246 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49266 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49285 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49294 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49296 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49306 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49311 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49317 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49325 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49342 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49390 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49398 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49420 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49428 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49437 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49440 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49469 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49496 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49504 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49513 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49528 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49531 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49533 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49534 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49536 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49543 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49562 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49563 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49564 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49566 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49591 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49610 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49616 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49617 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49622 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49650 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49651 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49654 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49666 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49742 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49758 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49764 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49765 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49766 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49801 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49803 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49822 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49828 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49829 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49837 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49858 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49898 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49901 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49932 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49938 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-49997 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50000 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50009 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50011 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50015 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50016 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50023 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50053 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50060 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50073 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50086 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50098 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50100 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50111 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50114 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50116 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50120 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50144 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50159 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50166 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50167 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50224 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50233 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50236 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50260 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50266 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50267 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50293 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50304 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50316 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50335 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50380 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50390 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50392 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50393 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50399 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50407 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50418 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50420 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50428 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50445 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50461 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50469 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50472 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50493 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50500 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50527 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50539 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50541 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50550 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50554 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50627 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50642 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50746 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50772 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50822 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50871 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0597 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-37454 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-4133 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-4569 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52485 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52590 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52591 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52593 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52610 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52625 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52629 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52652 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52660 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52671 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52676 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52677 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52680 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52700 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52732 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52761 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52762 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52763 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52808 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52815 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52834 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52878 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52888 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52913 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52918 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52920 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52939 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53002 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53008 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53010 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53042 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53055 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53068 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53074 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53091 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53093 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53103 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53105 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53133 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53149 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53152 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53200 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53221 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53231 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53244 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53248 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53250 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53261 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53270 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53287 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53332 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53335 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53347 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53348 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53353 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53355 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53367 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53370 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53383 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53393 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53415 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53421 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53429 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53438 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53441 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53458 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53460 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53466 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53470 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53476 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53482 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53491 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53499 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53509 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53513 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53529 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53538 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53539 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53540 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53545 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53562 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53574 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53579 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53584 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53588 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53594 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53597 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53602 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53618 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53620 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53627 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53635 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53647 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53651 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53661 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53682 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53685 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53753 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53765 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53780 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53806 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53822 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53829 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53846 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53849 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53856 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54013 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54028 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54129 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54271 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-2193 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-25740 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26584 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26595 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26656 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26668 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26677 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26680 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26691 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26700 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26706 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26715 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26718 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26726 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26740 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26756 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26759 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26795 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26807 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26844 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26866 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26876 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26893 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26896 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26920 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26947 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26948 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27002 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27010 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27011 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27012 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27014 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27032 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27034 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27035 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27037 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27054 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27056 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27062 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27389 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27402 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27403 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35784 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35794 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35799 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35803 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35808 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35817 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35826 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35839 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35840 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35844 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35875 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35904 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35924 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35931 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35938 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35945 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35951 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35956 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35971 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35995 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36000 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36009 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36023 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36029 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36244 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36478 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36479 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36897 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36917 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36922 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36924 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36951 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36969 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-37021 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38543 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38553 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38554 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38564 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38594 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38602 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38608 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38620 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38632 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39472 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39490 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39507 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40910 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40911 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40915 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40965 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40966 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40967 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40969 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40972 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40973 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40977 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40998 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40999 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41001 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41002 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41008 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41023 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41036 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41048 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41062 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41079 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41082 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41088 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41093 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42063 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42068 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42080 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42098 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42110 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42122 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42128 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42129 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42252 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42267 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42296 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42319 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42321 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43817 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43819 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43823 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43824 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43831 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43832 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43872 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-43899 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43901 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43902 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43904 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43909 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43912 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44939 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44950 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44958 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44963 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44969 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44982 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45009 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45015 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45828 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46678 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46681 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46715 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46716 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46720 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46726 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46727 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46728 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46730 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46732 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46733 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46752 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46754 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46760 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46761 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46765 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46770 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46772 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46773 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46775 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46776 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46802 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46806 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46807 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46808 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46810 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46826 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46832 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46834 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46848 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46857 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46860 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47141 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47408 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47658 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47661 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47662 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47665 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47667 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47669 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47673 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47678 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47683 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47690 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47703 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47704 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47720 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47728 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47794 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47809 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49568 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49891 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49893 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49897 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49898 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49899 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49901 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49905 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49906 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49908 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49910 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49911 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49912 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49914 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49915 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49916 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49917 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49918 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49919 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49920 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49921 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49922 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49923 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49925 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49927 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49929 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49940 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49945 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49954 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49970 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49978 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50002 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50003 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50017 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50028 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50038 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50060 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50062 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50138 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50166 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50168 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50187 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50196 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50256 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50258 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50272 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50289 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50298 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52559 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53051 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53058 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53079 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53090 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53093 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53094 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53114 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53122 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53128 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53187 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53190 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53195 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53196 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53210 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53219 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53220 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53221 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53224 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53234 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-54683 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56369 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56544 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56557 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56565 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56566 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56583 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56588 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56590 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56591 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56592 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56611 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56641 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56647 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56692 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56703 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56712 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56715 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56718 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56722 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56746 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56776 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56777 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56778 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56785 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56787 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57809 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57872 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57888 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57897 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57903 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57924 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57939 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57975 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57976 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58012 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58053 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58089 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58094 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58095 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58096 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58097 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58098 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58100 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58237 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58241 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21629 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21634 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21635 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21656 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21682 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21690 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21696 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21712 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21738 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21750 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21758 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 10.6% High Exploitation Risk | Not Applicable |
| CVE-2025-21766 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21768 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21792 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21801 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21816 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21820 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21831 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21838 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21839 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21866 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21881 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21885 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21891 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21894 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21899 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21931 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21976 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22026 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22028 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22053 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22057 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22071 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22072 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22073 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22090 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22103 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22125 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22127 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23130 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23131 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23161 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37742 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37758 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37800 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37807 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37820 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37833 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37834 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37842 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37852 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37853 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37883 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37911 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37925 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37951 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37959 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37961 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37967 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37980 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38014 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38040 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38057 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38059 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38062 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38063 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38080 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38096 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38097 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38105 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38125 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38126 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38127 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38148 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38162 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38166 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38192 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38215 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38262 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38264 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38272 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38300 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38310 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38319 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38331 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38333 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38362 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38408 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38409 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38410 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38426 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38436 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38438 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38449 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38491 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38499 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38544 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38576 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38590 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38614 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38623 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38624 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38626 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38630 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38643 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38644 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38645 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38659 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38665 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38692 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38696 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38705 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38709 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38710 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38716 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39675 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39684 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39693 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39705 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39706 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39707 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39716 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39732 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39746 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39747 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39763 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39770 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39772 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39773 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39800 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39801 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39819 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39827 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39829 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39833 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39850 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39851 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39925 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39929 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39931 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39932 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39940 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40005 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40075 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40102 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40104 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40160 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40164 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40339 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68188 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68223 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68231 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68283 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68340 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68358 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68379 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71081 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71083 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71109 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71121 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71160 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71161 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71183 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71184 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71188 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71268 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71269 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71272 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71273 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71287 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71297 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71305 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23019 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23031 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23066 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23069 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23086 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23088 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23137 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23138 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23141 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23154 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23157 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23213 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23247 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23255 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23267 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23272 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23276 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23278 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23287 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23292 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23296 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23330 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23340 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23374 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23389 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23442 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23444 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23449 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23465 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23468 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31407 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31412 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31420 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31441 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31446 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31448 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31451 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31453 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31462 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31487 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31496 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31503 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31519 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31521 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31531 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31540 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31548 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31560 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31577 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31585 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31590 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31596 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31599 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31603 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31605 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31606 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31615 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31616 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31617 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31618 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31619 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31623 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31624 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31625 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31630 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31634 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31637 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31642 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31664 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31673 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31675 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31676 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31677 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31678 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31681 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31684 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31698 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31699 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31701 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31722 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31723 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31724 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31725 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31754 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31755 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31767 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43025 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43036 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43046 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43058 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43071 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43073 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43080 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43085 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43088 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43089 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43091 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43093 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43103 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43104 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43105 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43107 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43111 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43113 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43114 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43119 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43123 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43143 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43153 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43162 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43167 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43182 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43216 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43219 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43225 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43244 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43262 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43271 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43288 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43302 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43313 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43317 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43318 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43338 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43350 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43359 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43361 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43362 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43409 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43413 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43421 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43456 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43492 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43502 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45834 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45835 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45836 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45838 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45841 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45842 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45843 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45844 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45846 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45855 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45944 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45981 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45986 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45987 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45988 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45993 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45997 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46000 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46002 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46003 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46018 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46019 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46021 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46023 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46026 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46027 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46038 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46040 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46044 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46046 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46049 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46051 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46064 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46070 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46078 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46082 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46086 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46102 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46107 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46127 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46137 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46146 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46151 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46157 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46158 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46160 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46161 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46167 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46169 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46170 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46172 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46184 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46193 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46196 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46200 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46214 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46220 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46225 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46226 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46229 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46231 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46233 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46235 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46236 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46247 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46252 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46254 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46273 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46280 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46291 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46304 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46307 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46312 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46320 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46321 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46322 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-2544 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2011-4915 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4916 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2011-4917 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9892 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9900 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-10723 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-13694 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12378 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12379 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12380 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12381 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12382 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12455 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-47432 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-50704 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50766 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50815 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-23000 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31081 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31085 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-4134 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52653 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52674 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52811 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53696 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53712 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53859 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53867 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54019 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54023 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54067 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54121 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54237 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54324 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27393 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35865 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39990 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40092 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40094 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40099 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40100 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40103 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40196 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40253 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68173 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68321 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68378 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68778 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68780 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68794 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68822 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31486 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43253 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43419 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43483 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43484 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43496 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45877 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45905 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45917 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46068 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46083 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46088 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46101 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46103 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46178 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46292 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46299 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc-dev-bin 2.31-13+deb11u14 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc-dev-bin 2.31-13+deb11u14 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc6-dev 2.31-13+deb11u14 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc6-dev 2.31-13+deb11u14 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-3523 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-50700 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-32255 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-26886 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-71225 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54181 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40343 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71193 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc-dev-bin 2.31-13+deb11u14 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc-dev-bin 2.31-13+deb11u14 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc6-dev 2.31-13+deb11u14 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc6-dev 2.31-13+deb11u14 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52633 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2004-0230 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 80.9% Actively Exploited | Not Applicable |
| CVE-2010-4563 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2005-3660 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-4039 | NONE0 | gcc-10-base 10.2.1-6 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-4039 | NONE0 | gcc-9-base 9.3.0-22 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-30258 | NONE0 | gpgv 2.2.27-2+deb11u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68972 | NONE0 | gpgv 2.2.27-2+deb11u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules 1.4.0-9+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules-bin 1.4.0-9+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-runtime 1.4.0-9+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam0g 1.4.0-9+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-20794 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-47382 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47599 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-27672 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48751 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48816 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49201 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49215 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49443 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49579 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49588 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49630 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49632 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49967 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50350 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-52589 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52608 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52639 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53178 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53401 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53447 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53520 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53794 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53816 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54201 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54287 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-2201 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 8.6% Low-Moderate Risk | Not Applicable |
| CVE-2024-24855 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-24864 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26583 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26585 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26607 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26869 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27408 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27415 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36024 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36949 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36952 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-37354 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38580 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39500 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39508 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42253 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43866 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46787 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46870 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-47660 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47668 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49859 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50135 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53088 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53100 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57857 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57974 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21651 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21701 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22060 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37920 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38232 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38234 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38524 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38717 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39726 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39754 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39927 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39961 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40016 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40139 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40252 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68239 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68296 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23004 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23118 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23126 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23212 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23302 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31697 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43275 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43448 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45949 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46017 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46159 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46187 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2017-0630 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-16230 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16234 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-54035 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54185 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54202 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26915 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4010 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-49934 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2012-4542 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-47484 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49196 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53733 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54263 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38540 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42123 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42230 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40206 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68768 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-50720 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26661 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26662 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26672 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26757 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26758 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26769 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40123 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2010-5321 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-16089 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-48646 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36928 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42156 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42158 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-16229 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16231 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16232 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-16233 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2010-4756 | NONE0 | libc-dev-bin 2.31-13+deb11u14 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2010-4756 | NONE0 | libc6-dev 2.31-13+deb11u14 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-23003 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-32251 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3219 | NONE0 | gpgv 2.2.27-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncurses6 6.2+20201114-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw6 6.2+20201114-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.2+20201114-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2015-2877 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-1075 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52561 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52926 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53992 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54145 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54153 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41027 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47738 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50057 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50211 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40303 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40341 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.2+20201114-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.2+20201114-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-11191 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2007-3719 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42155 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.1-2+deb11u1 No fix yet | — | Not Applicable |
| CVE-2025-6297 | NONE0 | dpkg 1.20.13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47770 | NONE0 | jq 1.6-2.1+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-49839 | NONE0 | jq 1.6-2.1+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-47770 | NONE0 | libjq1 1.6-2.1+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-49839 | NONE0 | libjq1 1.6-2.1+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.4.0-9+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.4.0-9+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.4.0-9+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.4.0-9+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl1.1 1.1.1w-0+deb11u7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31657 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-50634 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50708 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53699 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53707 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53742 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53748 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53834 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54020 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54047 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54151 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54157 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54180 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54182 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36331 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-27558 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40032 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40036 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40043 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40077 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40093 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40095 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40107 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40112 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40124 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40126 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40137 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40180 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40193 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40266 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40288 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40289 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40311 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40314 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40333 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40337 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40358 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68190 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68254 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68256 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68303 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68315 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68322 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68330 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68335 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68765 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68772 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68781 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71192 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71198 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31597 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31598 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31602 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31622 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31626 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31627 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31629 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31656 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31768 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43075 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43076 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43117 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43258 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43497 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43499 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45839 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45850 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45893 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46006 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46075 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46077 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46080 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46091 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46098 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46108 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46109 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46112 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46122 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46124 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46128 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46177 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46303 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46265 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46276 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46285 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46301 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | — | Not Applicable |
| CVE-2026-46331 | NONE0 | linux-libc-dev 5.10.257-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login 1:4.8.1-1+deb11u1 No fix yet | — | Not Applicable |
| CVE-2025-27587 | NONE0 | openssl 1.1.1w-0+deb11u7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.8.1-1+deb11u1 No fix yet | — | Not Applicable |
| CVE-2026-48959 | NONE0 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15649 | NONE0 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 2.96-7+deb11u1 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.34+dfsg-1+deb11u1 No fix yet | — | Not Applicable |
| GHSA-72hv-8253-57qq | NONE0 | com.fasterxml.jackson.core:jackson-core 2.15.2 fixed in 2.21.1, 2.18.6 | — | Not Applicable |
| CVE-2026-42583 | NONE0 | io.netty:netty-codec 4.1.127.Final fixed in 4.1.133.Final | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45205 | NONE0 | org.apache.commons:commons-configuration2 2.10.1 fixed in 2.15.0 | 0.5% Theoretical Threat | Not Applicable |