Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker could exploit FFmpeg or libxml2 vulnerabilities to achieve remote code execution or cause a denial of service, compromising the vllm service. Mitigations include deploying behind a web application firewall, restricting network access, and applying available patches. Consider rebuilding the image with updated base dependencies to reduce the attack surface.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-40962 | HIGH8.33 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40962 | HIGH8.33 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40962 | HIGH8.33 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-8376 | HIGH8.33 | libperl5.34 5.34.0-3ubuntu1.5 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40962 | HIGH8.33 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40962 | HIGH8.33 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40962 | HIGH8.33 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6653 | HIGH8.33 | libxml2 2.9.13+dfsg-1ubuntu0.11 fixed in 2.9.13+dfsg-1ubuntu0.12 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59197 | HIGH8.2 | pillow 12.2.0 fixed in 12.3.0 | — | Directly Exposed |
| CVE-2022-3964 | HIGH8.1 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48434 | HIGH8.1 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3964 | HIGH8.1 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48434 | HIGH8.1 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3964 | HIGH8.1 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48434 | HIGH8.1 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3964 | HIGH8.1 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48434 | HIGH8.1 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3964 | HIGH8.1 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48434 | HIGH8.1 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3964 | HIGH8.1 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48434 | HIGH8.1 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | HIGH8.1 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3964 | HIGH8.1 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48434 | HIGH8.1 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3964 | HIGH8.1 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48434 | HIGH8.1 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-59950 | HIGH8.1 | mcp 1.27.2 fixed in 1.28.1 | — | Directly Exposed |
| CVE-2025-37924 | HIGH7.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 9.8% Low-Moderate Risk | Directly Exposed |
| CVE-2013-7445 | HIGH7.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-64600 | HIGH7.8 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2019-19378 | HIGH7.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19814 | HIGH7.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33845 | HIGH7.73 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | HIGH7.73 | libperl5.34 5.34.0-3ubuntu1.5 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | HIGH7.73 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3109 | HIGH7.5 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3109 | HIGH7.5 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3109 | HIGH7.5 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3109 | HIGH7.5 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3109 | HIGH7.5 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33846 | HIGH7.5 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | HIGH7.5 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3109 | HIGH7.5 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-4743 | HIGH7.5 | libsdl2-2.0-0 2.0.20+dfsg-2ubuntu1.22.04.1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3109 | HIGH7.5 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3109 | HIGH7.5 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-4899 | HIGH7.5 | libzstd 1.4.4-1.el8 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0400 | HIGH7.5 | linux-libc-dev 5.15.0-181.191 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-38501 | HIGH7.5 | linux-libc-dev 5.15.0-181.191 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20426 | HIGH7.5 | linux-libc-dev 5.15.0-181.191 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-21240 | HIGH7.5 | python3-httplib2 0.20.2-2 No fix yet | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-59199 | HIGH7.5 | pillow 12.2.0 fixed in 12.3.0 | — | Directly Exposed |
| CVE-2026-59200 | HIGH7.5 | pillow 12.2.0 fixed in 12.3.0 | — | Directly Exposed |
| CVE-2026-59204 | HIGH7.5 | pillow 12.2.0 fixed in 12.3.0 | — | Directly Exposed |
| CVE-2026-59205 | HIGH7.5 | pillow 12.2.0 fixed in 12.3.0 | — | Directly Exposed |
| CVE-2026-59198 | HIGH7.5 | pillow 12.2.0 fixed in 12.3.0 | — | Directly Exposed |
| CVE-2026-59203 | HIGH7.5 | pillow 12.2.0 fixed in 12.3.0 | — | Directly Exposed |
| CVE-2026-59885 | HIGH7.5 | pyasn1 0.6.3 fixed in 0.6.4 | — | Directly Exposed |
| CVE-2026-59886 | HIGH7.5 | pyasn1 0.6.3 fixed in 0.6.4 | — | Directly Exposed |
| CVE-2025-1594 | HIGH7.48 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1594 | HIGH7.48 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1594 | HIGH7.48 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1594 | HIGH7.48 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1594 | HIGH7.48 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1594 | HIGH7.48 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1594 | HIGH7.48 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1594 | HIGH7.48 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43037 | HIGH7.48 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-23395 | HIGH7.48 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54058 | HIGH7.28 | pillow 12.2.0 fixed in 12.3.0 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53381 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-53384 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-53388 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-53391 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-53392 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-53393 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-53397 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-53398 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-53399 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63794 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63800 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63801 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63807 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63808 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63809 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63823 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63824 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63826 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63829 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63830 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63831 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63875 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63887 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63888 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63889 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63891 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63898 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63899 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63901 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63912 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63913 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63914 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63916 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63917 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63919 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63920 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63921 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63922 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63924 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63925 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63928 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63940 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63947 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63956 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63957 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63958 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63962 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63971 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63975 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63984 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63992 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63993 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63994 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64001 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64002 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64007 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64009 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64011 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64015 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64018 | HIGH7 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64025 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64026 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64032 | HIGH7 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64034 | HIGH7 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64047 | HIGH7 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64048 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64098 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64102 | HIGH7 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64109 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64111 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64113 | HIGH7 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64114 | HIGH7 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64115 | HIGH7 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64137 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64174 | HIGH7 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64189 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64191 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64192 | HIGH7 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-42013 | MEDIUM6.97 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM6.97 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-52194 | MEDIUM6.97 | libsndfile1 1.0.31-2ubuntu0.2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-37555 | MEDIUM6.97 | libsndfile1 1.0.31-2ubuntu0.2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31788 | MEDIUM6.97 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-bin 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.13 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | libpython3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | libpython3.10-stdlib 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-43114 | MEDIUM6.88 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43112 | MEDIUM6.88 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | python3.10 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | python3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-43133 | MEDIUM6.71 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-15794 | MEDIUM6.7 | linux-libc-dev 5.15.0-181.191 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-32230 | MEDIUM6.63 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-32230 | MEDIUM6.63 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-32230 | MEDIUM6.63 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-32230 | MEDIUM6.63 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-32230 | MEDIUM6.63 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-45221 | MEDIUM6.63 | libmfx1 22.3.0-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-32230 | MEDIUM6.63 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-32230 | MEDIUM6.63 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-32230 | MEDIUM6.63 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libudev1 249.11-0ubuntu3.16 fixed in 249.11-0ubuntu3.19 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37777 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23216 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31402 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-49359 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49910 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49935 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50095 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50212 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50213 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50234 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53629 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53673 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53179 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21812 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22040 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-22041 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-37778 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-37899 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-37926 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37952 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38349 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38437 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38552 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39863 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39952 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71073 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71089 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23171 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23208 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23226 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23227 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23378 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23428 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31532 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31709 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31720 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31729 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31759 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43049 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43329 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43378 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43499 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45891 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46274 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53148 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53262 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53359 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2020-14356 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-3238 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48744 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48771 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48990 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48998 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49471 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-50071 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50090 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50163 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50240 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50303 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-0030 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-2007 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-26242 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52452 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52624 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52751 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52837 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52916 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52921 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53037 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53072 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53187 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53218 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26699 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26742 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26842 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35932 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35949 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36012 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36898 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36914 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36921 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38556 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40900 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40954 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40989 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41045 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41050 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41069 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41074 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42117 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42118 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42147 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43842 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46729 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46811 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46813 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46820 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46833 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46836 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47745 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49880 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49931 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49991 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49992 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50063 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50112 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50246 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53098 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53133 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56604 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21927 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21945 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21967 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37903 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37928 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-37947 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38201 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38369 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38734 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71238 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23193 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23281 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23447 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23448 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31452 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31578 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31581 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31696 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43196 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43250 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45839 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45902 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45916 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45920 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45936 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45946 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45984 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46004 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46047 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46068 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46069 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46075 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46122 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46163 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46180 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46189 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46219 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46234 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46241 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46243 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52943 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52962 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52969 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52992 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53004 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53136 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53137 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53294 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53296 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13165 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-12930 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12931 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-26934 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49722 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49980 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50256 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50406 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50492 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50518 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50552 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-33053 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53052 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53320 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53510 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53544 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53596 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26983 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35868 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50217 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56609 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57887 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21734 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21863 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21915 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22083 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23133 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37786 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37822 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37861 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37957 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38069 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38117 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38118 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38131 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38239 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38250 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38259 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38361 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38422 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38485 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38595 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38702 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39797 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39810 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39859 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71152 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71220 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23068 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23221 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23234 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23262 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23359 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23361 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31399 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31455 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31485 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31489 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31493 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31500 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31527 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31576 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31580 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31583 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31686 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31702 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31715 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31747 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31748 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43015 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43020 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43027 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43205 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43328 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43426 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43458 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45866 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45867 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45879 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45885 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46267 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46285 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46294 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46301 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53059 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53089 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53112 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53115 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53117 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53120 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53129 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53156 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53157 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53195 | MEDIUM6.63 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21759 | MEDIUM6.6 | linux-libc-dev 5.15.0-181.191 No fix yet | 7.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3826 | MEDIUM6.5 | libasan6 11.4.0-1ubuntu1~22.04.3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | MEDIUM6.5 | libcairo-gobject2 1.16.0-5ubuntu2.1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | MEDIUM6.5 | libcairo2 1.16.0-5ubuntu2.1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-34969 | MEDIUM6.5 | libdbus-1-3 1.12.20-2ubuntu4.1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3826 | MEDIUM6.5 | libgcc-11-dev 11.4.0-1ubuntu1~22.04.3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6988 | MEDIUM6.5 | libopenjp2-7 2.4.0-6ubuntu0.5 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3826 | MEDIUM6.5 | libstdc++-11-dev 11.4.0-1ubuntu1~22.04.3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3826 | MEDIUM6.5 | libtsan0 11.4.0-1ubuntu1~22.04.3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-1193 | MEDIUM6.5 | linux-libc-dev 5.15.0-181.191 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-69872 | MEDIUM6.46 | diskcache 5.6.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-6603 | MEDIUM6.38 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-63757 | MEDIUM6.38 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6603 | MEDIUM6.38 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-63757 | MEDIUM6.38 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6603 | MEDIUM6.38 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-63757 | MEDIUM6.38 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6603 | MEDIUM6.38 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-63757 | MEDIUM6.38 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6603 | MEDIUM6.38 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-63757 | MEDIUM6.38 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | libdw1 0.186-1ubuntu0.1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | libelf1 0.186-1ubuntu0.1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-41989 | MEDIUM6.38 | libgcrypt20 1.9.4-3ubuntu3 fixed in 1.9.4-3ubuntu3.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libgssapi-krb5-2 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libgssapi-krb5-2 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libk5crypto3 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libk5crypto3 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5-3 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5-3 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5support0 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5support0 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | MEDIUM6.38 | libpcre2-8-0 10.39-3ubuntu0.1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-6603 | MEDIUM6.38 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-63757 | MEDIUM6.38 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | libpython3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | libpython3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | libpython3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | libpython3.10-stdlib 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | libpython3.10-stdlib 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | libpython3.10-stdlib 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM6.38 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM6.38 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-6603 | MEDIUM6.38 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-63757 | MEDIUM6.38 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6603 | MEDIUM6.38 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-63757 | MEDIUM6.38 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2173 | MEDIUM6.38 | libzvbi-common 0.2.35-19 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-2174 | MEDIUM6.38 | libzvbi-common 0.2.35-19 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-2176 | MEDIUM6.38 | libzvbi-common 0.2.35-19 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-2173 | MEDIUM6.38 | libzvbi0 0.2.35-19 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-2174 | MEDIUM6.38 | libzvbi0 0.2.35-19 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-2176 | MEDIUM6.38 | libzvbi0 0.2.35-19 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-43501 | MEDIUM6.38 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31669 | MEDIUM6.38 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43186 | MEDIUM6.38 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46195 | MEDIUM6.38 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-53071 | MEDIUM6.38 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53266 | MEDIUM6.38 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-25836 | MEDIUM6.38 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-36347 | MEDIUM6.38 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40210 | MEDIUM6.38 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43110 | MEDIUM6.38 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43190 | MEDIUM6.38 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59939 | MEDIUM6.38 | python3-httplib2 0.20.2-2 fixed in 0.20.2-2ubuntu0.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | python3.10 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | python3.10 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | python3.10 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | python3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | python3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | python3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-54059 | MEDIUM6.38 | pillow 12.2.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54060 | MEDIUM6.38 | pillow 12.2.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-55379 | MEDIUM6.38 | pillow 12.2.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-55380 | MEDIUM6.38 | pillow 12.2.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54234 | MEDIUM6.38 | vllm 0.23.0 fixed in 0.24.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-55574 | MEDIUM6.38 | vllm 0.23.0 fixed in 0.24.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53923 | MEDIUM6.38 | vllm 0.23.0 fixed in 0.24.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-22037 | MEDIUM6.32 | linux-libc-dev 5.15.0-181.191 No fix yet | 28.2% High Exploitation Risk | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40170 | MEDIUM6.29 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-14899 | MEDIUM6.29 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-43038 | MEDIUM6.21 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31607 | MEDIUM6.21 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43074 | MEDIUM6.21 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53781 | MEDIUM6.21 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23243 | MEDIUM6.21 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | libpython3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4786 | MEDIUM6.03 | libpython3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | libpython3.10-stdlib 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4786 | MEDIUM6.03 | libpython3.10-stdlib 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46135 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23455 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46259 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49172 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49218 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49234 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49401 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49518 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49961 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50551 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52682 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52701 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53254 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53376 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53575 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53751 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-6610 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26954 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35937 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35939 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36013 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-36915 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41013 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41935 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49861 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49928 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50164 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53147 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53216 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57945 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57982 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58015 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58054 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21946 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21985 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22038 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22039 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-22104 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22107 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37879 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38081 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38329 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38330 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38340 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38679 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38728 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39744 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39750 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39761 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39901 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40064 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40082 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68183 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68324 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23204 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23235 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23315 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23318 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23388 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23397 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31568 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31614 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31685 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31778 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43040 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43051 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43052 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43141 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43241 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43281 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43386 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43427 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43449 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43450 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43453 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45893 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45957 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45994 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46022 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46033 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46053 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46056 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46064 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46120 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46150 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46191 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46209 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52968 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53138 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53149 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53179 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53303 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53309 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53330 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43126 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43380 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43414 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53255 | MEDIUM6.03 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | python3.10 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4786 | MEDIUM6.03 | python3.10 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | python3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4786 | MEDIUM6.03 | python3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM5.95 | libcap2 1:2.44-1ubuntu0.22.04.2 fixed in 1:2.44-1ubuntu0.22.04.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5222 | MEDIUM5.95 | libicu70 70.1-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43304 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46043 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52989 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52993 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53002 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-54518 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23191 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23392 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31586 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31663 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31694 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43116 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43198 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43341 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43493 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45852 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46119 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46275 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46319 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52924 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53006 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53036 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53072 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53185 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53212 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53224 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53239 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53254 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53256 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53264 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53270 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53275 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-3864 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-1247 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-2961 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52586 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49855 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50106 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50286 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57876 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37776 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39759 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39826 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39905 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40135 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40158 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40168 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71203 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71221 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23050 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23054 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23270 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23454 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31408 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43050 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43158 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43226 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43233 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43334 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43339 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45856 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45859 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45860 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45942 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45970 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46015 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46052 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46054 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46090 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46099 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46116 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46123 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46133 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46149 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46174 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46181 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46227 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46266 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46324 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52912 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52917 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52918 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52920 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52933 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52935 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52942 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52945 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52947 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52956 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52957 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52986 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-52991 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52998 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53000 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53005 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53009 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53011 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53016 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53049 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53075 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53091 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53131 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53133 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53223 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53228 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-53246 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53268 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53354 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53355 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53357 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-45885 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21739 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31508 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45894 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53053 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53062 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53078 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53189 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53230 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53253 | MEDIUM5.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.9.4-3ubuntu3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.18.0-4ubuntu0.1 fixed in 4.18.0-4ubuntu0.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3714 | MEDIUM5.9 | linux-libc-dev 5.15.0-181.191 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-1121 | MEDIUM5.9 | linux-libc-dev 5.15.0-181.191 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-53196 | MEDIUM5.78 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46331 | MEDIUM5.7 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-50616 | MEDIUM5.7 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53095 | MEDIUM5.7 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57795 | MEDIUM5.7 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21714 | MEDIUM5.7 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50851 | MEDIUM5.61 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45991 | MEDIUM5.61 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53267 | MEDIUM5.61 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-59728 | MEDIUM5.52 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59732 | MEDIUM5.52 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59733 | MEDIUM5.52 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59728 | MEDIUM5.52 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59732 | MEDIUM5.52 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59733 | MEDIUM5.52 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59728 | MEDIUM5.52 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59732 | MEDIUM5.52 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59733 | MEDIUM5.52 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59728 | MEDIUM5.52 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59732 | MEDIUM5.52 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59733 | MEDIUM5.52 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59728 | MEDIUM5.52 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59732 | MEDIUM5.52 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59733 | MEDIUM5.52 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.35-0ubuntu3.11 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.35-0ubuntu3.13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.35-0ubuntu3.13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.35-0ubuntu3.13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-39329 | MEDIUM5.52 | libopenjp2-7 2.4.0-6ubuntu0.5 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-37769 | MEDIUM5.52 | libpixman-1-0 0.40.0-1ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-59728 | MEDIUM5.52 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59732 | MEDIUM5.52 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59733 | MEDIUM5.52 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50613 | MEDIUM5.52 | libsndfile1 1.0.31-2ubuntu0.2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-59728 | MEDIUM5.52 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59732 | MEDIUM5.52 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59733 | MEDIUM5.52 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59728 | MEDIUM5.52 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59732 | MEDIUM5.52 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59733 | MEDIUM5.52 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2175 | MEDIUM5.52 | libzvbi-common 0.2.35-19 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-2177 | MEDIUM5.52 | libzvbi-common 0.2.35-19 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-2175 | MEDIUM5.52 | libzvbi0 0.2.35-19 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-2177 | MEDIUM5.52 | libzvbi0 0.2.35-19 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-53176 | MEDIUM5.52 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2015-8553 | MEDIUM5.52 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-53785 | MEDIUM5.52 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40336 | MEDIUM5.52 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23179 | MEDIUM5.52 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31588 | MEDIUM5.52 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-0564 | MEDIUM5.52 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-55514 | MEDIUM5.52 | vllm 0.23.0 fixed in 0.24.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54233 | MEDIUM5.52 | vllm 0.23.0 fixed in 0.24.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54235 | MEDIUM5.52 | vllm 0.23.0 fixed in 0.24.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-55646 | MEDIUM5.52 | vllm 0.23.0 fixed in 0.24.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libbinutils 2.38-4ubuntu2.12 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010204 | MEDIUM5.5 | libbinutils 2.38-4ubuntu2.12 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo-gobject2 1.16.0-5ubuntu2.1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo2 1.16.0-5ubuntu2.1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf-nobfd0 2.38-4ubuntu2.12 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010204 | MEDIUM5.5 | libctf-nobfd0 2.38-4ubuntu2.12 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf0 2.38-4ubuntu2.12 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010204 | MEDIUM5.5 | libctf0 2.38-4ubuntu2.12 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-38562 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 7.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-53369 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-53379 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-53385 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-53400 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-53402 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-53403 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63803 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63810 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63822 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63832 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63858 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63860 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-63865 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-63867 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63868 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63870 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63872 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63890 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63892 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63893 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63897 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63900 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63902 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63903 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63904 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63926 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63927 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63942 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63948 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63961 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63963 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63964 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63973 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63976 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63983 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63985 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63990 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63991 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-63999 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64004 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64005 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64006 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64012 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64014 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64039 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64046 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64076 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64077 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64078 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64079 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64103 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64106 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64112 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64116 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64118 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64123 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64125 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64126 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64133 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64144 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64153 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64155 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64170 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64173 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64176 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64177 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64178 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64179 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64185 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64187 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64190 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-64206 | MEDIUM5.5 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Directly Exposed |
| CVE-2026-40225 | MEDIUM5.44 | libudev1 249.11-0ubuntu3.16 fixed in 249.11-0ubuntu3.19 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libudev1 249.11-0ubuntu3.16 fixed in 249.11-0ubuntu3.21 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23450 | MEDIUM5.44 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31502 | MEDIUM5.44 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31516 | MEDIUM5.44 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52910 | MEDIUM5.44 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53033 | MEDIUM5.44 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53090 | MEDIUM5.44 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39978 | MEDIUM5.44 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40074 | MEDIUM5.44 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68371 | MEDIUM5.44 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23456 | MEDIUM5.44 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-44032 | MEDIUM5.44 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-44033 | MEDIUM5.44 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-44034 | MEDIUM5.44 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45888 | MEDIUM5.44 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-40918 | MEDIUM5.35 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57893 | MEDIUM5.35 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40307 | MEDIUM5.35 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.24.0-6build1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23253 | MEDIUM5.27 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54081 | MEDIUM5.27 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40146 | MEDIUM5.27 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | libpython3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | libpython3.10-stdlib 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40190 | MEDIUM5.18 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31449 | MEDIUM5.18 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31700 | MEDIUM5.18 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31708 | MEDIUM5.18 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52829 | MEDIUM5.18 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53850 | MEDIUM5.18 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40071 | MEDIUM5.18 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40080 | MEDIUM5.18 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40355 | MEDIUM5.18 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68342 | MEDIUM5.18 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68343 | MEDIUM5.18 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68736 | MEDIUM5.18 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43134 | MEDIUM5.18 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31464 | MEDIUM5.18 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31570 | MEDIUM5.18 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | python3.10 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | python3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-33221 | MEDIUM5.1 | cuda-compat-13-0 580.95.05-0ubuntu1 fixed in 580.159.03-0ubuntu0.22.04.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52481 | MEDIUM5.1 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-31649 | MEDIUM5.1 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-bin 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.13 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.35-0ubuntu3.11 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-dev-bin 2.35-0ubuntu3.13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.35-0ubuntu3.13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.35-0ubuntu3.13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-32570 | MEDIUM5.02 | libdav1d5 0.9.2-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.10-stdlib 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.02 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-7008 | MEDIUM5.02 | libudev1 249.11-0ubuntu3.16 fixed in 249.11-0ubuntu3.21 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-53764 | MEDIUM5.02 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40242 | MEDIUM5.02 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35870 | MEDIUM5.02 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | python3.10 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | python3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23240 | MEDIUM4.93 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-23271 | MEDIUM4.93 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31414 | MEDIUM4.93 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-53789 | MEDIUM4.93 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54107 | MEDIUM4.93 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40237 | MEDIUM4.93 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40323 | MEDIUM4.93 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40340 | MEDIUM4.93 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68742 | MEDIUM4.93 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23239 | MEDIUM4.93 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31426 | MEDIUM4.93 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43279 | MEDIUM4.93 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46065 | MEDIUM4.93 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46113 | MEDIUM4.93 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52923 | MEDIUM4.93 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31392 | MEDIUM4.93 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-8925 | MEDIUM4.86 | curl 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8925 | MEDIUM4.86 | libcurl3-gnutls 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8925 | MEDIUM4.86 | libcurl4 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-49138 | MEDIUM4.84 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49569 | MEDIUM4.84 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46024 | MEDIUM4.84 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-36350 | MEDIUM4.76 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-36357 | MEDIUM4.76 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-0537 | MEDIUM4.7 | linux-libc-dev 5.15.0-181.191 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-24195 | MEDIUM4.67 | cuda-compat-13-0 580.95.05-0ubuntu1 fixed in 580.159.03-0ubuntu0.22.04.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libasan6 11.4.0-1ubuntu1~22.04.3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libasan6 11.4.0-1ubuntu1~22.04.3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libatomic1 12.3.0-1ubuntu1~22.04.3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-10256 | MEDIUM4.67 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-10256 | MEDIUM4.67 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-10256 | MEDIUM4.67 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-10256 | MEDIUM4.67 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-10256 | MEDIUM4.67 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libbinutils 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libbinutils 2.38-4ubuntu2.12 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-48064 | MEDIUM4.67 | libbinutils 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libcc1-0 12.3.0-1ubuntu1~22.04.3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf-nobfd0 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libctf-nobfd0 2.38-4ubuntu2.12 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-48064 | MEDIUM4.67 | libctf-nobfd0 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf0 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libctf0 2.38-4ubuntu2.12 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-48064 | MEDIUM4.67 | libctf0 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.4.7-1ubuntu0.7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1-dev 2.4.7-1ubuntu0.7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libgcc-11-dev 11.4.0-1ubuntu1~22.04.3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc-11-dev 11.4.0-1ubuntu1~22.04.3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc-s1 12.3.0-1ubuntu1~22.04.3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgfortran5 12.3.0-1ubuntu1~22.04.3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgomp1 12.3.0-1ubuntu1~22.04.3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libitm1 12.3.0-1ubuntu1~22.04.3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | liblsan0 12.3.0-1ubuntu1~22.04.3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-47169 | MEDIUM4.67 | libmfx1 22.3.0-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-48368 | MEDIUM4.67 | libmfx1 22.3.0-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-39328 | MEDIUM4.67 | libopenjp2-7 2.4.0-6ubuntu0.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-10256 | MEDIUM4.67 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libquadmath0 12.3.0-1ubuntu1~22.04.3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-35789 | MEDIUM4.67 | librabbitmq4 0.10.0-1ubuntu2 fixed in 0.10.0-1ubuntu2.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libstdc++-11-dev 11.4.0-1ubuntu1~22.04.3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++-11-dev 11.4.0-1ubuntu1~22.04.3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++6 12.3.0-1ubuntu1~22.04.3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-10256 | MEDIUM4.67 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-10256 | MEDIUM4.67 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libtsan0 11.4.0-1ubuntu1~22.04.3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libtsan0 11.4.0-1ubuntu1~22.04.3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libubsan1 12.3.0-1ubuntu1~22.04.3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-31637 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45988 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-56692 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71315 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23066 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23222 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23340 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23391 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23449 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31403 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31447 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31454 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31469 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31473 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31507 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31548 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31665 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31673 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31678 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31680 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31758 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43009 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43016 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43030 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43060 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43091 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43093 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43111 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43153 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43214 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43365 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43406 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43407 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43437 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43456 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43502 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45850 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45864 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45899 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46273 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46304 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46320 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52909 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52958 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53050 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53086 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53159 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53269 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2015-7837 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-8660 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-4095 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-47432 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47658 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0480 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-38457 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-40133 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-4543 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-48628 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48633 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48673 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48706 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48766 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48887 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48929 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48976 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48979 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49069 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49108 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49123 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49124 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49125 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49133 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49134 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49161 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49167 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49173 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49177 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49178 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49203 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49245 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49296 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49303 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49306 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49317 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49333 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49342 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49393 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49420 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49469 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49476 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49484 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49496 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49504 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49516 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49528 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49529 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49531 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49533 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49534 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49539 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49543 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49547 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49552 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49562 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49622 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49699 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49742 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49750 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49759 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49764 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49766 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49773 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49783 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49803 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49810 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49829 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49833 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49858 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49901 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49932 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49940 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49943 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49955 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49965 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49971 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49974 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49997 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50002 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50009 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50015 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50016 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50073 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50116 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50166 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50167 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50178 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50195 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50224 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50230 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50232 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50236 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50260 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50266 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50284 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50304 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50316 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50322 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50332 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50354 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50357 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50380 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50383 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50390 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50393 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50407 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50418 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50425 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50461 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50464 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50467 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50479 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50500 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50527 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50539 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50550 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50554 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50571 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50627 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50704 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50746 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50748 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50772 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50815 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50862 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50863 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50871 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-0160 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31082 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52485 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52569 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52576 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52582 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52590 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52591 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52625 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52632 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52634 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52648 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52653 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52657 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52660 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52671 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52673 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52676 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52700 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52732 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52737 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52761 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52831 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52857 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52879 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52888 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52905 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52920 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52939 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52981 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53002 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53008 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53009 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53010 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53036 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53042 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53068 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53093 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53105 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53115 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53149 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53152 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53168 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53180 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53198 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53209 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53221 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53231 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53240 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53247 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53248 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53258 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53261 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53292 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53323 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53325 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53332 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53347 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53348 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53353 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53355 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53362 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53366 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53367 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53370 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53371 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53382 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53383 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53385 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53387 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53410 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53424 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53429 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53434 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53438 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53460 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53466 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53483 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53491 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53509 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53529 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53538 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53539 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53540 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53545 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53547 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53558 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53561 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53562 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53574 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53584 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53588 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53602 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53609 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53620 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53627 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53628 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53635 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53647 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53651 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53657 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53671 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53682 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53685 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53694 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53702 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53721 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53743 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53753 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53765 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53767 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53780 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53806 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53822 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53829 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53846 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53849 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53867 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54002 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54016 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54019 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54023 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54028 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54052 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54067 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54088 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54121 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54129 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54190 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54234 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54237 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54242 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54259 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54271 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54280 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54324 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-14027 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26595 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26605 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26647 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26656 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26658 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26691 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26714 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26719 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26740 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26756 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26759 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26767 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26770 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26807 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26844 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26853 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26866 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26876 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26938 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26948 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26953 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27002 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27005 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27014 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27025 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27032 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27035 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27041 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27056 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27057 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27062 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27389 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27400 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27418 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27435 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35784 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35794 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35799 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35801 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35803 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35808 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35826 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35832 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35839 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35843 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35865 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35875 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35878 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-35908 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35924 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35926 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35931 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35942 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35945 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35946 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35956 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35959 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35971 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35995 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35998 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35999 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36000 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36009 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36021 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36026 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36244 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36478 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36479 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36900 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36909 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36911 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36917 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36918 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36920 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36922 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36924 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36948 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36951 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36966 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-37021 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38543 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38554 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38557 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38564 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38594 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38608 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38625 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39282 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39298 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40966 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40972 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40975 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40977 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40979 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40998 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40999 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41001 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41008 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41023 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41030 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41031 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41036 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41062 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41067 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41075 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41079 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41082 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41088 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42067 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42091 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42110 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42122 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42125 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42128 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42129 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42139 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42239 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42273 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42319 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42320 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42321 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43823 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43824 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43831 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43832 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43844 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43872 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-43899 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43911 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43912 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44950 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44961 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44962 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44963 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44970 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45010 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45015 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46678 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46681 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46705 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46715 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46716 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46717 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46718 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46720 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46726 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46727 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46728 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46730 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46733 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46748 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46749 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46754 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46762 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46765 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46770 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46775 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46802 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46803 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46806 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46808 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46823 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46834 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46835 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46842 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46843 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46848 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46857 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46860 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46861 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47141 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47658 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47661 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47662 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47664 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47678 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47683 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47703 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47704 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47728 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47736 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47794 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47809 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-48873 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49568 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49870 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49888 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49891 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49893 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49898 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49899 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49901 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49904 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49905 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49906 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49908 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49909 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49910 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49911 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49912 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49914 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49915 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49916 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49917 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49918 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49919 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49920 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49921 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49922 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49923 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49929 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49932 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49939 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49940 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49945 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49970 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49978 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49987 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49988 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49990 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49994 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50012 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50014 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50017 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50028 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50034 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50048 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50056 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50098 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50138 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50146 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50166 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50187 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50271 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50284 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50285 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50289 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50298 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-52559 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-52560 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53056 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53079 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53091 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53175 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53187 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53190 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53195 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53196 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53210 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53219 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53220 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53221 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53224 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53234 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53687 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-54683 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56368 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56544 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56557 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56565 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56566 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56583 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56584 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56588 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56591 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56592 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56607 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56611 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56639 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56641 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56647 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56657 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56660 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56665 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56671 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56677 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56703 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56707 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56709 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56712 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56717 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56718 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56719 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56722 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56727 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56782 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57804 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57809 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57843 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57852 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57872 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57875 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57888 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57895 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57924 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57950 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57952 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57975 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57976 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57993 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57999 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58012 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58018 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58019 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58053 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58077 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58089 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58094 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58095 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58096 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58097 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58098 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58100 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58238 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58241 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21629 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21634 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21635 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21649 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21656 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21658 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21667 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21672 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21673 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21682 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21696 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21712 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21723 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21730 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21738 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21750 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21752 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21768 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21792 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21801 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21816 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21817 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21819 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21821 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21831 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21832 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21833 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21838 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21872 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21881 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21885 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21891 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21894 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21899 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21908 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21918 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21931 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21944 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21955 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21972 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21976 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21986 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22019 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22026 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22028 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22042 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22043 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22053 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22057 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22072 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22090 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22103 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22105 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22109 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22113 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22124 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22125 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22127 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23130 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23131 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23132 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23141 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23155 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23160 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23162 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37743 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37744 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37745 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37746 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37747 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37775 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37806 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37807 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37820 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37833 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37834 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37842 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37852 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37853 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37855 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37856 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37870 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37876 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37877 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37878 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37880 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37884 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37907 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37931 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37938 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37945 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37951 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37954 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37956 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37959 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37961 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37980 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37984 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38006 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38011 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38014 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38015 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38020 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38029 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38033 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38036 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38038 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38039 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38040 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38041 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38042 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38045 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38047 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38059 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38060 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38062 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38063 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38064 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38070 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38071 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38080 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38092 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38096 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38097 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38098 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38099 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38105 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38126 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38127 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38140 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38162 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38166 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38168 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38189 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38191 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-38192 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38199 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38202 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38205 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38207 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38208 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38215 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38225 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38244 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38261 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38264 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38269 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38272 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38275 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38300 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38321 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38331 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38333 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38334 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38343 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38353 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38359 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38360 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38368 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38373 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38409 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38426 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38436 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38438 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38449 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38491 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38503 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38507 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38520 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38531 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38544 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38560 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38590 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38615 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38621 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38626 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38643 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38644 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38659 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38665 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38692 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38705 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38709 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38710 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38716 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39677 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39692 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39705 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39706 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39707 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39715 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39716 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39720 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39732 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39745 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39746 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39747 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39748 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39753 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39762 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39763 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39764 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39770 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39771 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39779 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39781 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39789 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39800 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39819 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39827 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39829 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39833 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39838 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39850 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39851 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39886 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39908 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39925 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39929 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39931 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39932 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39933 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39940 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39942 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39947 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39989 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39990 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40005 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40057 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40075 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40099 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40100 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40102 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40103 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40104 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40160 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40195 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40196 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40251 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40284 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40287 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40305 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40325 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40334 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40339 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40347 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40362 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68171 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68173 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68178 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68188 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68193 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68206 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68219 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68223 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68231 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68236 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68265 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68281 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68283 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68297 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68307 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68309 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68310 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68313 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68317 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68333 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68334 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68345 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68358 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68363 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68378 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68379 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68778 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68794 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68798 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68802 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68822 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71095 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71107 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71109 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71115 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71150 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71158 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71160 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71161 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71183 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71184 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71202 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71204 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71222 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71223 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71227 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71229 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71232 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71233 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71235 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71236 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71237 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71239 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71265 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71266 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71267 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71268 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71269 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71272 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71273 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71285 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71287 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71289 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71290 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71291 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71292 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71293 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71294 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71295 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71297 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71299 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71300 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71302 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22979 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22996 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23000 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23031 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23069 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23086 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23088 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23100 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23113 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23137 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23138 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23141 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23154 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23157 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23190 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23196 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23202 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23206 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23213 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23214 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23215 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23217 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23220 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23228 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23229 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23236 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23237 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23238 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23241 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23242 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23247 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23255 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23256 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23257 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23258 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23259 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23260 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23261 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23264 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23265 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23266 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23267 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23272 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23276 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23277 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23278 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23279 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23285 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23286 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23287 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23289 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23290 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23291 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23292 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23293 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23296 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23298 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23300 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23303 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23304 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23307 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23310 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23312 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23324 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23330 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23334 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23335 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23339 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23347 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23352 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23356 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23357 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23362 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23365 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23367 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23368 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23370 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23371 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23374 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23379 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23381 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23382 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23389 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23396 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23398 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23399 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23401 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23420 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23434 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23438 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23439 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23442 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23446 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23460 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23462 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23465 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23468 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23472 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23474 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31391 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31394 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31400 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31407 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31410 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31411 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31412 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31415 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31416 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31418 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31420 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31421 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31422 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31423 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31424 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31425 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31427 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31428 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31441 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31450 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31451 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31461 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31462 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31467 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31480 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31483 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31486 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31487 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31492 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31495 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31496 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31497 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31498 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31503 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31509 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31510 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31512 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31515 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31518 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31519 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31520 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31521 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31522 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31524 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31531 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31537 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31540 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31545 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31546 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31549 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31550 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31551 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31552 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31555 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31557 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31560 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31565 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31577 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31579 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31585 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31590 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31592 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31594 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31595 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31596 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31599 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31603 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31605 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31606 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31610 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31615 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31616 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31617 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31618 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31619 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31623 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31624 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31625 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31628 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31630 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31634 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31642 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31651 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31658 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31660 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31661 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31662 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31664 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31670 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31671 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31672 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31674 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31675 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31676 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31677 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31679 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31681 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31682 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31684 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31687 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31692 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31698 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31699 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31701 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31704 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31721 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31722 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31723 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31724 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31725 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31726 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31737 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31738 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31749 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31752 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31754 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31755 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31756 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31762 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31763 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31767 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31770 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31773 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31777 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31781 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43014 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43021 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43022 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43024 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43025 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43026 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43028 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43032 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43035 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43036 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43041 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43042 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43043 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43045 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43046 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43048 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43054 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43058 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43061 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43062 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43064 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43065 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43066 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43068 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43069 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43072 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43073 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43079 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43080 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43085 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43088 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43089 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43098 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43099 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43101 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43103 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43104 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43105 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43107 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43109 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43113 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43115 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43118 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43119 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43123 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43124 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43127 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43129 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43130 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43131 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43132 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43135 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43136 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43137 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43139 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43140 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43143 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43145 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43147 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43148 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43149 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43152 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43156 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43159 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43161 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43162 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43165 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43167 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43168 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43170 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43171 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43172 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43173 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43182 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43183 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43187 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43189 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43191 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43194 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43195 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43200 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43201 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43202 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43204 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43209 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43213 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43216 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43218 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43219 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43220 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43223 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43225 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43227 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43228 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43230 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43231 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43234 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43242 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43243 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43244 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43246 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43251 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43253 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43255 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43257 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43261 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43262 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43264 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43266 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43267 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43268 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43269 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43270 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43271 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43273 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43277 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43287 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43288 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43289 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43292 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43294 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43295 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43296 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43298 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43299 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43300 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43302 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43305 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43306 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43308 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43309 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43310 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43311 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43312 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43313 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43314 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43315 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43316 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43317 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43318 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43319 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43320 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43327 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43333 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43338 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43340 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43343 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43344 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43350 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43355 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43357 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43359 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43361 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43362 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43363 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43381 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43382 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43387 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43398 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43400 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43405 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43409 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43410 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43411 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43413 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43416 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43419 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43421 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43424 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43425 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43428 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43429 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43432 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43436 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43445 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43451 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43452 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43459 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43466 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43469 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43471 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43472 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43473 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43474 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43475 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43483 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43491 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43492 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43496 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45834 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45835 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45836 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45840 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45842 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45843 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45846 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45847 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45848 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45855 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45857 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45873 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45890 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45904 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45912 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45915 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45917 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45919 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45923 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45924 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45930 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45934 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45940 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45941 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45944 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45948 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45954 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45960 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45961 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45964 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45965 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45968 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45969 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45974 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45978 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45981 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45983 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45985 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45986 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45987 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45997 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45999 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46000 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46002 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46003 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46009 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46012 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46014 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46018 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46019 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46021 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46023 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46026 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46027 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46032 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46037 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46038 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46040 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46044 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46046 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46049 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46050 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46051 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46059 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46070 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46072 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46077 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46078 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46080 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46082 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46083 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46086 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46088 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46091 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46092 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46098 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46101 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46102 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46103 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46107 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46108 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46127 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46128 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46132 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46137 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46146 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46151 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46153 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46157 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46158 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46160 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46161 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46167 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46168 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46169 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46170 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46172 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46178 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46184 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46186 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46193 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46196 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46200 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46214 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46220 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46225 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46226 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46229 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46231 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46233 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46235 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46236 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46247 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46302 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46303 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46321 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46322 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52913 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52915 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52916 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52921 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52925 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52926 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52927 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52928 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52929 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52930 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52936 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52937 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52939 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52944 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52946 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-52948 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52954 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52960 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52963 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52970 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52972 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52975 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52977 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52981 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52984 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52985 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52988 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52990 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52995 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52999 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53001 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53003 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53012 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53015 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53017 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53018 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53021 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53022 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53023 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53034 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53037 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53039 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53056 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53064 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53066 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53069 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53074 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53076 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53077 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53080 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53083 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53088 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53107 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53122 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53128 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53134 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53139 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53150 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53167 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53168 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53181 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53199 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53208 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53218 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53219 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53220 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53221 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-53227 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53245 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53252 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53263 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53284 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53287 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53289 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53291 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53292 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53295 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53304 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53306 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53313 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53314 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53317 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53320 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53325 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53327 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53331 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53332 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53337 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53339 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53345 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53349 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53353 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53358 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-13693 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12928 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12929 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-3114 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49651 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4133 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27010 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27011 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50009 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53093 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58237 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21645 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21693 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37800 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71304 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71313 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23198 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23336 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23444 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31446 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31448 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31453 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31667 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31771 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43071 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43180 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43211 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43352 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43353 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43480 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43484 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45838 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45841 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45844 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45858 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45862 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45868 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45869 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45870 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45871 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45872 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45875 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45877 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45883 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45911 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46147 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46245 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46249 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46252 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46253 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46254 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46280 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46291 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46292 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46299 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46307 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46312 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52982 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53035 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53047 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53048 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53060 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53061 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53063 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53065 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53070 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53073 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53082 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53093 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53096 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53106 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53111 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53135 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53146 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53147 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53158 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53177 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53207 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53213 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53225 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53226 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53229 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53232 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53236 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53237 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53238 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53249 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53258 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53265 | MEDIUM4.67 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | MEDIUM4.64 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl 5.34.0-3ubuntu1.5 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-base 5.34.0-3ubuntu1.5 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-modules-5.34 5.34.0-3ubuntu1.5 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58055 | MEDIUM4.59 | libnghttp2-14 1.43.0-1ubuntu0.3 fixed in 1.43.0-1ubuntu0.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-3109 | MEDIUM4.5 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | MEDIUM4.5 | patch 2.7.6-7build2 No fix yet | 8.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-3341 | MEDIUM4.5 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-0518 | MEDIUM4.5 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-3341 | MEDIUM4.5 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-0518 | MEDIUM4.5 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-3341 | MEDIUM4.5 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-0518 | MEDIUM4.5 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-3341 | MEDIUM4.5 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-0518 | MEDIUM4.5 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-3341 | MEDIUM4.5 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-0518 | MEDIUM4.5 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc-bin 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.13 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-bin 2.35-0ubuntu3.11 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-dev-bin 2.35-0ubuntu3.13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.35-0ubuntu3.13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6-dev 2.35-0ubuntu3.13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | MEDIUM4.5 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.2.5-2ubuntu1 fixed in 5.2.5-2ubuntu1.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-3341 | MEDIUM4.5 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-0518 | MEDIUM4.5 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.10-stdlib 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3341 | MEDIUM4.5 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-0518 | MEDIUM4.5 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-3341 | MEDIUM4.5 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-0518 | MEDIUM4.5 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-3523 | MEDIUM4.5 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-50700 | MEDIUM4.5 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54181 | MEDIUM4.5 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47689 | MEDIUM4.5 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-40353 | MEDIUM4.5 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71225 | MEDIUM4.5 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23457 | MEDIUM4.5 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53194 | MEDIUM4.5 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | python3.10 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | python3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54236 | MEDIUM4.5 | vllm 0.23.0 fixed in 0.24.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1594 | MEDIUM4.49 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-40217 | MEDIUM4.42 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40338 | MEDIUM4.42 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50721 | MEDIUM4.33 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71193 | MEDIUM4.33 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23035 | MEDIUM4.33 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssapi-krb5-2 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libk5crypto3 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-3 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5support0 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM4.25 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-23180 | MEDIUM4.25 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-8286 | MEDIUM4.13 | curl 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl3-gnutls 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl4 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | MEDIUM4.13 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-12491 | MEDIUM4.08 | vllm 0.23.0 fixed in 0.24.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15467 | MEDIUM4.06 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 47.6% High Exploitation Risk | Post-Exploit |
| CVE-2025-15467 | MEDIUM4.06 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 47.6% High Exploitation Risk | Post-Exploit |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.37.2-4ubuntu3.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | MEDIUM4 | libdw1 0.186-1ubuntu0.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | MEDIUM4 | libelf1 0.186-1ubuntu0.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.37.2-4ubuntu3.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.37.2-4ubuntu3.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.37.2-4ubuntu3.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-24032 | MEDIUM4 | libzstd 1.4.4-1.el8 fixed in 1.4.8+dfsg-2build1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52955 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-57857 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21947 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23004 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23169 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43047 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-1205 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-48816 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49967 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50350 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52589 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53178 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53401 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53447 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53452 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53478 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53794 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53816 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54035 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54071 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54149 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54185 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54201 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54323 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26869 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27408 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36024 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36949 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38306 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-39293 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-39508 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42107 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42253 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43866 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46870 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49859 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50135 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53176 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53178 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56788 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57974 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21651 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21732 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21825 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37920 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38234 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38440 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38524 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38717 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39726 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39754 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39825 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39884 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39927 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39961 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39977 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39992 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40016 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40039 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40139 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40250 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68214 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68239 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68296 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68745 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71074 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71274 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23110 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23118 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23126 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23181 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23207 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23212 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23302 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23348 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23452 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23463 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31393 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31466 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31523 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31697 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31728 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31751 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43053 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43163 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43275 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43342 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43383 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43420 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43430 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43439 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43448 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45905 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45949 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46159 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46187 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53108 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53352 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52749 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50183 | MEDIUM4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-32230 | LOW3.98 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2016-2568 | LOW3.98 | pkexec 0.105-33ubuntu0.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2016-2568 | LOW3.98 | policykit-1 0.105-33ubuntu0.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2016-2568 | LOW3.98 | polkitd 0.105-33ubuntu0.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-15213 | LOW3.91 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4010 | LOW3.91 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-49934 | LOW3.91 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-3826 | LOW3.9 | cpp-11 11.4.0-1ubuntu1~22.04.3 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3826 | LOW3.9 | g++-11 11.4.0-1ubuntu1~22.04.3 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3826 | LOW3.9 | gcc-11 11.4.0-1ubuntu1~22.04.3 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3826 | LOW3.9 | gcc-11-base 11.4.0-1ubuntu1~22.04.3 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-6603 | LOW3.82 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-63757 | LOW3.82 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.10-4ubuntu4.1 fixed in 1.10-4ubuntu4.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl3-gnutls 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl4 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-69421 | LOW3.82 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28388 | LOW3.82 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-28389 | LOW3.82 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | LOW3.82 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW3.82 | libpython3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.10-stdlib 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-45896 | LOW3.82 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | python3.10 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | python3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-55798 | LOW3.82 | pillow 12.2.0 fixed in 12.3.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW3.77 | curl 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl3-gnutls 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl4 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW3.77 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69419 | LOW3.77 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-23458 | LOW3.74 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-17977 | LOW3.74 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-50720 | LOW3.74 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52508 | LOW3.74 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53733 | LOW3.74 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54247 | LOW3.74 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54253 | LOW3.74 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54263 | LOW3.74 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26648 | LOW3.74 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26662 | LOW3.74 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26672 | LOW3.74 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26757 | LOW3.74 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26758 | LOW3.74 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36910 | LOW3.74 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38628 | LOW3.74 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40123 | LOW3.74 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40198 | LOW3.74 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40206 | LOW3.74 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68768 | LOW3.74 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2020-14304 | LOW3.74 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-68973 | LOW3.57 | dirmngr 2.2.27-3ubuntu2.4 fixed in 2.2.27-3ubuntu2.5 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gnupg 2.2.27-3ubuntu2.4 fixed in 2.2.27-3ubuntu2.5 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gnupg-utils 2.2.27-3ubuntu2.4 fixed in 2.2.27-3ubuntu2.5 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gnupg2 2.2.27-3ubuntu2.4 fixed in 2.2.27-3ubuntu2.5 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpg 2.2.27-3ubuntu2.4 fixed in 2.2.27-3ubuntu2.5 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpg-agent 2.2.27-3ubuntu2.4 fixed in 2.2.27-3ubuntu2.5 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpg-wks-client 2.2.27-3ubuntu2.4 fixed in 2.2.27-3ubuntu2.5 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpg-wks-server 2.2.27-3ubuntu2.4 fixed in 2.2.27-3ubuntu2.5 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpgconf 2.2.27-3ubuntu2.4 fixed in 2.2.27-3ubuntu2.5 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpgsm 2.2.27-3ubuntu2.4 fixed in 2.2.27-3ubuntu2.5 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpgv 2.2.27-3ubuntu2.4 fixed in 2.2.27-3ubuntu2.5 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-41848 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42010 | LOW3.53 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48646 | LOW3.48 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9820 | LOW3.4 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-8924 | LOW3.31 | curl 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-59728 | LOW3.31 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-59732 | LOW3.31 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-59733 | LOW3.31 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl3-gnutls 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl4 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-36613 | LOW3.31 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36613 | LOW3.31 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36613 | LOW3.31 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36613 | LOW3.31 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36613 | LOW3.31 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36613 | LOW3.31 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36613 | LOW3.31 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36613 | LOW3.31 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | LOW3.3 | binutils 2.38-4ubuntu2.12 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010204 | LOW3.3 | binutils 2.38-4ubuntu2.12 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-common 2.38-4ubuntu2.12 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010204 | LOW3.3 | binutils-common 2.38-4ubuntu2.12 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010204 | LOW3.3 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-46848 | LOW3.28 | libtasn1-6 4.18.0-4ubuntu0.1 fixed in 4.18.0-4ubuntu0.2 | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.8-1ubuntu2 fixed in 4.8-1ubuntu2.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-7055 | LOW3.17 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-7055 | LOW3.17 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-7055 | LOW3.17 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-7055 | LOW3.17 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-7055 | LOW3.17 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-7055 | LOW3.17 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-1580 | LOW3.17 | libdav1d5 0.9.2-1 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2024-7055 | LOW3.17 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-7055 | LOW3.17 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-7055 | LOW3.17 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3832 | LOW3.15 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-7883 | LOW3.15 | libllvm15 1:15.0.7-0ubuntu0.22.04.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53791 | LOW3.15 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59890 | LOW3.11 | setuptools 80.10.2 fixed in 83.0.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31790 | LOW3.01 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2025-69420 | LOW3.01 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-22796 | LOW3.01 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.01 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-40962 | LOW3 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-40962 | LOW3 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-40962 | LOW3 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-40393 | LOW3 | libgbm1 23.2.1-1ubuntu3.1~22.04.3 fixed in 23.2.1-1ubuntu3.1~22.04.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-40393 | LOW3 | libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.3 fixed in 23.2.1-1ubuntu3.1~22.04.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-40393 | LOW3 | libglapi-mesa 23.2.1-1ubuntu3.1~22.04.3 fixed in 23.2.1-1ubuntu3.1~22.04.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-40393 | LOW3 | libglx-mesa0 23.2.1-1ubuntu3.1~22.04.3 fixed in 23.2.1-1ubuntu3.1~22.04.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | LOW3 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | LOW3 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl 5.34.0-3ubuntu1.5 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.34.0-3ubuntu1.5 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-modules-5.34 5.34.0-3ubuntu1.5 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-3964 | LOW2.92 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 3.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48434 | LOW2.92 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2020-35501 | LOW2.89 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-45582 | LOW2.86 | tar 1.34+dfsg-1ubuntu0.1.22.04.2 fixed in 1.34+dfsg-1ubuntu0.1.22.04.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | binutils 2.38-4ubuntu2.12 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-48064 | LOW2.8 | binutils 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-common 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | binutils-common 2.38-4ubuntu2.12 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-48064 | LOW2.8 | binutils-common 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-48064 | LOW2.8 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2021-46195 | LOW2.8 | cpp-11 11.4.0-1ubuntu1~22.04.3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | cpp-11 11.4.0-1ubuntu1~22.04.3 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-10256 | LOW2.8 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-46195 | LOW2.8 | g++-11 11.4.0-1ubuntu1~22.04.3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | g++-11 11.4.0-1ubuntu1~22.04.3 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2021-46195 | LOW2.8 | gcc-11 11.4.0-1ubuntu1~22.04.3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | gcc-11 11.4.0-1ubuntu1~22.04.3 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2021-46195 | LOW2.8 | gcc-11-base 11.4.0-1ubuntu1~22.04.3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | gcc-11-base 11.4.0-1ubuntu1~22.04.3 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | gcc-12-base 12.3.0-1ubuntu1~22.04.3 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-22795 | LOW2.8 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-20633 | LOW2.8 | patch 2.7.6-7build2 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.7.6-7build2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.34+dfsg-1ubuntu0.1.22.04.2 fixed in 1.34+dfsg-1ubuntu0.1.22.04.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0987 | LOW2.8 | gir1.2-packagekitglib-1.0 1.2.5-2ubuntu3.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-0217 | LOW2.8 | gir1.2-packagekitglib-1.0 1.2.5-2ubuntu3.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libbinutils 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf-nobfd0 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf0 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0987 | LOW2.8 | libpackagekit-glib2-18 1.2.5-2ubuntu3.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-0217 | LOW2.8 | libpackagekit-glib2-18 1.2.5-2ubuntu3.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | libpython3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | libpython3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | libpython3.10-stdlib 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.10-stdlib 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | libpython3.10-stdlib 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 249.11-0ubuntu3.21 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 249.11-0ubuntu3.16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52926 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48667 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48668 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50628 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50778 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50811 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52561 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53992 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54145 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54172 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54227 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54233 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54261 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54320 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47738 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50057 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50211 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57898 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40268 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40303 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40341 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71224 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31668 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | python3.10 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | python3.10 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | python3.10 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | python3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | python3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | python3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3341 | LOW2.7 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-0518 | LOW2.7 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW2.55 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.37.2-4ubuntu3.4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.10-4ubuntu4.1 fixed in 1.10-4ubuntu4.2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.37.2-4ubuntu3.4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68160 | LOW2.4 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.37.2-4ubuntu3.4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW2.38 | libbinutils 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf-nobfd0 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf0 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW2.04 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.21 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36613 | LOW1.99 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-50583 | LOW1.95 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW1.89 | binutils 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-common 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW1.89 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.8.1-2ubuntu2.2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-common 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-0987 | LOW1.68 | packagekit 1.2.5-2ubuntu3.1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-0217 | LOW1.68 | packagekit 1.2.5-2ubuntu3.1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-29383 | LOW1.68 | passwd 1:4.8.1-2ubuntu2.2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-42155 | LOW1.61 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW1.43 | binutils 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-common 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | NONE0 | libncurses6 6.3-2ubuntu0.1 fixed in 6.3-2ubuntu0.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncursesw6 6.3-2ubuntu0.1 fixed in 6.3-2ubuntu0.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-2568 | NONE0 | libpolkit-agent-1-0 0.105-33ubuntu0.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-2568 | NONE0 | libpolkit-gobject-1-0 0.105-33ubuntu0.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.3-2ubuntu0.1 fixed in 6.3-2ubuntu0.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.3-2ubuntu0.1 fixed in 6.3-2ubuntu0.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.3-2ubuntu0.1 fixed in 6.3-2ubuntu0.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68973 | NONE0 | gnupg-l10n 2.2.27-3ubuntu2.4 fixed in 2.2.27-3ubuntu2.5 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-34969 | NONE0 | dbus 1.12.20-2ubuntu4.1 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | libncurses6 6.3-2ubuntu0.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libncursesw6 6.3-2ubuntu0.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libtinfo6 6.3-2ubuntu0.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.3-2ubuntu0.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-bin 6.3-2ubuntu0.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.4.0-11ubuntu2.6 fixed in 1.4.0-11ubuntu2.7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.4.0-11ubuntu2.6 fixed in 1.4.0-11ubuntu2.7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.4.0-11ubuntu2.6 fixed in 1.4.0-11ubuntu2.7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.4.0-11ubuntu2.6 fixed in 1.4.0-11ubuntu2.7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login 1:4.8.1-2ubuntu2.2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libpam-systemd 249.11-0ubuntu3.21 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-29383 | NONE0 | login 1:4.8.1-2ubuntu2.2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | systemd 249.11-0ubuntu3.21 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | systemd-sysv 249.11-0ubuntu3.21 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-33219 | NONE0 | cuda-compat-13-0 580.95.05-0ubuntu1 fixed in 580.126.09-0ubuntu0.22.04.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-33220 | NONE0 | cuda-compat-13-0 580.95.05-0ubuntu1 fixed in 580.126.09-0ubuntu0.22.04.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-24182 | NONE0 | cuda-compat-13-0 580.95.05-0ubuntu1 fixed in 580.159.03-0ubuntu0.22.04.1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-24187 | NONE0 | cuda-compat-13-0 580.95.05-0ubuntu1 fixed in 580.159.03-0ubuntu0.22.04.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-24190 | NONE0 | cuda-compat-13-0 580.95.05-0ubuntu1 fixed in 580.159.03-0ubuntu0.22.04.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-24192 | NONE0 | cuda-compat-13-0 580.95.05-0ubuntu1 fixed in 580.159.03-0ubuntu0.22.04.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-24193 | NONE0 | cuda-compat-13-0 580.95.05-0ubuntu1 fixed in 580.159.03-0ubuntu0.22.04.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-24194 | NONE0 | cuda-compat-13-0 580.95.05-0ubuntu1 fixed in 580.159.03-0ubuntu0.22.04.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-24196 | NONE0 | cuda-compat-13-0 580.95.05-0ubuntu1 fixed in 580.159.03-0ubuntu0.22.04.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-24197 | NONE0 | cuda-compat-13-0 580.95.05-0ubuntu1 fixed in 580.159.03-0ubuntu0.22.04.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-24198 | NONE0 | cuda-compat-13-0 580.95.05-0ubuntu1 fixed in 580.159.03-0ubuntu0.22.04.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-24199 | NONE0 | cuda-compat-13-0 580.95.05-0ubuntu1 fixed in 580.159.03-0ubuntu0.22.04.1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | curl 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-49502 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-50010 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-51793 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-51794 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-51798 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6602 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6604 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6605 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35366 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35367 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-35368 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-36616 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36617 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36618 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22919 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-25473 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-59731 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56109 | NONE0 | libasound2 1.2.6.1-1ubuntu1.1 fixed in 1.2.6.1-1ubuntu1.2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56109 | NONE0 | libasound2-data 1.2.6.1-1ubuntu1.1 fixed in 1.2.6.1-1ubuntu1.2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-49502 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-50010 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-51793 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-51794 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-51798 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6602 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6604 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6605 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35366 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35367 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-35368 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-36616 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36617 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36618 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22919 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-25473 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-59731 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-49502 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-50010 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-51793 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-51794 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-51798 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6602 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6604 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6605 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35366 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35367 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-35368 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-36616 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36617 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36618 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22919 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-25473 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-59731 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-49502 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-50010 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-51793 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-51794 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-51798 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6602 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6604 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6605 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35366 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35367 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-35368 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-36616 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36617 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36618 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22919 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-25473 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-59731 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-49502 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-50010 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-51793 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-51794 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-51798 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6602 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6604 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6605 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35366 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35367 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-35368 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-36616 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36617 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36618 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22919 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-25473 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-59731 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-49502 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-50010 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-51793 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-51794 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-51798 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6602 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6604 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6605 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35366 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35367 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-35368 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-36616 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36617 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36618 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22919 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-25473 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-59731 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl3-gnutls 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl4 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-50593 | NONE0 | libgraphite2-3 1.3.14-1build2 fixed in 1.3.14-1ubuntu0.1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-22656 | NONE0 | libmfx1 22.3.0-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-47282 | NONE0 | libmfx1 22.3.0-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40930 | NONE0 | libpng16-16 1.6.37-3ubuntu0.5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-49502 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-50010 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-51793 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-51794 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-51798 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6602 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6604 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6605 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35366 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35367 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-35368 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-36616 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36617 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36618 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22919 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-25473 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-59731 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.10-stdlib 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-44235 | NONE0 | librabbitmq4 0.10.0-1ubuntu2 fixed in 0.10.0-1ubuntu2.1 | — | Not Applicable |
| CVE-2026-44236 | NONE0 | librabbitmq4 0.10.0-1ubuntu2 fixed in 0.10.0-1ubuntu2.1 | — | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-0 3.37.2-2ubuntu0.5 fixed in 3.37.2-2ubuntu0.6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-0 3.37.2-2ubuntu0.5 fixed in 3.37.2-2ubuntu0.6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-0 3.37.2-2ubuntu0.5 fixed in 3.37.2-2ubuntu0.7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-0 3.37.2-2ubuntu0.5 fixed in 3.37.2-2ubuntu0.7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-49502 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-50010 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-51793 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-51794 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-51798 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6602 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6604 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6605 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35366 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35367 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-35368 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-36616 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36617 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36618 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22919 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-25473 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-59731 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-49502 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-50010 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-51793 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-51794 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-51798 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6602 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6604 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6605 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35366 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35367 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-35368 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-36616 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36617 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36618 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22919 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-25473 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-59731 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libx264-163 2:0.163.3060+git5db6aa6-2build1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-68263 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43011 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53215 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23372 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31405 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31433 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31476 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31478 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31627 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31656 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31657 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31659 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31695 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31705 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31712 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31716 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31780 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43075 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43076 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43206 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43236 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43370 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52911 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52914 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53040 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53043 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53046 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53068 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53130 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53186 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53198 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-50634 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50708 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50759 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50785 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53707 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53714 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53742 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53748 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53855 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54047 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54059 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54105 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54125 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54151 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54180 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54187 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36331 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-27558 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40012 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40032 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40036 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40073 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40077 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40084 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40093 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40095 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40107 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40137 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40180 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40192 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40193 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40208 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40266 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40285 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40286 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40288 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40289 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40310 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40311 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40332 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40333 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40335 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40337 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40356 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40358 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-54505 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-62626 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68175 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68184 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68190 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68196 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68201 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68230 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68246 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68256 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68311 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68315 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68322 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68772 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68781 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68786 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68806 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68809 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71067 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71192 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71195 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71198 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23176 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23182 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23245 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23364 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31409 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31417 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31477 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31494 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31597 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31598 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31602 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31611 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31612 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31622 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31626 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31629 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31683 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31711 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31768 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43117 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43184 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43203 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43245 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43336 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43373 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43377 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43476 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45935 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45958 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46006 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46062 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46112 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46124 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46177 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46328 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52919 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52922 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52931 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52934 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53041 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53045 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53329 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53356 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-53374 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-53375 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-53376 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-53377 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-53382 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-53383 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-53386 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-53387 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-53390 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63793 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63796 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63798 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63806 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63814 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63815 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63817 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63818 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63827 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63828 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63833 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63834 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63835 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63836 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63846 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63847 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63848 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63854 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63855 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63856 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63862 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63879 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63881 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63882 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63895 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63905 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63908 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63915 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63930 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63931 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63933 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63934 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63954 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63959 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63960 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-63967 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-64010 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-64033 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64055 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64056 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64083 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64084 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64085 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64086 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64087 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64088 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64089 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64090 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-64091 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-64093 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-64094 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-64095 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-64096 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64097 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-64135 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64138 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-64164 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64165 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64166 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64168 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64188 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | — | Not Applicable |
| CVE-2026-31396 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31761 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43207 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43232 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43283 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43291 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43324 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43497 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46250 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46265 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46270 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53161 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53216 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53217 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53273 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-10037 | NONE0 | mailcap 3.70+nmu1ubuntu1 fixed in 3.70+nmu1ubuntu1.22.04.1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.10 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.10-minimal 3.10.12-1~22.04.15 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-10813 | NONE0 | lmcache 0.4.6 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| GHSA-4xgf-cpjx-pc3j | NONE0 | pydantic-settings 2.14.1 fixed in 2.14.2 | — | Not Applicable |
| CVE-2025-3000 | NONE0 | torch 2.11.0+cu130 fixed in 2.13.0 | 0.2% Theoretical Threat | Not Applicable |
| GHSA-4w2j-m93h-cj5j | NONE0 | quinn-proto 0.11.14 fixed in 0.11.15 | — | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.