Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker could exploit CVE-2026-8376 or CVE-2026-40962 to achieve remote code execution or cause denial of service via crafted inputs. The vulnerabilities are present in libraries that may not be directly exposed through the vLLM service, but they increase the overall attack surface. It is recommended to apply available patches and limit network exposure.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| 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 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.1% Theoretical Threat | 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 | 5.2% 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-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.6% Theoretical Threat | Directly Exposed |
| CVE-2026-54058 | HIGH7.73 | pillow 12.2.0 fixed in 12.3.0 | 0.4% 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-41409 | HIGH7.5 | libpcre2-8-0 10.39-3ubuntu0.1 No fix yet | 1.1% 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-2026-28388 | HIGH7.5 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28389 | HIGH7.5 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28390 | HIGH7.5 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 1.0% 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-4899 | HIGH7.5 | libzstd1 1.4.8+dfsg-3build1 No fix yet | 1.6% 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-2025-1594 | HIGH7.48 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1594 | HIGH7.48 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1594 | HIGH7.48 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1594 | HIGH7.48 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1594 | HIGH7.48 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1594 | HIGH7.48 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1594 | HIGH7.48 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1594 | HIGH7.48 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | 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-59197 | MEDIUM6.97 | pillow 12.2.0 fixed in 12.3.0 | 0.4% 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.8% 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-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-2016-2568 | MEDIUM6.63 | libpolkit-agent-1-0 0.105-33ubuntu0.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-2568 | MEDIUM6.63 | libpolkit-gobject-1-0 0.105-33ubuntu0.1 No fix yet | 0.4% 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-2016-2568 | MEDIUM6.63 | policykit-1 0.105-33ubuntu0.1 No fix yet | 0.4% Theoretical Threat | 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-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.6% 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.6% 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.6% 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.6% 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.6% 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.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | libelf1 0.186-1ubuntu0.1 No fix yet | 0.7% 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.6% 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.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libk5crypto3 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libk5crypto3 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5-3 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5-3 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5support0 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5support0 1.19.2-2ubuntu0.7 fixed in 1.19.2-2ubuntu0.8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-6603 | MEDIUM6.38 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% 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-2023-6603 | MEDIUM6.38 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% 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.6% 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-59939 | MEDIUM6.38 | python3-httplib2 0.20.2-2 fixed in 0.20.2-2ubuntu0.1 | 0.4% 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-59199 | MEDIUM6.38 | pillow 12.2.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59200 | MEDIUM6.38 | pillow 12.2.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59204 | MEDIUM6.38 | pillow 12.2.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59205 | MEDIUM6.38 | pillow 12.2.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59198 | MEDIUM6.38 | pillow 12.2.0 fixed in 12.3.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59203 | MEDIUM6.38 | pillow 12.2.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59885 | MEDIUM6.38 | pyasn1 0.6.3 fixed in 0.6.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59886 | MEDIUM6.38 | pyasn1 0.6.3 fixed in 0.6.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54234 | MEDIUM6.38 | vllm 0.23.1rc1.dev301+g04c2a8dea fixed in 0.24.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-55574 | MEDIUM6.38 | vllm 0.23.1rc1.dev301+g04c2a8dea fixed in 0.24.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53923 | MEDIUM6.38 | vllm 0.23.1rc1.dev301+g04c2a8dea fixed in 0.24.0 | 0.3% Theoretical Threat | 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.4% 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-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-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-2024-2236 | MEDIUM5.9 | libgcrypt20 1.9.4-3ubuntu3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 1.2% 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-2026-42014 | MEDIUM5.61 | libgnutls30 3.7.3-4ubuntu1.7 fixed in 3.7.3-4ubuntu1.9 | 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 fixed in 2.35-0ubuntu3.14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.35-0ubuntu3.13 fixed in 2.35-0ubuntu3.14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.35-0ubuntu3.13 fixed in 2.35-0ubuntu3.14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.35-0ubuntu3.13 fixed in 2.35-0ubuntu3.14 | 0.4% 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.6% 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-55514 | MEDIUM5.52 | vllm 0.23.1rc1.dev301+g04c2a8dea fixed in 0.24.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54233 | MEDIUM5.52 | vllm 0.23.1rc1.dev301+g04c2a8dea fixed in 0.24.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54235 | MEDIUM5.52 | vllm 0.23.1rc1.dev301+g04c2a8dea fixed in 0.24.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-55646 | MEDIUM5.52 | vllm 0.23.1rc1.dev301+g04c2a8dea 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-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-13757 | MEDIUM5.27 | libp11-kit0 0.24.0-6build1 No fix yet | 0.1% 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-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-2025-15281 | MEDIUM5.02 | libc-bin 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.13 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-dev-bin 2.35-0ubuntu3.13 fixed in 2.35-0ubuntu3.14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.35-0ubuntu3.13 fixed in 2.35-0ubuntu3.14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.35-0ubuntu3.13 fixed in 2.35-0ubuntu3.14 | 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-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.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.6% 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-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-34180 | MEDIUM5 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | MEDIUM4.86 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2013-7445 | MEDIUM4.68 | linux-libc-dev 5.15.0-181.191 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19378 | MEDIUM4.68 | linux-libc-dev 5.15.0-181.191 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19814 | MEDIUM4.68 | linux-libc-dev 5.15.0-181.191 No fix yet | 3.3% Low-Moderate Risk | Post-Exploit |
| 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 | libhwasan0 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-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-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.6% 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-45445 | MEDIUM4.64 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.6% 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-2022-0400 | MEDIUM4.5 | linux-libc-dev 5.15.0-181.191 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-38501 | MEDIUM4.5 | linux-libc-dev 5.15.0-181.191 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-20426 | MEDIUM4.5 | linux-libc-dev 5.15.0-181.191 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28388 | MEDIUM4.5 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28389 | MEDIUM4.5 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28390 | MEDIUM4.5 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | MEDIUM4.5 | patch 2.7.6-7build2 No fix yet | 8.2% 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 fixed in 2.35-0ubuntu3.14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-dev-bin 2.35-0ubuntu3.13 fixed in 2.35-0ubuntu3.14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.35-0ubuntu3.13 fixed in 2.35-0ubuntu3.14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6-dev 2.35-0ubuntu3.13 fixed in 2.35-0ubuntu3.14 | 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 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl3 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.6% 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-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.1rc1.dev301+g04c2a8dea 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.6% Theoretical Threat | Post-Exploit |
| CVE-2026-43037 | MEDIUM4.49 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-23395 | MEDIUM4.49 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23455 | MEDIUM4.26 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.35-0ubuntu3.11 fixed in 2.35-0ubuntu3.14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-dev-bin 2.35-0ubuntu3.13 fixed in 2.35-0ubuntu3.14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-dev-bin 2.35-0ubuntu3.13 fixed in 2.35-0ubuntu3.14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.35-0ubuntu3.13 fixed in 2.35-0ubuntu3.14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.35-0ubuntu3.13 fixed in 2.35-0ubuntu3.14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6-dev 2.35-0ubuntu3.13 fixed in 2.35-0ubuntu3.14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6-dev 2.35-0ubuntu3.13 fixed in 2.35-0ubuntu3.14 | 0.4% 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-31788 | MEDIUM4.18 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8925 | MEDIUM4.13 | curl 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | curl 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8925 | MEDIUM4.13 | libcurl3-gnutls 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl3-gnutls 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8925 | MEDIUM4.13 | libcurl4 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl4 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43114 | MEDIUM4.13 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43112 | MEDIUM4.13 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | MEDIUM4.13 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-12491 | MEDIUM4.08 | vllm 0.23.1rc1.dev301+g04c2a8dea 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-43133 | MEDIUM4.03 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-15794 | MEDIUM4.02 | linux-libc-dev 5.15.0-181.191 No fix yet | 1.2% Low-Moderate 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-2024-32230 | LOW3.98 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-37777 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23216 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31402 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-49359 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49910 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49935 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50095 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50212 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50213 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50234 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53629 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53673 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53179 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-21812 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22040 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-22041 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-37778 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-37899 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-37926 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37952 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38349 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38437 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38552 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39863 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39952 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71073 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71089 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23171 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23208 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23226 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-23227 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23378 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23428 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31532 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31709 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31720 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31729 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31759 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43049 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43329 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43378 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43499 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-45891 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46274 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53148 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53262 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53359 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2020-14356 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-3238 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48744 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48771 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48990 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48998 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49471 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-50071 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50090 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50163 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50240 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50303 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-0030 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-2007 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-26242 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52452 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52624 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-52751 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52837 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52916 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52921 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53037 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53072 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53187 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53218 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26699 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26742 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26842 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35932 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35949 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36012 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36898 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36914 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36921 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38556 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40900 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40954 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40989 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41045 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41050 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41069 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41074 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42117 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42118 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42147 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43842 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46729 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46811 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46813 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46820 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46833 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46836 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47745 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49880 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49931 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49991 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49992 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50063 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50112 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50246 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53098 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53133 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56604 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21927 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21945 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21967 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37903 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37928 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-37947 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38201 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38369 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38734 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71238 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23193 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23281 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23447 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23448 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31452 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31578 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31581 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31696 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43196 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43250 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45839 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45902 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45916 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45920 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45936 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45946 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45984 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46004 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46047 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46068 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46069 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46075 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46122 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46163 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46180 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46189 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46219 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46234 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46241 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46243 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-52943 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52962 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52969 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52992 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53004 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53136 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53137 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53294 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53296 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64600 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2017-13165 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-12930 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2018-12931 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-26934 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49722 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49980 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50256 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50406 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50492 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50518 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50552 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-33053 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53052 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53320 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53510 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53544 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53596 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26983 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35868 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50217 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-56609 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57887 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21734 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21863 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21915 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22083 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23133 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37786 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37822 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37861 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-37957 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38069 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38117 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38118 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38131 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38239 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38250 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38259 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38361 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38422 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38485 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38595 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38702 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39797 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39810 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39859 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71152 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71220 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23068 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23221 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23234 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23262 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23359 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23361 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31399 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31455 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31485 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31489 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31493 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31500 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31527 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31576 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31580 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31583 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31686 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31702 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31715 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31747 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31748 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43015 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43020 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43027 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43205 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43328 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43426 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43458 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45866 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45867 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45879 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45885 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46267 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46285 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46294 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46301 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53059 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53089 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53112 | LOW3.98 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53115 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53117 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53120 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53129 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53156 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53157 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53195 | LOW3.98 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% 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 | polkitd 0.105-33ubuntu0.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-21759 | LOW3.96 | linux-libc-dev 5.15.0-181.191 No fix yet | 7.4% Low-Moderate Risk | Post-Exploit |
| 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-2023-1193 | LOW3.9 | linux-libc-dev 5.15.0-181.191 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-6603 | LOW3.82 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% 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.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl4 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43501 | LOW3.82 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-31669 | LOW3.82 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43186 | LOW3.82 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-46195 | LOW3.82 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-53071 | LOW3.82 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53266 | LOW3.82 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-25836 | LOW3.82 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-36347 | LOW3.82 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40210 | LOW3.82 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43110 | LOW3.82 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43190 | LOW3.82 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% 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-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-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.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22037 | LOW3.79 | linux-libc-dev 5.15.0-181.191 No fix yet | 37.1% High Exploitation Risk | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | curl 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl3-gnutls 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl4 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-40170 | LOW3.77 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2019-14899 | LOW3.77 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW3.77 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.4% 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-43038 | LOW3.72 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31607 | LOW3.72 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43074 | LOW3.72 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-53781 | LOW3.72 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23243 | LOW3.72 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46135 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46259 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49172 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49218 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49234 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49401 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49518 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49961 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50551 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52682 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52701 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53254 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53376 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53575 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53751 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-6610 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-14040 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26954 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-35937 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35939 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36013 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-36915 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41013 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41935 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49861 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49928 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50164 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53147 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53216 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57945 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57982 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58015 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58054 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21946 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21985 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22038 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-22039 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-22104 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22107 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37879 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38081 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38329 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38330 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38340 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38679 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38728 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39744 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39750 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39761 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39901 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40064 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40082 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68183 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68324 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23204 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23235 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23315 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23318 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23388 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23397 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31568 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31614 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31685 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31778 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43040 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43051 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43052 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43141 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43241 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43281 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43386 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43427 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43449 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43450 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43453 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45893 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45957 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45994 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46022 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46033 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46053 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46056 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-46064 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46120 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46150 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46191 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46209 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52968 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53138 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53149 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53179 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53303 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53309 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53330 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43126 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43380 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43414 | LOW3.62 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53255 | LOW3.62 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| 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-2026-43304 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46043 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-52989 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-52993 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53002 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-54518 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-23191 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23392 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31586 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31663 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31694 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43116 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43198 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43341 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43493 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45852 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46119 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46275 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46319 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52924 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53006 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53036 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53072 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53185 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53212 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53224 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53239 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53254 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53256 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53264 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53270 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53275 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-3864 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2022-1247 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-2961 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52586 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49855 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50106 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50286 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-57876 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37776 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39759 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39826 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39905 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40135 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40158 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40168 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71203 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71221 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23050 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23054 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23270 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23454 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31408 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43050 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43158 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43226 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43233 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43334 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43339 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45856 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45859 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45860 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-45942 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45970 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46015 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46052 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46054 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46090 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46099 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-46116 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46123 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46133 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-46149 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46174 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46181 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46227 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46266 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-46324 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52912 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52917 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52918 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-52920 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-52933 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52935 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52942 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52945 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-52947 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52956 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-52957 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-52986 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-52991 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52998 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53000 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53005 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53009 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53011 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53016 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53049 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53075 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53091 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53131 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53133 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53223 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53228 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53246 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53268 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53354 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53355 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53357 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53381 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53384 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53388 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53391 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53392 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53393 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53397 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53398 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53399 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63794 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63800 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63801 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63807 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-63808 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63809 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63823 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-63824 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-63826 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63829 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-63830 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-63831 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63875 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63887 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-63888 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-63889 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-63891 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-63898 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63899 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63901 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63912 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-63913 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63914 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63916 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-63917 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63919 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63920 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63921 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63922 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-63924 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-63925 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-63928 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63940 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63947 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-63956 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63957 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63958 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63962 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63971 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63975 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-63984 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63992 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63993 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63994 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-64001 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64002 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64007 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-64009 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64011 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64015 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64018 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64025 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-64026 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64032 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64034 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64047 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-64048 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-64098 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64102 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-64109 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64111 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64113 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-64114 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64115 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64137 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64174 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64189 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64191 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64192 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64255 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64271 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64276 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64277 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64280 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64296 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64298 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64303 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-64322 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64324 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64342 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64355 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-64364 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-64372 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64378 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64401 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64448 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-64456 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64530 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-64531 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64534 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64539 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64543 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64548 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64551 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64554 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-45885 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-21739 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31508 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45894 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53053 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53062 | LOW3.57 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53078 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53189 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53230 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53253 | LOW3.57 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-3714 | LOW3.54 | linux-libc-dev 5.15.0-181.191 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2018-1121 | LOW3.54 | linux-libc-dev 5.15.0-181.191 No fix yet | 4.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-31790 | LOW3.54 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.23 | 1.2% Low-Moderate Risk | Post-Exploit |
| 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-2026-53196 | LOW3.47 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-46331 | LOW3.42 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-50616 | LOW3.42 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53095 | LOW3.42 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57795 | LOW3.42 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21714 | LOW3.42 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| 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-2022-50851 | LOW3.37 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45991 | LOW3.37 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53267 | LOW3.37 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| 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-2026-53176 | LOW3.31 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2015-8553 | LOW3.31 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-53785 | LOW3.31 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40336 | LOW3.31 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23179 | LOW3.31 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31588 | LOW3.31 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64535 | LOW3.31 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-0564 | LOW3.31 | linux-libc-dev 5.15.0-181.191 No fix yet | 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-aarch64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010204 | LOW3.3 | binutils-aarch64-linux-gnu 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-2025-38562 | LOW3.3 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 7.6% 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-23450 | LOW3.26 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-31502 | LOW3.26 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31516 | LOW3.26 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52910 | LOW3.26 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53033 | LOW3.26 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53090 | LOW3.26 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39978 | LOW3.26 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40074 | LOW3.26 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68371 | LOW3.26 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23456 | LOW3.26 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-44032 | LOW3.26 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-44033 | LOW3.26 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-44034 | LOW3.26 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-45888 | LOW3.26 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-37924 | LOW3.23 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 11.0% High Exploitation Risk | Post-Exploit |
| CVE-2024-40918 | LOW3.21 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-57893 | LOW3.21 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40307 | LOW3.21 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | 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-2026-23253 | LOW3.16 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54081 | LOW3.16 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40146 | LOW3.16 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | 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.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40190 | LOW3.11 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31449 | LOW3.11 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31700 | LOW3.11 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31708 | LOW3.11 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52829 | LOW3.11 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-53850 | LOW3.11 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40071 | LOW3.11 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40080 | LOW3.11 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40355 | LOW3.11 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68342 | LOW3.11 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68343 | LOW3.11 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68736 | LOW3.11 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43134 | LOW3.11 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31464 | LOW3.11 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31570 | LOW3.11 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59890 | LOW3.11 | setuptools 80.10.2 fixed in 83.0.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-52481 | LOW3.06 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-31649 | LOW3.06 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-53764 | LOW3.01 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40242 | LOW3.01 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35870 | LOW3.01 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% 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.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.6% 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-40962 | LOW3 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-40962 | LOW3 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-40962 | LOW3 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-40962 | LOW3 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.1% 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-40962 | LOW3 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.1% 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-2026-34180 | LOW3 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-23240 | LOW2.96 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-23271 | LOW2.96 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31414 | LOW2.96 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-53789 | LOW2.96 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54107 | LOW2.96 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40237 | LOW2.96 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40323 | LOW2.96 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40340 | LOW2.96 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68742 | LOW2.96 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23239 | LOW2.96 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31426 | LOW2.96 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43279 | LOW2.96 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46065 | LOW2.96 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46113 | LOW2.96 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52923 | LOW2.96 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31392 | LOW2.96 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% 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-2022-49138 | LOW2.91 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49569 | LOW2.91 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46024 | LOW2.91 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-36350 | LOW2.86 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-36357 | LOW2.86 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| 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-2017-0537 | LOW2.82 | linux-libc-dev 5.15.0-181.191 No fix yet | 1.0% Low-Moderate Risk | 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-aarch64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | binutils-aarch64-linux-gnu 2.38-4ubuntu2.12 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-48064 | LOW2.8 | binutils-aarch64-linux-gnu 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-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-31637 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-45988 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-56692 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71315 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23066 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23222 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23340 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23391 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23449 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31403 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31447 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31454 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31469 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31473 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31507 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31548 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31665 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31673 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31678 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31680 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31758 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43009 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43016 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43030 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43060 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43091 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43093 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43111 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43153 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43214 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43365 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43406 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43407 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43437 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43456 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43502 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45850 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45864 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45899 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46273 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46304 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46320 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52909 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52958 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53050 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53086 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53159 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53269 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2015-7837 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2016-8660 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-4095 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-47432 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47658 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-0480 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-38457 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-40133 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-4543 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-48628 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48633 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48673 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48706 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48766 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48887 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48929 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48976 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48979 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49069 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49108 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49123 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49124 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49125 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49133 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49134 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49161 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49167 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49173 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49177 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49178 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49203 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49245 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49296 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49303 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49306 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49317 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49333 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49342 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49393 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49420 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49469 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49476 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49484 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49496 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49504 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49516 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49528 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49529 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49531 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49533 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49534 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49539 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49543 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49547 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49552 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49562 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49622 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49699 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49742 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49750 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49759 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49764 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49766 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49773 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49783 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49803 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49810 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49829 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49833 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49858 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49901 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49932 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49940 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49943 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49955 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49965 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49971 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49974 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49997 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50002 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50009 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50015 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50016 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50073 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50116 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50166 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50167 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50178 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50195 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50224 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50230 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50232 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50236 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50260 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50266 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50284 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50304 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50316 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50322 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50332 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50354 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50357 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50380 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50383 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50390 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50393 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50407 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50418 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50425 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50461 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50464 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50467 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50479 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50500 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50527 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50539 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50550 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50554 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50571 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50627 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50704 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50746 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50748 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50772 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50815 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50862 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50863 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50871 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-0160 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-31082 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-52485 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52569 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52576 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52582 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52590 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52591 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52625 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52632 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52634 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52648 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52653 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52657 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52660 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52671 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52673 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52676 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52700 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52732 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52737 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52761 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52831 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52857 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52879 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52888 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52905 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52920 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52939 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52981 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53002 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53008 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53009 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53010 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53036 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53042 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53068 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53093 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53105 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53115 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53149 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53152 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53168 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53180 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53198 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53209 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53221 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53231 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53240 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53247 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53248 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53258 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53261 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53292 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53323 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53325 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53332 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53347 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53348 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53353 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53355 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53362 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53366 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53367 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53370 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53371 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53382 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53383 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53385 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53387 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53410 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53424 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53429 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53434 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53438 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53460 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53466 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53483 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53491 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53509 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53529 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53538 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53539 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53540 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53545 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53547 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53558 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53561 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53562 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53574 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53584 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53588 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53602 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53609 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53620 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53627 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53628 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53635 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53647 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53651 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53657 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53671 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53682 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53685 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53694 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53702 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53721 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53743 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53753 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53765 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53767 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53780 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53806 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53822 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53829 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53846 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53849 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53867 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54002 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54016 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54019 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54023 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54028 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54052 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54067 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54088 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54121 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54129 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54190 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54234 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54237 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54242 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54259 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54271 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54280 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54324 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-14027 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26595 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26605 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26647 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26656 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26658 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26691 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26714 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26719 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26740 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26756 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26759 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-26767 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26770 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26807 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26844 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26853 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26866 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26876 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26938 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26948 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26953 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27002 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27005 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27014 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27025 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-27032 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-27035 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-27041 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-27056 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27057 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27062 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27389 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27400 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27418 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27435 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35784 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35794 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35799 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35801 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35803 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35808 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35826 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35832 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35839 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35843 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35865 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35875 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35878 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2024-35908 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35924 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35926 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35931 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35942 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35945 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35946 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35956 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35959 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-35971 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35995 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35998 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35999 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36000 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36009 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36021 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36026 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36244 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36478 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-36479 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36900 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36909 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36911 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36917 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36918 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36920 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36922 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36924 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36948 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36951 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36966 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-37021 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38543 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38554 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38557 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38564 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38594 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38608 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38625 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-39282 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-39298 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-40966 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40972 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-40975 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40977 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-40979 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40998 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40999 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41001 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41008 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41023 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41030 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41031 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41036 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41062 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41067 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41075 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41079 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41082 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41088 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42067 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42091 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42110 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42122 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-42125 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42128 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42129 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42139 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42239 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42273 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42319 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42320 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42321 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43823 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43824 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43831 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43832 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43844 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43872 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43899 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43911 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43912 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44950 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44961 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44962 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44963 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44970 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-45010 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-45015 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46678 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46681 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46705 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46715 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46716 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46717 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46718 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46720 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46726 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46727 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46728 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46730 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46733 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46748 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46749 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46754 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46762 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46765 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46770 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46775 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46802 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46803 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46806 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46808 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46823 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46834 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46835 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46842 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46843 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46848 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46857 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46860 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46861 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47141 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47658 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47661 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47662 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47664 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47678 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47683 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47703 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47704 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47728 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47736 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47794 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47809 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-48873 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49568 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49870 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49888 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49891 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49893 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49898 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49899 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49901 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49904 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49905 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49906 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49908 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49909 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49910 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49911 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49912 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49914 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49915 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49916 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49917 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49918 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49919 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49920 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49921 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49922 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49923 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49929 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49932 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49939 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49940 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49945 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49970 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49978 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49987 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49988 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49990 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49994 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50012 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50014 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50017 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50028 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50034 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50048 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50056 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50098 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50138 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50146 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50166 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50187 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50271 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50284 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50285 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50289 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50298 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-52559 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-52560 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53056 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53079 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53091 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53175 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53187 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53190 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53195 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53196 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53210 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53219 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53220 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53221 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53224 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53234 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53687 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-54683 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56368 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56544 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56557 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56565 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56566 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56583 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56584 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56588 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56591 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56592 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56607 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56611 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56639 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56641 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56647 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56657 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56660 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56665 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56671 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56677 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-56703 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56707 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56709 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56712 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56717 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56718 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56719 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56722 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56727 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56782 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57804 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57809 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57843 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57852 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57872 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57875 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57888 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57895 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57924 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57950 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57952 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57975 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57976 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57993 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57999 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58012 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58018 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58019 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58053 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58077 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58089 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58094 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58095 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58096 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58097 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58098 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58100 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58238 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58241 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21629 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21634 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21635 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21649 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21656 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21658 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21667 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21672 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21673 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21682 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21696 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21712 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21723 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21730 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21738 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21750 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21752 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21768 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21792 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21801 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21816 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21817 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21819 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21821 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21831 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21832 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21833 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21838 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21872 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21881 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21885 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21891 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21894 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21899 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21908 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21918 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21931 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21944 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21955 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21972 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21976 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21986 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22019 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22026 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22028 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22042 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22043 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22053 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22057 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22072 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22090 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22103 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22105 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22109 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22113 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22124 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22125 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22127 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23130 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23131 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23132 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23141 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23155 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23160 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23162 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37743 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37744 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37745 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37746 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37747 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37775 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37806 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37807 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37820 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37833 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37834 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37842 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37852 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37853 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37855 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37856 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37870 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37876 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37877 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37878 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37880 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37884 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37907 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37931 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37938 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37945 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37951 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37954 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37956 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37959 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37961 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37980 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37984 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38006 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38011 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38014 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38015 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38020 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38029 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38033 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38036 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38038 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38039 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38040 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38041 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38042 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38045 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38047 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38059 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38060 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38062 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38063 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38064 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38070 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38071 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38080 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38092 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38096 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38097 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38098 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38099 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38105 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38126 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38127 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38140 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38162 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38166 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38168 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38189 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38191 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-38192 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38199 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38202 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38205 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38207 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38208 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38215 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38225 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38244 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38261 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38264 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38269 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38272 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38275 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38300 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38321 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38331 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38333 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38334 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38343 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38353 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38359 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38360 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38368 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38373 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38409 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38426 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38436 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38438 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38449 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38491 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38503 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38507 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38520 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38531 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38544 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38560 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38590 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38615 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38621 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38626 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38643 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38644 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38659 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38665 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38692 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38705 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38709 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38710 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38716 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39677 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39692 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39705 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39706 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39707 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39715 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39716 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39720 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39732 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39745 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39746 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39747 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39748 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39753 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39762 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39763 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39764 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39770 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39771 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39779 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39781 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39789 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39800 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39819 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39827 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39829 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39833 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39838 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39850 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39851 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39886 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39908 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39925 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39929 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39931 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39932 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39933 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39940 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39942 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39947 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39989 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39990 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40005 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40057 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40075 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40099 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40100 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40102 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40103 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40104 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40160 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40195 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40196 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40251 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40284 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40287 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40305 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40325 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40334 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40339 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40347 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40362 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-68171 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68173 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68178 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68188 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68193 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68206 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68219 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68223 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68231 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68236 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68265 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68281 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68283 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68297 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68307 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68309 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68310 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68313 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68317 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68333 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68334 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68345 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68358 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68363 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68378 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68379 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68778 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68794 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68798 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68802 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68822 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71095 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71107 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71109 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71115 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71150 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71158 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71160 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71161 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71183 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71184 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71202 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71204 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71222 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71223 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71227 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71229 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71232 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71233 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71235 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71236 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71237 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71239 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71265 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71266 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71267 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71268 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71269 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71272 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71273 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71285 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71287 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71289 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71290 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71291 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71292 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71293 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71294 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71295 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71297 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71299 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71300 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71302 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22979 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22996 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23000 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23031 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23069 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23086 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23088 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23100 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23113 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23137 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23138 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23141 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23154 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23157 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23190 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23196 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23202 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23206 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23213 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23214 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23215 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23217 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23220 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23228 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23229 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23236 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23237 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23238 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23241 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23242 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-23247 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23255 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23256 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23257 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23258 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23259 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23260 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23261 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23264 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23265 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23266 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23267 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23272 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23276 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23277 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23278 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23279 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23285 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23286 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23287 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23289 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23290 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23291 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23292 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23293 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23296 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23298 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23300 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23303 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23304 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23307 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23310 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23312 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23324 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23330 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23334 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23335 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23339 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23347 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23352 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23356 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23357 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23362 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23365 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23367 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23368 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23370 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23371 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23374 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23379 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23381 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23382 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23389 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23396 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23398 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23399 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23401 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23420 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23434 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23438 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23439 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23442 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23446 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23460 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23462 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-23465 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23468 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23472 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23474 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31391 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31394 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31400 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31407 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31410 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31411 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31412 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31415 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31416 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31418 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31420 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31421 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31422 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31423 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31424 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31425 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31427 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31428 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31441 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31450 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-31451 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31461 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31462 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31467 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31480 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31483 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31486 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31487 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31492 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31495 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31496 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31497 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31498 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31503 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31509 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31510 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31512 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31515 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31518 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31519 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31520 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31521 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31522 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31524 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31531 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31537 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31540 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31545 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31546 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31549 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31550 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31551 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31552 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-31555 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31557 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31560 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31565 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31577 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31579 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31585 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31590 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31592 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31594 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31595 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31596 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31599 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31603 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31605 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31606 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31610 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31615 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31616 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31617 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31618 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31619 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31623 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31624 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31625 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31628 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31630 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31634 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31642 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31651 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31658 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31660 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31661 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31662 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31664 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31670 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31671 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31672 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31674 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31675 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31676 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31677 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31679 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31681 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31682 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-31684 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31687 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31692 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31698 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31699 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31701 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31704 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31721 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31722 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31723 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31724 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31725 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31726 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31737 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31738 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31749 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31752 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31754 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31755 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31756 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31762 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31763 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31767 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31770 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31773 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31777 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31781 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43014 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43021 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43022 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43024 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43025 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43026 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43028 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43032 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43035 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43036 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43041 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43042 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43043 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43045 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43046 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43048 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43054 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43058 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43061 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43062 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43064 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43065 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43066 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43068 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43069 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43072 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43073 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43079 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43080 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43085 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43088 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43089 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43098 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43099 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43101 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43103 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43104 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43105 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43107 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43109 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43113 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43115 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43118 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43119 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43123 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43124 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43127 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43129 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43130 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43131 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43132 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43135 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43136 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43137 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43139 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43140 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43143 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43145 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43147 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43148 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43149 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43152 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43156 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43159 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43161 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43162 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43165 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43167 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43168 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43170 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43171 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43172 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43173 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43182 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43183 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43187 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43189 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43191 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43194 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43195 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43200 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43201 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43202 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43204 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43209 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43213 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43216 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43218 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43219 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43220 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43223 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43225 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43227 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43228 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43230 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43231 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43234 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43242 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43243 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43244 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43246 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43251 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43253 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43255 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43257 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43261 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43262 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43264 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43266 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43267 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43268 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43269 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43270 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43271 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43273 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43277 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43287 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43288 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43289 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43292 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43294 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43295 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43296 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43298 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43299 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43300 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43302 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43305 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43306 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43308 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43309 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43310 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43311 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43312 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43313 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43314 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43315 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43316 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43317 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43318 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43319 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43320 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43327 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43333 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43338 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43340 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43343 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43344 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43350 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43355 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43357 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43359 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43361 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43362 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43363 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43381 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43382 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43387 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43398 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43400 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43405 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43409 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43410 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43411 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43413 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43416 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43419 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43421 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43424 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43425 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43428 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43429 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43432 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43436 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43445 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43451 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43452 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43459 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43466 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43469 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43471 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43472 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43473 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43474 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43475 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43483 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43491 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43492 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43496 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45834 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45835 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45836 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45840 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45842 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45843 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-45846 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45847 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45848 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45855 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45857 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45873 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45890 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45904 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45912 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45915 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45917 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45919 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45923 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45924 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45930 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45934 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45940 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45941 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45944 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45948 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45954 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45960 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45961 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45964 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45965 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45968 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45969 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45974 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45978 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45981 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45983 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45985 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45986 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45987 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45997 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45999 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46000 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46002 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46003 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46009 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46012 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46014 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46018 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46019 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46021 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46023 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46026 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46027 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46032 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46037 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46038 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46040 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46044 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46046 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46049 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46050 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46051 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46059 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46070 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46072 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46077 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46078 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46080 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46082 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46083 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46086 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46088 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46091 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46092 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46098 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46101 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46102 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46103 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46107 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46108 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46127 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46128 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46132 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46137 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46146 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46151 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46153 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46157 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46158 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46160 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46161 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46167 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46168 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46169 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46170 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46172 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46178 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46184 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46186 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46193 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46196 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46200 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46214 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46220 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46225 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46226 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46229 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46231 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46233 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46235 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46236 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46247 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46302 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46303 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-46321 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46322 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52913 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52915 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52916 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52921 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52925 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52926 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52927 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52928 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52929 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-52930 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52936 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52937 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52939 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52944 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52946 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-52948 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52954 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-52960 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-52963 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52970 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52972 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52975 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52977 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52981 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-52984 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52985 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52988 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52990 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52995 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52999 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53001 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53003 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53012 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53015 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53017 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53018 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53021 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53022 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53023 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53034 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53037 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53039 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53056 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53064 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53066 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53069 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53074 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53076 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53077 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53080 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53083 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53088 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53107 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53122 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53128 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53134 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53139 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53150 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53167 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53168 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53181 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53199 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53208 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53218 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53219 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53220 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53221 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53227 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53245 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53252 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53263 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53284 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53287 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53289 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53291 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53292 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53295 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53304 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53306 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53313 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53314 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53317 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53320 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53325 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53327 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53331 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53332 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53337 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53339 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53345 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53349 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53353 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53358 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53369 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53376 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53377 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53379 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53385 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53400 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53402 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53403 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63803 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-63810 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63822 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63832 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63858 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-63860 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-63865 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-63867 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-63868 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63870 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-63872 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-63890 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63892 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63893 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-63897 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63900 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63902 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63903 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63904 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63926 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63927 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63942 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63948 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63961 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63963 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63964 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63973 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63976 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-63983 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63985 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-63990 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63991 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63999 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64004 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64005 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64006 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64012 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64014 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64039 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64046 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-64076 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64077 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64078 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64079 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64103 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64106 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64112 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64116 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-64118 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64123 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64125 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-64126 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64133 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64144 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64153 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64155 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64170 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64173 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64176 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64177 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64178 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64179 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64185 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64187 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64190 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64206 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-64210 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-64212 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64213 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64220 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64222 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64225 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64227 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64231 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64237 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64243 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64245 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64275 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64294 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64299 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64316 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64332 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64334 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64338 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64346 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64351 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64352 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64362 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64363 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64373 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64403 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-64406 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-64423 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64424 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64435 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-64452 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64478 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64496 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64507 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64512 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64514 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64524 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64537 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64540 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64541 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64544 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64545 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64546 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64547 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-64553 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2017-13693 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2018-12928 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2018-12929 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-3114 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49651 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-4133 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27010 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27011 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50009 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53093 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58237 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21645 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21693 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37800 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71304 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71313 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23198 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23336 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23444 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31446 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31448 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31453 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31667 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31771 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43071 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43180 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43211 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43352 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43353 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43480 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43484 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45838 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45841 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45844 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45858 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45862 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45868 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45869 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45870 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45871 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45872 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45875 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45877 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45883 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45911 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46147 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46245 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46249 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46252 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46253 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46254 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46280 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46291 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46292 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46299 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46307 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46312 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52982 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53035 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53047 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53048 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53060 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53061 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53063 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53065 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53070 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53073 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53082 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53093 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53096 | LOW2.8 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53106 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53111 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53135 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53146 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53147 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53158 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53177 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53207 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53213 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53225 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53226 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53229 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53232 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53236 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53237 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53238 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53249 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53258 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53265 | LOW2.8 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% 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.6% 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-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-2022-3523 | LOW2.7 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-50700 | LOW2.7 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54181 | LOW2.7 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47689 | LOW2.7 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-40353 | LOW2.7 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71225 | LOW2.7 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23457 | LOW2.7 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53194 | LOW2.7 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-64538 | LOW2.7 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-40217 | LOW2.65 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40338 | LOW2.65 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50721 | LOW2.6 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71193 | LOW2.6 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23035 | LOW2.6 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23180 | LOW2.55 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.1% 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-52955 | LOW2.4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-57857 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21947 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-23004 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23169 | LOW2.4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43047 | LOW2.4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-1205 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-48816 | LOW2.4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49967 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50350 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52589 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53178 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53401 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53447 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53452 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53478 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53794 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53816 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54035 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54071 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54149 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54185 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54201 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54323 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26869 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27408 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36024 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36949 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38306 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39293 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39508 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42107 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42253 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43866 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46870 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49859 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50135 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53176 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53178 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56788 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57974 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21651 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21732 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21825 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37920 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38234 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38440 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38524 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38717 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39726 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39754 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39825 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39884 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39927 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39961 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39977 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39992 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40016 | LOW2.4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40039 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40139 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40250 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68214 | LOW2.4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68239 | LOW2.4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68296 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68745 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71074 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71274 | LOW2.4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23110 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23118 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23126 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23181 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23207 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23212 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23302 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23348 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23452 | LOW2.4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23463 | LOW2.4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31393 | LOW2.4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31466 | LOW2.4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31523 | LOW2.4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31697 | LOW2.4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31728 | LOW2.4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31751 | LOW2.4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43053 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43163 | LOW2.4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43275 | LOW2.4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43342 | LOW2.4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43383 | LOW2.4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43420 | LOW2.4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43430 | LOW2.4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43439 | LOW2.4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43448 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45905 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45949 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46159 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46187 | LOW2.4 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53108 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53352 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52749 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50183 | LOW2.4 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% 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-2019-15213 | LOW2.35 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4010 | LOW2.35 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-49934 | LOW2.35 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-45896 | LOW2.29 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23458 | LOW2.24 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-17977 | LOW2.24 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-50720 | LOW2.24 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52508 | LOW2.24 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53733 | LOW2.24 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54247 | LOW2.24 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54253 | LOW2.24 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54263 | LOW2.24 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26648 | LOW2.24 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26662 | LOW2.24 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26672 | LOW2.24 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26757 | LOW2.24 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26758 | LOW2.24 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36910 | LOW2.24 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38628 | LOW2.24 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40123 | LOW2.24 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40198 | LOW2.24 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40206 | LOW2.24 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68768 | LOW2.24 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2020-14304 | LOW2.24 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-41848 | LOW2.14 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48646 | LOW2.09 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| 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-2025-1152 | LOW1.89 | binutils 2.38-4ubuntu2.12 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-aarch64-linux-gnu 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-2023-53791 | LOW1.89 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW1.89 | openssl 3.0.2-0ubuntu1.20 fixed in 3.0.2-0ubuntu1.25 | 0.4% 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-2020-35501 | LOW1.73 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% 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-aarch64-linux-gnu 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-2023-52926 | LOW1.68 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48667 | LOW1.68 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48668 | LOW1.68 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50628 | LOW1.68 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50778 | LOW1.68 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50811 | LOW1.68 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52561 | LOW1.68 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53992 | LOW1.68 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54145 | LOW1.68 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54172 | LOW1.68 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54227 | LOW1.68 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54233 | LOW1.68 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54261 | LOW1.68 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54320 | LOW1.68 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47738 | LOW1.68 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50057 | LOW1.68 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50211 | LOW1.68 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57898 | LOW1.68 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40268 | LOW1.68 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40303 | LOW1.68 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40341 | LOW1.68 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71224 | LOW1.68 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31668 | LOW1.68 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-185.195 | 0.4% 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-2026-40228 | LOW1.68 | systemd-sysv 249.11-0ubuntu3.21 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| 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-aarch64-linux-gnu 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-2022-50583 | LOW1.17 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42155 | LOW0.97 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59950 | NONE0 | mcp 1.28.0 fixed in 1.28.1 | 0.1% Theoretical Threat | Not Applicable |
| 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-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-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.3% 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.4% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% 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.4% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% 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.4% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% 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.4% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% 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.4% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% 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.4% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% 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.3% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl4 7.81.0-1ubuntu1.24 fixed in 7.81.0-1ubuntu1.25 | 0.3% 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.4% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% 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-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.4% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% 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.4% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% 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.7% 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.6% 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.4% 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.1% 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.1% 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.1% Theoretical Threat | Not Applicable |
| CVE-2026-53356 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53374 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53375 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53382 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53383 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53386 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53387 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53390 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63793 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63796 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63798 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63806 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63814 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63815 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63817 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63818 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63827 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63828 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63833 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63834 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63835 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63836 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63846 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63847 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63848 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63854 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63855 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63856 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63862 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63879 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63881 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63882 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63895 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63905 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63908 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63915 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63930 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63931 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63933 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63934 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63954 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63959 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63960 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63967 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64010 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64033 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64055 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64056 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64083 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64084 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64085 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64086 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64087 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64088 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64089 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64090 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64091 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64093 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64094 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64095 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64096 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64097 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64135 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64138 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64164 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64165 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64166 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64168 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64188 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64218 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64219 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64221 | NONE0 | linux-libc-dev 5.15.0-181.191 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64234 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64241 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64242 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64246 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64249 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64266 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64268 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64269 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64270 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64272 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64273 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64274 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64279 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64301 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64304 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64305 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64306 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64312 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64313 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64315 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64317 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64318 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64320 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64323 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64329 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64330 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64331 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64333 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64335 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64336 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64337 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64340 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64341 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64343 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64344 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64345 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64347 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64348 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64350 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64359 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64360 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64361 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64370 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64371 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64374 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64375 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64379 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64380 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64381 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64388 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64389 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64390 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64391 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64392 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64393 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64394 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64395 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64396 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64397 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64398 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64399 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64405 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64408 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64411 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64412 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64413 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64420 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64422 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64425 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64428 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64429 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64430 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64432 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64434 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64436 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64438 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64440 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64441 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64442 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64443 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64444 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64445 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64446 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64449 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64450 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64454 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64455 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64461 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64462 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64463 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64465 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64468 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64469 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64470 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64471 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64475 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64483 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64484 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64487 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64488 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64494 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64495 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64497 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64500 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64503 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64504 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64505 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64508 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64510 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64513 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64523 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64527 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64528 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64529 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64532 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64533 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64536 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64549 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64550 | NONE0 | linux-libc-dev 5.15.0-181.191 No fix yet | 0.2% Theoretical Threat | 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-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.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.