This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker with local access to the container could exploit kernel use-after-free vulnerabilities (e.g., CVE-2026-46274, CVE-2026-31532) to escalate privileges to the host or cause service disruption. While no post-exploitation vulnerabilities were found, the large number of medium-severity surface vulnerabilities (59) warrants caution and prompt patching of the host kernel.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-46274 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31532 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31576 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31578 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31580 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31581 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31582 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31583 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31686 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31696 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31702 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31709 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31715 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45989 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45995 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45996 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46001 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46004 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46045 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46047 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46162 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46163 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46180 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46183 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46189 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46213 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46219 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46234 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46241 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46243 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46331 | MEDIUM6.63 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-1193 | MEDIUM6.5 | linux-libc-dev 7.0.0-22.22 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-41989 | MEDIUM6.38 | libgcrypt20 1.12.0-2 fixed in 1.12.0-2ubuntu0.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43501 | MEDIUM6.38 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46195 | MEDIUM6.38 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-25836 | MEDIUM6.38 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0846 | MEDIUM6.38 | python3-nltk 3.9.2-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0847 | MEDIUM6.38 | python3-nltk 3.9.2-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-33231 | MEDIUM6.38 | python3-nltk 3.9.2-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | golang.org/x/net v0.40.0 fixed in 0.53.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-14899 | MEDIUM6.29 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-31607 | MEDIUM6.21 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46244 | MEDIUM6.21 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46135 | MEDIUM6.03 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-50551 | MEDIUM6.03 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31613 | MEDIUM6.03 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31614 | MEDIUM6.03 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45994 | MEDIUM6.03 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46020 | MEDIUM6.03 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46022 | MEDIUM6.03 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46033 | MEDIUM6.03 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46053 | MEDIUM6.03 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46056 | MEDIUM6.03 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46120 | MEDIUM6.03 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46150 | MEDIUM6.03 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46155 | MEDIUM6.03 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46191 | MEDIUM6.03 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46203 | MEDIUM6.03 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46209 | MEDIUM6.03 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46043 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43493 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46039 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46119 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46185 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46275 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46319 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-3864 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-1247 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-2961 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31586 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31694 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31703 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43491 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45840 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46015 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46052 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46054 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46069 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46076 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46084 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46090 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46099 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46114 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46116 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46117 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46121 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46123 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46132 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46133 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46139 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46145 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46149 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46152 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46166 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46173 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46174 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46176 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46181 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46215 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46227 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46242 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46306 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46309 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46316 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46317 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46324 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-45885 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46281 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46294 | MEDIUM5.95 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.12.0-2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3714 | MEDIUM5.9 | linux-libc-dev 7.0.0-22.22 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-1121 | MEDIUM5.9 | linux-libc-dev 7.0.0-22.22 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-46125 | MEDIUM5.78 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45837 | MEDIUM5.7 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-6238 | MEDIUM5.7 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31589 | MEDIUM5.61 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45991 | MEDIUM5.61 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-bin 2.43-2ubuntu2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.43-2ubuntu2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-dev-bin 2.43-2ubuntu2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.43-2ubuntu2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-gconv-modules-extra 2.43-2ubuntu2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-gconv-modules-extra 2.43-2ubuntu2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6 2.43-2ubuntu2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.43-2ubuntu2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6-dev 2.43-2ubuntu2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.43-2ubuntu2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2015-8553 | MEDIUM5.52 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31588 | MEDIUM5.52 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-0564 | MEDIUM5.52 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libbinutils 2.46-3ubuntu2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf-nobfd0 2.46-3ubuntu2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf0 2.46-3ubuntu2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libgprofng0 2.46-3ubuntu2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libsframe3 2.46-3ubuntu2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-44034 | MEDIUM5.44 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-40190 | MEDIUM5.18 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31700 | MEDIUM5.18 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31708 | MEDIUM5.18 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-33230 | MEDIUM5.18 | python3-nltk 3.9.2-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.43-2ubuntu2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-dev-bin 2.43-2ubuntu2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-gconv-modules-extra 2.43-2ubuntu2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.43-2ubuntu2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.43-2ubuntu2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46065 | MEDIUM4.93 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46113 | MEDIUM4.93 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46024 | MEDIUM4.84 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-0537 | MEDIUM4.7 | linux-libc-dev 7.0.0-22.22 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.7.4-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1-dev 2.7.4-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45988 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46273 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46304 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46320 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2015-7837 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-8660 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-0480 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-4543 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-48846 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48929 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49940 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50230 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50232 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50332 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50380 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-0160 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31082 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52879 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53642 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54190 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35895 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35995 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21988 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22077 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31574 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31575 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31577 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31579 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31585 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31590 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31591 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31592 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31593 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31594 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31595 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31596 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31599 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31600 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31601 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31603 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31604 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31605 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31606 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31610 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31615 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31616 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31617 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31618 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31619 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31621 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31623 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31624 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31625 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31628 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31698 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31699 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31701 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31704 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31710 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31713 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31714 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31719 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43058 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43072 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43073 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43348 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43349 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43350 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43492 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43496 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43502 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45834 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45835 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45836 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45838 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45841 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45842 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45843 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45844 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45845 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45846 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45986 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45987 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45990 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45997 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45999 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46002 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46003 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46005 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46007 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46009 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46010 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46012 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46013 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46014 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46016 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46018 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46019 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46021 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46023 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46026 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46027 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46028 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46030 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46032 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46034 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46035 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46037 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46038 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46040 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46041 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46042 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46044 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46046 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46049 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46050 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46051 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46059 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46060 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46061 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46063 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46064 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46066 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46068 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46070 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46071 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46078 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46079 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46082 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46083 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46086 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46088 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46089 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46092 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46093 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46094 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46095 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46101 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46102 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46103 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46104 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46105 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46106 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46107 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46111 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46115 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46126 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46127 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46130 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46131 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46136 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46137 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46138 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46140 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46144 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46146 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46148 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46151 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46153 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46156 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46157 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46158 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46160 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46161 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46165 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46167 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46168 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46169 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46170 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46171 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46172 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46178 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46179 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46182 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46184 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46186 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46188 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46190 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46192 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46193 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46196 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46200 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46201 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46202 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46207 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46211 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46214 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46216 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46220 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46221 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46222 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46223 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46224 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46225 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46226 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46228 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46229 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46231 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46233 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46235 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46236 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46239 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46289 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46302 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46315 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46321 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46322 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13693 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12928 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12929 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31609 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43071 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46147 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46279 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46280 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46283 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46284 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46291 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46292 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46295 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46298 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46299 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46307 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46312 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46313 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46318 | MEDIUM4.67 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.41.3-3ubuntu2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-bin 2.43-2ubuntu2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-dev-bin 2.43-2ubuntu2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-gconv-modules-extra 2.43-2ubuntu2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.43-2ubuntu2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6-dev 2.43-2ubuntu2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.41.3-3ubuntu2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.41.3-3ubuntu2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.41.3-3ubuntu2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-47911 | MEDIUM4.5 | golang.org/x/net v0.40.0 fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58190 | MEDIUM4.5 | golang.org/x/net v0.40.0 fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.41.3-3ubuntu2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.41.3-3ubuntu2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.41.3-3ubuntu2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.41.3-3ubuntu2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31697 | MEDIUM4 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46008 | MEDIUM4 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46025 | MEDIUM4 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46159 | MEDIUM4 | linux-libc-dev 7.0.0-22.22 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46187 | MEDIUM4 | linux-libc-dev 7.0.0-22.22 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46194 | MEDIUM4 | linux-libc-dev 7.0.0-22.22 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31620 | LOW3.91 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-15213 | LOW3.91 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4010 | LOW3.91 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2018-17977 | LOW3.74 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-14304 | LOW3.74 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-52005 | LOW3.59 | git 1:2.53.0-1ubuntu1 No fix yet | 0.5% Theoretical Threat | Post-ExploitContext importance: MEDIUM |
| CVE-2022-41848 | LOW3.57 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc-bin 2.43-2ubuntu2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc-dev-bin 2.43-2ubuntu2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc-gconv-modules-extra 2.43-2ubuntu2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6 2.43-2ubuntu2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6-dev 2.43-2ubuntu2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | LOW3.3 | binutils 2.46-3ubuntu2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-common 2.46-3ubuntu2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-x86-64-linux-gnu 2.46-3ubuntu2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.9-2build3 fixed in 4.9-2ubuntu1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0848 | LOW3.06 | python3-nltk 3.9.2-1 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2020-35501 | LOW2.89 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-45582 | LOW2.86 | tar 1.35+dfsg-4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2013-7445 | LOW2.81 | linux-libc-dev 7.0.0-22.22 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19378 | LOW2.81 | linux-libc-dev 7.0.0-22.22 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19814 | LOW2.81 | linux-libc-dev 7.0.0-22.22 No fix yet | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.8-2build1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-35373 | LOW2.8 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41990 | LOW2.8 | libgcrypt20 1.12.0-2 fixed in 1.12.0-2ubuntu0.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 259.5-0ubuntu3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 259.5-0ubuntu3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46057 | LOW2.8 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0400 | LOW2.7 | linux-libc-dev 7.0.0-22.22 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-20426 | LOW2.7 | linux-libc-dev 7.0.0-22.22 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | LOW2.7 | patch 2.8-2build1 No fix yet | 8.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.41.3-3ubuntu2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | login 1:4.16.0-2+really2.41.3-3ubuntu2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.41.3-3ubuntu2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.41.3-3ubuntu2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14009 | LOW2.69 | python3-nltk 3.9.2-1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-39821 | LOW2.51 | golang.org/x/net v0.40.0 fixed in 0.55.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-33236 | LOW2.48 | python3-nltk 3.9.2-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-15794 | LOW2.41 | linux-libc-dev 7.0.0-22.22 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.41.3-3ubuntu2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | login 1:4.16.0-2+really2.41.3-3ubuntu2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.41.3-3ubuntu2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.41.3-3ubuntu2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-3238 | LOW2.39 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50090 | LOW2.39 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50240 | LOW2.39 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-0030 | LOW2.39 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-26242 | LOW2.39 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2017-13165 | LOW2.39 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-12930 | LOW2.39 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2018-12931 | LOW2.39 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-26934 | LOW2.39 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-33053 | LOW2.39 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66418 | LOW2.29 | python3-pip 25.1.1+dfsg-1ubuntu2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-66471 | LOW2.29 | python3-pip 25.1.1+dfsg-1ubuntu2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-21441 | LOW2.29 | python3-pip 25.1.1+dfsg-1ubuntu2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-66418 | LOW2.29 | python3-pip-whl 25.1.1+dfsg-1ubuntu2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-66471 | LOW2.29 | python3-pip-whl 25.1.1+dfsg-1ubuntu2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-21441 | LOW2.29 | python3-pip-whl 25.1.1+dfsg-1ubuntu2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-1703 | LOW1.99 | python3-pip 25.1.1+dfsg-1ubuntu2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-1703 | LOW1.99 | python3-pip-whl 25.1.1+dfsg-1ubuntu2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.17.4-2ubuntu3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-52005 | NONE0 | git-man 1:2.53.0-1ubuntu1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-33811 | NONE0 | stdlib v1.26.2 fixed in 1.25.10, 1.26.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | stdlib v1.26.2 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-39820 | NONE0 | stdlib v1.26.2 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-39836 | NONE0 | stdlib v1.26.2 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-39826 | NONE0 | stdlib v1.26.2 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42507 | NONE0 | stdlib v1.26.2 fixed in 1.25.11, 1.26.4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login.defs 1:4.17.4-2ubuntu3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31608 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-54518 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31705 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31718 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46277 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46311 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54105 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54187 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-54505 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31584 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31587 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31597 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31598 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31602 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31611 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31612 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31622 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31626 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31627 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31629 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31711 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31712 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31716 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31717 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43495 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43497 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43498 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43499 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45839 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46006 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46011 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46029 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46031 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46036 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46055 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46058 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46062 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46067 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46072 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46073 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46074 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46075 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46077 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46080 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46081 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46085 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46087 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46091 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46096 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46097 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46098 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46100 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46108 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46109 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46110 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46112 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46118 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46122 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46124 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46128 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46129 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46134 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46141 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46142 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46143 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46154 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46164 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46177 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46210 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46232 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46240 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46290 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46303 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46305 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46332 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52904 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52905 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52906 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52907 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46276 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46278 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46282 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46285 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46286 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46287 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46288 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46293 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46296 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46297 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46301 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46308 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46310 | NONE0 | linux-libc-dev 7.0.0-22.22 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-35341 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-35344 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35345 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35348 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35350 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35351 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35352 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35354 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35357 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35359 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35360 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35363 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-35364 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35367 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35368 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35370 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35371 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35374 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35377 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-25680 | NONE0 | golang.org/x/net v0.40.0 fixed in 0.55.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25681 | NONE0 | golang.org/x/net v0.40.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27136 | NONE0 | golang.org/x/net v0.40.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42502 | NONE0 | golang.org/x/net v0.40.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42506 | NONE0 | golang.org/x/net v0.40.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39824 | NONE0 | golang.org/x/sys v0.33.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-39823 | NONE0 | stdlib v1.26.2 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39825 | NONE0 | stdlib v1.26.2 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42499 | NONE0 | stdlib v1.26.2 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.26.2 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.26.2 fixed in 1.25.11, 1.26.4 | 0.3% Theoretical Threat | Not Applicable |