Last scanned:
This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker could achieve remote code execution via CVE-2026-35029 or CVE-2026-42271 in LiteLLM, or bypass authentication to reach protected management routes, potentially taking over the host and accessing sensitive data. Updating LiteLLM to a patched version (>=1.83.7) fully eliminates the two cited RCE vulnerabilities, but the image still contains 276 exposed vulnerabilities, 4 with severity >=7. Note: these LiteLLM vulnerabilities require the proxy service to be running and exposed; the default /bin/bash startup does not indicate it is active, but the risk remains high for databricks runtime workloads.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-35029 | HIGH8 | litellm 1.75.9 fixed in 1.83.0 | 26.4% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42271 | HIGH8 | litellm 1.75.9 fixed in 1.83.7 | 83.0% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2026-23949 | HIGH7.31 | jaraco.context 5.3.0 fixed in 6.1.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-69243 | HIGH7 | aiohttp 3.11.10 fixed in 3.14.2 | — | Directly Exposed |
| CVE-2026-44843 | MEDIUM6.97 | langchain-core 1.2.6 fixed in 1.3.3, 0.3.85 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59822 | MEDIUM6.97 | litellm 1.75.9 fixed in 1.84.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59197 | MEDIUM6.97 | pillow 11.1.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-49468 | MEDIUM6.66 | litellm 1.75.9 fixed in 1.84.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-73417 | MEDIUM6.64 | jupyterlab 4.3.4 fixed in 4.6.2, 4.5.10 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2016-2568 | MEDIUM6.63 | libpolkit-agent-1-0 124-2ubuntu1.24.04.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-2568 | MEDIUM6.63 | libpolkit-gobject-1-0 124-2ubuntu1.24.04.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-2568 | MEDIUM6.63 | polkitd 124-2ubuntu1.24.04.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-53000 | MEDIUM6.63 | nbconvert 7.16.6 fixed in 7.17.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42311 | MEDIUM6.63 | pillow 11.1.0 fixed in 12.2.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42557 | MEDIUM6.53 | jupyterlab 4.3.4 fixed in 4.5.7 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42557 | MEDIUM6.53 | notebook 7.3.2 fixed in 7.5.6 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-48710 | MEDIUM6.5 | starlette 0.50.0 fixed in 1.0.1 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-73415 | MEDIUM6.4 | jupyterlab 4.3.4 fixed in 4.6.2, 4.5.10 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2025-1352 | MEDIUM6.38 | libdw1t64 0.190-1.1ubuntu0.1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | libelf1t64 0.190-1.1ubuntu0.1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42215 | MEDIUM6.38 | GitPython 3.1.43 fixed in 3.1.47 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-32597 | MEDIUM6.38 | PyJWT 2.10.1 fixed in 2.12.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69223 | MEDIUM6.38 | aiohttp 3.11.10 fixed in 3.13.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69227 | MEDIUM6.38 | aiohttp 3.11.10 fixed in 3.13.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69228 | MEDIUM6.38 | aiohttp 3.11.10 fixed in 3.13.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34515 | MEDIUM6.38 | aiohttp 3.11.10 fixed in 3.13.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-47265 | MEDIUM6.38 | aiohttp 3.11.10 fixed in 3.14.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54273 | MEDIUM6.38 | aiohttp 3.11.10 fixed in 3.14.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54274 | MEDIUM6.38 | aiohttp 3.11.10 fixed in 3.14.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54277 | MEDIUM6.38 | aiohttp 3.11.10 fixed in 3.14.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54278 | MEDIUM6.38 | aiohttp 3.11.10 fixed in 3.14.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-53643 | MEDIUM6.38 | aiohttp 3.11.10 fixed in 3.12.14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34513 | MEDIUM6.38 | aiohttp 3.11.10 fixed in 3.13.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-50269 | MEDIUM6.38 | aiohttp 3.11.10 fixed in 3.14.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54275 | MEDIUM6.38 | aiohttp 3.11.10 fixed in 3.14.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54279 | MEDIUM6.38 | aiohttp 3.11.10 fixed in 3.14.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54280 | MEDIUM6.38 | aiohttp 3.11.10 fixed in 3.14.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-33079 | MEDIUM6.38 | mistune 3.1.2 fixed in 3.2.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-49851 | MEDIUM6.38 | mistune 3.1.2 fixed in 3.3.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25990 | MEDIUM6.38 | pillow 11.1.0 fixed in 12.1.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40192 | MEDIUM6.38 | pillow 11.1.0 fixed in 12.2.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-54059 | MEDIUM6.38 | pillow 11.1.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54060 | MEDIUM6.38 | pillow 11.1.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-55379 | MEDIUM6.38 | pillow 11.1.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-55380 | MEDIUM6.38 | pillow 11.1.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59199 | MEDIUM6.38 | pillow 11.1.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59200 | MEDIUM6.38 | pillow 11.1.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59204 | MEDIUM6.38 | pillow 11.1.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59205 | MEDIUM6.38 | pillow 11.1.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59198 | MEDIUM6.38 | pillow 11.1.0 fixed in 12.3.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0994 | MEDIUM6.38 | protobuf 5.29.4 fixed in 6.33.5, 5.29.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-30922 | MEDIUM6.38 | pyasn1 0.4.8 fixed in 0.6.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-59885 | MEDIUM6.38 | pyasn1 0.4.8 fixed in 0.6.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59886 | MEDIUM6.38 | pyasn1 0.4.8 fixed in 0.6.4 | 0.3% 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-49477 | MEDIUM6.38 | soupsieve 2.5 fixed in 2.8.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48818 | MEDIUM6.38 | starlette 0.50.0 fixed in 1.1.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54283 | MEDIUM6.38 | starlette 0.50.0 fixed in 1.3.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31958 | MEDIUM6.38 | tornado 6.5.1 fixed in 6.5.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32874 | MEDIUM6.38 | ujson 5.10.0 fixed in 5.12.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-32875 | MEDIUM6.38 | ujson 5.10.0 fixed in 5.12.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44660 | MEDIUM6.38 | ujson 5.10.0 fixed in 5.12.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32874 | MEDIUM6.38 | ujson 5.8.0 fixed in 5.12.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-32875 | MEDIUM6.38 | ujson 5.8.0 fixed in 5.12.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44660 | MEDIUM6.38 | ujson 5.8.0 fixed in 5.12.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66418 | MEDIUM6.38 | urllib3 2.3.0 fixed in 2.6.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-66471 | MEDIUM6.38 | urllib3 2.3.0 fixed in 2.6.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-48526 | MEDIUM6.29 | PyJWT 2.10.1 fixed in 2.13.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-29481 | MEDIUM6.21 | libbpf1 1:1.3.0-2build2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44244 | MEDIUM6.21 | GitPython 3.1.43 fixed in 3.1.49 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34993 | MEDIUM6.21 | aiohttp 3.11.10 fixed in 3.14.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40110 | MEDIUM6.21 | jupyter_server 2.15.0 fixed in 2.18.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35030 | MEDIUM6.18 | litellm 1.75.9 fixed in 1.83.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59821 | MEDIUM6.12 | litellm 1.75.9 fixed in 1.82.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44243 | MEDIUM6.03 | GitPython 3.1.43 fixed in 3.1.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-28684 | MEDIUM6.03 | python-dotenv 1.2.1 fixed in 1.2.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35397 | MEDIUM5.98 | jupyter_server 2.15.0 fixed in 2.18.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-40171 | MEDIUM5.98 | jupyterlab 4.3.4 fixed in 4.5.7 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42266 | MEDIUM5.98 | jupyterlab 4.3.4 fixed in 4.5.7 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-47101 | MEDIUM5.98 | litellm 1.75.9 fixed in 1.83.14 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-47102 | MEDIUM5.98 | litellm 1.75.9 fixed in 1.83.10 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-40171 | MEDIUM5.98 | notebook 7.3.2 fixed in 7.5.6 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-5222 | MEDIUM5.95 | libicu74 74.2-1ubuntu3.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.10.3-2ubuntu0.1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-40934 | MEDIUM5.78 | jupyter_server 2.15.0 fixed in 2.18.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69224 | MEDIUM5.52 | aiohttp 3.11.10 fixed in 3.13.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-26007 | MEDIUM5.52 | cryptography 44.0.1 fixed in 46.0.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68146 | MEDIUM5.52 | filelock 3.17.0 fixed in 3.20.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59820 | MEDIUM5.52 | litellm 1.75.9 fixed in 1.83.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59922 | MEDIUM5.52 | mistune 3.1.2 fixed in 3.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59925 | MEDIUM5.52 | mistune 3.1.2 fixed in 3.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59928 | MEDIUM5.52 | mistune 3.1.2 fixed in 3.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39377 | MEDIUM5.52 | nbconvert 7.16.6 fixed in 7.17.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libbinutils 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf0 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-19617 | MEDIUM5.5 | libdevmapper1.02.1 2:1.02.185-3ubuntu3.2 No fix yet | — | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libsframe1 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.25.3-4ubuntu2.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-5569 | MEDIUM5.27 | zipp 3.17.0 fixed in 3.19.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55655 | MEDIUM5.18 | openssh-server 1:9.6p1-3ubuntu13.18 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55655 | MEDIUM5.18 | openssh-sftp-server 1:9.6p1-3ubuntu13.18 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54276 | MEDIUM5.18 | aiohttp 3.11.10 fixed in 3.14.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-61669 | MEDIUM5.18 | jupyter_server 2.15.0 fixed in 2.18.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44708 | MEDIUM5.18 | mistune 3.1.2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44896 | MEDIUM5.18 | mistune 3.1.2 fixed in 3.2.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44897 | MEDIUM5.18 | mistune 3.1.2 fixed in 3.2.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59923 | MEDIUM5.18 | mistune 3.1.2 fixed in 3.3.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59926 | MEDIUM5.18 | mistune 3.1.2 fixed in 3.3.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59929 | MEDIUM5.18 | mistune 3.1.2 fixed in 3.3.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-67724 | MEDIUM5.18 | tornado 6.5.1 fixed in 6.5.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-50181 | MEDIUM5.18 | urllib3 2.3.0 fixed in 2.5.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-50182 | MEDIUM5.18 | urllib3 2.3.0 fixed in 2.5.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48524 | MEDIUM5.02 | PyJWT 2.10.1 fixed in 2.13.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59924 | MEDIUM5.02 | mistune 3.1.2 fixed in 3.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59884 | MEDIUM5.02 | pyasn1 0.4.8 fixed in 0.6.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59884 | MEDIUM5.02 | pyasn1 0.6.3 fixed in 0.6.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49476 | MEDIUM5.02 | soupsieve 2.5 fixed in 2.8.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-39378 | MEDIUM4.84 | nbconvert 7.16.6 fixed in 7.17.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.3.dfsg-3.1ubuntu2.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-67221 | MEDIUM4.67 | orjson 3.11.5 fixed in 3.11.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42308 | MEDIUM4.67 | pillow 11.1.0 fixed in 12.2.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42310 | MEDIUM4.67 | pillow 11.1.0 fixed in 12.2.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25645 | MEDIUM4.67 | requests 2.32.3 fixed in 2.33.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48523 | MEDIUM4.59 | PyJWT 2.10.1 fixed in 2.13.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-44727 | MEDIUM4.59 | jupyter_server 2.15.0 fixed in 2.20.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48525 | MEDIUM4.5 | PyJWT 2.10.1 fixed in 2.13.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69229 | MEDIUM4.5 | aiohttp 3.11.10 fixed in 3.13.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22815 | MEDIUM4.5 | aiohttp 3.11.10 fixed in 3.13.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34516 | MEDIUM4.5 | aiohttp 3.11.10 fixed in 3.13.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34525 | MEDIUM4.5 | aiohttp 3.11.10 fixed in 3.13.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59881 | MEDIUM4.5 | aiohttp 3.11.10 fixed in 3.14.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69225 | MEDIUM4.5 | aiohttp 3.11.10 fixed in 3.13.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69226 | MEDIUM4.5 | aiohttp 3.11.10 fixed in 3.13.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69230 | MEDIUM4.5 | aiohttp 3.11.10 fixed in 3.13.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34514 | MEDIUM4.5 | aiohttp 3.11.10 fixed in 3.13.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34517 | MEDIUM4.5 | aiohttp 3.11.10 fixed in 3.13.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34518 | MEDIUM4.5 | aiohttp 3.11.10 fixed in 3.13.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34519 | MEDIUM4.5 | aiohttp 3.11.10 fixed in 3.13.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34073 | MEDIUM4.5 | cryptography 44.0.1 fixed in 46.0.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22701 | MEDIUM4.5 | filelock 3.17.0 fixed in 3.20.3 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45409 | MEDIUM4.5 | idna 3.7 fixed in 3.15 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40087 | MEDIUM4.5 | langchain-core 1.2.6 fixed in 0.3.84, 1.2.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59927 | MEDIUM4.5 | mistune 3.1.2 fixed in 3.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-4565 | MEDIUM4.5 | protobuf 5.29.4 fixed in 4.25.8, 5.29.5, 6.31.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25087 | MEDIUM4.5 | pyarrow 21.0.0 fixed in 23.0.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-47081 | MEDIUM4.5 | requests 2.32.3 fixed in 2.32.4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-48817 | MEDIUM4.5 | starlette 0.50.0 fixed in 1.1.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54282 | MEDIUM4.5 | starlette 0.50.0 fixed in 1.3.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-67725 | MEDIUM4.5 | tornado 6.5.1 fixed in 6.5.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-67726 | MEDIUM4.5 | tornado 6.5.1 fixed in 6.5.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-35536 | MEDIUM4.5 | tornado 6.5.1 fixed in 6.5.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-49854 | MEDIUM4.5 | tornado 6.5.1 fixed in 6.5.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54911 | MEDIUM4.5 | ujson 5.10.0 fixed in 5.13.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54911 | MEDIUM4.5 | ujson 5.8.0 fixed in 5.13.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44431 | MEDIUM4.5 | urllib3 2.3.0 fixed in 2.7.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59819 | MEDIUM4.17 | litellm 1.75.9 fixed in 1.83.10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-12216 | MEDIUM4.08 | libduktape207 2.7.0+tests-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.39.3-9ubuntu6.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | MEDIUM4 | libdw1t64 0.190-1.1ubuntu0.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | MEDIUM4 | libelf1t64 0.190-1.1ubuntu0.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libfdisk1 2.39.3-9ubuntu6.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.39.3-9ubuntu6.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.39.3-9ubuntu6.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.39.3-9ubuntu6.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55798 | LOW3.82 | pillow 11.1.0 fixed in 12.3.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59842 | LOW3.65 | jupyterlab 4.3.4 fixed in 4.4.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59930 | LOW3.65 | mistune 3.1.2 fixed in 3.3.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48522 | LOW3.57 | PyJWT 2.10.1 fixed in 2.13.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | LOW3.3 | binutils 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-47273 | LOW3.17 | setuptools 75.8.0 fixed in 78.1.1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-55654 | LOW3.15 | openssh-server 1:9.6p1-3ubuntu13.18 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-55654 | LOW3.15 | openssh-sftp-server 1:9.6p1-3ubuntu13.18 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34520 | LOW3.15 | aiohttp 3.11.10 fixed in 3.13.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-26013 | LOW3.15 | langchain-core 1.2.6 fixed in 1.2.11 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-55655 | LOW3.11 | openssh-client 1:9.6p1-3ubuntu13.18 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59890 | LOW3.11 | setuptools 75.8.0 fixed in 83.0.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59890 | LOW3.11 | setuptools 78.1.1 fixed in 83.0.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42284 | LOW3 | GitPython 3.1.43 fixed in 3.1.47 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-66034 | LOW3 | fonttools 4.55.3 fixed in 4.60.2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6357 | LOW2.96 | pip 25.0.1 fixed in 26.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41488 | LOW2.89 | langchain-openai 1.1.6 fixed in 1.1.14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | LOW2.8 | binutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2019-20633 | LOW2.8 | patch 2.7.6-7build3 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.7.6-7build3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-8643 | LOW2.8 | pip 25.0.1 fixed in 26.1.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-0987 | LOW2.8 | gir1.2-packagekitglib-1.0 1.2.8-2ubuntu1.5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-0217 | LOW2.8 | gir1.2-packagekitglib-1.0 1.2.8-2ubuntu1.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libnss-systemd 255.4-1ubuntu8.17 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0987 | LOW2.8 | libpackagekit-glib2-18 1.2.8-2ubuntu1.5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-0217 | LOW2.8 | libpackagekit-glib2-18 1.2.8-2ubuntu1.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libpam-systemd 255.4-1ubuntu8.17 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd-shared 255.4-1ubuntu8.17 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 255.4-1ubuntu8.17 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 255.4-1ubuntu8.17 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0987 | LOW2.8 | packagekit 1.2.8-2ubuntu1.5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-0217 | LOW2.8 | packagekit 1.2.8-2ubuntu1.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | systemd-resolved 255.4-1ubuntu8.17 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | systemd-timesyncd 255.4-1ubuntu8.17 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4539 | LOW2.8 | Pygments 2.19.1 fixed in 2.20.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54058 | LOW2.78 | pillow 11.1.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2018-6952 | LOW2.7 | patch 2.7.6-7build3 No fix yet | 8.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-69244 | LOW2.7 | aiohttp 3.11.10 fixed in 3.14.3 | — | Post-Exploit |
| CVE-2026-34070 | LOW2.7 | langchain-core 1.2.6 fixed in 1.2.22 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-21441 | LOW2.7 | urllib3 2.3.0 fixed in 2.6.3 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-8869 | LOW2.7 | pip 25.0.1 fixed in 25.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3219 | LOW2.55 | pip 25.0.1 fixed in 26.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.39.3-9ubuntu6.5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.39.3-9ubuntu6.5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.39.3-9ubuntu6.5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW2.38 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-31879 | LOW2.2 | wget 1.21.4-1ubuntu4.4 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-1703 | LOW1.99 | pip 25.0.1 fixed in 26.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-55654 | LOW1.89 | openssh-client 1:9.6p1-3ubuntu13.18 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.13+dfsg1-4ubuntu3.2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-0987 | LOW1.68 | packagekit-tools 1.2.8-2ubuntu1.5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-0217 | LOW1.68 | packagekit-tools 1.2.8-2ubuntu1.5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-68159 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68480 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-63797 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64564 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2025-38187 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38563 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71073 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31663 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53148 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53262 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64531 | NONE0 | linux-libc-dev 6.8.0-137.137 fixed in 6.8.0-138.138 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2020-14356 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50090 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50240 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0030 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27022 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38581 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40954 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-44932 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44951 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44964 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46820 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46833 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53098 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21687 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52943 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53109 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53136 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53137 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53143 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53361 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53362 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53366 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63794 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63804 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64103 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64225 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64239 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64242 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64245 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64246 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64249 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64270 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64271 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64272 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64273 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64274 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64530 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64600 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68143 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68290 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2017-13165 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2018-12930 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12931 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-33053 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-50217 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38069 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38206 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38421 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38565 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39862 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39896 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39958 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40014 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53089 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53118 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53120 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53129 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53156 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53157 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53195 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53272 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53266 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-25836 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40210 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64396 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68136 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2019-20426 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2026-32274 | NONE0 | black 24.10.0 fixed in 26.3.1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-40170 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-14899 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-64176 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68121 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68166 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68278 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68294 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68426 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2022-50551 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-14040 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-53216 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58015 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21985 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22104 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38204 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38329 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38330 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38340 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38636 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40064 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68324 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68356 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23327 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31479 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31614 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46130 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46203 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53138 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53149 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53179 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64039 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64078 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64121 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64153 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64237 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64322 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64324 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68155 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68188 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68198 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68263 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68373 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-43126 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53255 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53398 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43116 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46275 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53182 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53185 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53224 | NONE0 | linux-libc-dev 6.8.0-137.137 fixed in 6.8.0-138.138 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53239 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53250 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53254 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53256 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53264 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53270 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53275 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53399 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64383 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64385 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64386 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64387 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64597 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68117 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-54187 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50106 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37776 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39905 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40158 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40168 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40356 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43303 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46054 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52912 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52917 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52918 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52935 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52942 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52945 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52947 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52953 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52956 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52991 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53000 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53005 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53009 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53091 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53131 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53132 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53133 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53223 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53242 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53246 | NONE0 | linux-libc-dev 6.8.0-137.137 fixed in 6.8.0-138.138 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53268 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53329 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53354 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53355 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53356 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53357 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53381 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53388 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53391 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53392 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53397 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63795 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63801 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63802 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63807 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63808 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63809 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63823 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63824 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63826 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63829 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63830 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63831 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63875 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63879 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63883 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63884 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63886 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63887 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63888 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63889 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63891 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63896 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63898 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63899 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63901 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63912 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63913 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63914 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63916 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63917 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63919 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63920 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63921 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63922 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63924 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63925 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63928 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63940 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63944 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63945 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63946 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63947 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63952 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63956 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63957 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63958 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63962 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63970 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63971 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63975 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63978 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63979 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63984 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63992 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63993 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63994 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64000 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64001 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64002 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64007 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64009 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64011 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64015 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64017 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64018 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64025 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64026 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64029 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64032 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64034 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64047 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64048 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64051 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64098 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64099 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64102 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64109 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64111 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64113 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64114 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64115 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64117 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64136 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64137 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64160 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64189 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64191 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64217 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64219 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64221 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64247 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64255 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64266 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64268 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64276 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64277 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64280 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64283 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64286 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64287 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64298 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64304 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64305 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64306 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64312 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64319 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64320 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64321 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64323 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64340 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64341 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64342 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64364 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64371 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64372 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64375 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64377 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64378 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64379 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64380 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64382 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64384 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64401 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64402 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64418 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64422 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64438 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64448 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64456 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64470 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64471 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64473 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64475 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64481 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64483 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64508 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64523 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64525 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64527 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64534 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64539 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64543 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64548 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64551 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64552 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64554 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64556 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64557 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64560 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64561 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64572 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64573 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64577 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64582 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68086 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68093 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68099 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68100 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68103 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68108 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68118 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68123 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68125 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68131 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68138 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68140 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68142 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68144 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68145 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68147 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68148 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68149 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68154 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68157 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68158 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68160 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68161 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68162 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68169 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68181 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68202 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68236 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68245 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68253 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68257 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68266 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68273 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68289 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68293 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68299 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68300 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68315 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68320 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68323 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68325 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68329 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68335 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68343 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68349 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68351 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68363 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68365 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68368 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68374 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68376 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68377 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68381 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68388 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68389 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68391 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68397 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68398 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68399 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68400 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68401 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68402 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68404 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68409 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68427 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68432 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68442 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68448 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68451 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68452 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68453 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68457 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68470 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68479 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72020 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72021 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72042 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72045 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72049 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72051 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72052 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72053 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72054 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72055 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72057 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72061 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72065 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72066 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72069 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72072 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72083 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72084 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72098 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72102 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72111 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72123 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72125 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72126 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72129 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72130 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72135 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72136 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72157 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72217 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72218 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72219 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72221 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72222 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72242 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72243 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72247 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72251 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72252 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72253 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72255 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72261 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72262 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72284 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72288 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72289 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72298 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72301 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72310 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72316 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72317 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72318 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72319 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72320 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72322 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72323 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72329 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72338 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72339 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72361 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72371 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72382 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72419 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72422 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72427 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72436 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72492 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74271 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74405 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74440 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74456 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74471 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74499 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74506 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45894 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53053 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53078 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53189 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53202 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53209 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53230 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53253 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53384 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63800 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64303 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64355 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68156 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-53196 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71176 | NONE0 | pytest 8.3.5 fixed in 9.0.3 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-15794 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-64296 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68284 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2023-6238 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53267 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64535 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2015-8553 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-1193 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-40336 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68729 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-52910 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53090 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40074 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45932 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-44034 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40190 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68350 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-23240 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52908 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40203 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40340 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23239 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52923 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | binutils-common 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-19617 | NONE0 | dmsetup 2:1.02.185-3ubuntu3.2 No fix yet | — | Not Applicable |
| CVE-2025-66382 | NONE0 | libexpat1-dev 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45850 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46320 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52909 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53159 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53183 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53269 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2015-7837 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-0480 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-48846 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48929 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49940 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50230 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50232 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50332 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50380 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-0160 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52879 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53642 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54190 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-14027 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27025 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35895 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35948 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35995 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41008 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42125 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42139 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43844 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43872 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-46742 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46748 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47729 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49904 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49908 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49910 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49916 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49932 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49940 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49970 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49990 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50003 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50034 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50102 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52560 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53056 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53064 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53207 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56368 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56544 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56591 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56617 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56639 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56671 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56702 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56712 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57809 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57852 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57875 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57922 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57950 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57976 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58012 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58089 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58094 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58095 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58098 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58100 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58241 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21696 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21730 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21752 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21817 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21819 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21907 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22002 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22043 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22108 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22127 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23131 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23135 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23162 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37743 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37746 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37747 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37806 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37807 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37833 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37834 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37855 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37870 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37876 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37877 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37907 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38033 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38036 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38038 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38047 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38070 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38092 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38096 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38132 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38168 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38188 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38189 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38199 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38203 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38205 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38237 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38272 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38311 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38353 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38360 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38372 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38438 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38498 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38597 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38605 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38621 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39745 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39771 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39833 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39908 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39910 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39925 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39990 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40040 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40075 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40086 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40102 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40195 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40334 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40362 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68188 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68193 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68209 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68211 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68212 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68251 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68281 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68304 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68309 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68317 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68333 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68353 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68730 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68802 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68822 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71115 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71158 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71204 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71223 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71289 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71290 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71293 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71299 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71300 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71302 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23017 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23137 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23152 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23196 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23201 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23217 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23247 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23259 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23346 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23377 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31410 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31420 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31461 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31462 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31486 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31526 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31531 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31560 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31630 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43010 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43021 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43029 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43034 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43045 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43127 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43131 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43161 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43165 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43191 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43195 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43216 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43219 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43220 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43228 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43229 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43240 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43243 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43267 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43292 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43294 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43298 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43301 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43305 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43306 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43311 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43331 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43344 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43398 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43400 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43410 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43443 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43463 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43464 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43474 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45901 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45930 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45944 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45963 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46066 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46071 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46158 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46170 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46171 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46315 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46321 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46322 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52913 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52915 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52916 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52921 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52926 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52927 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52928 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52929 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52930 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52937 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52939 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52941 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52944 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52946 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52948 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52960 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52972 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52988 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52994 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53017 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53018 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53027 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53080 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53103 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53134 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53139 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53140 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53144 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53150 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53163 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53167 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53168 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53181 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53184 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53190 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53199 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53208 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53210 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53214 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53218 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53219 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53220 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53221 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53227 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53245 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53251 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53252 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53263 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53274 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53281 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53284 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53285 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53292 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53297 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53313 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53317 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53325 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53327 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53331 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53332 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53336 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53337 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53339 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53343 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53345 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53347 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53349 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53350 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53353 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53358 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53365 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53377 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53382 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53385 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53393 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53400 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53402 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53403 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63798 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63803 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63810 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63821 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63822 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63832 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63853 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63858 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63867 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63868 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63869 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63870 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63871 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63876 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63877 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63881 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63882 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63890 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63892 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63893 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63897 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63900 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63902 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63903 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63904 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63906 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63926 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63927 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63942 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63943 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63948 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63961 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63963 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63964 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63968 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63969 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63973 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63974 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63976 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63980 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63983 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63985 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63990 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63991 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63999 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64003 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64004 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64005 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64006 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64012 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64014 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64036 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64038 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64046 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64052 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64060 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64064 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64070 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64073 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64076 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64077 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64079 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64090 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64092 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64094 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64097 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64106 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64112 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64116 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64118 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64123 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64125 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64126 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64127 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64128 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64131 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64133 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64134 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64135 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64144 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64146 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64147 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64154 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64155 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64163 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64165 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64166 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64168 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64170 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64173 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64174 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64177 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64178 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64179 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64180 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64182 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64183 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64184 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64185 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64187 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64190 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64192 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64205 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64206 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64210 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64212 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64213 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64214 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64220 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64222 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64227 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64231 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64233 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64234 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64240 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64241 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64243 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64244 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64254 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64256 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64275 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64279 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64289 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64294 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64297 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64299 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64301 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64313 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64315 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64316 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64326 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64329 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64330 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64332 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64333 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64334 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64335 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64336 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64338 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64343 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64344 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64346 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64347 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64351 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64352 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64360 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64362 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64363 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64365 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64368 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64369 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64370 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64373 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64374 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64376 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64381 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64388 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64403 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64404 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64405 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64406 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64407 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64408 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64409 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64411 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64412 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64413 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64417 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64419 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64423 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64424 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64428 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64430 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64433 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64435 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64436 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64450 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64452 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64454 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64455 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64458 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64463 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64465 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64472 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64474 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64476 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64478 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64479 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64480 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64482 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64486 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64487 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64488 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64489 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64496 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64507 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64510 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64511 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64512 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64513 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64514 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64524 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64529 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64537 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64540 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64541 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64542 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64544 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64545 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64546 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64547 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64549 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64553 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64555 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64567 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64569 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64570 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64574 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64576 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64579 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68085 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68090 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68091 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68096 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68098 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68102 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68104 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68105 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68106 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68107 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68109 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68110 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68111 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68112 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68113 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68114 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68115 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68116 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68119 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68126 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68127 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68129 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68130 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68132 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68135 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68137 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68139 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68141 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68146 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68152 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68153 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68164 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68165 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68175 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68176 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68178 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68180 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68182 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68183 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68184 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68186 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68187 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68189 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68190 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68193 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68194 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68195 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68196 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68197 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68204 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68205 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68206 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68207 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68209 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68210 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68211 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68212 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68214 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68215 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68216 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68217 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68218 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68219 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68222 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68226 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68227 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68228 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68229 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68231 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68233 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68234 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68235 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68238 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68241 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68242 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68243 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68244 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68246 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68247 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68248 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68249 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68250 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68251 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68252 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68254 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68255 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68256 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68258 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68259 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68260 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68261 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68262 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68269 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68271 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68272 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68277 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68279 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68281 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68286 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68287 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68288 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68291 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68297 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68301 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68304 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68306 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68308 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68309 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68310 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68312 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68313 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68317 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68318 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68319 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68322 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68324 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68326 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68328 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68331 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68333 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68336 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68338 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68339 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68346 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68348 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68352 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68353 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68354 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68355 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68357 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68360 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68362 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68364 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68366 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68367 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68369 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68371 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68372 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68382 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68383 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68386 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68392 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68395 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68396 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68403 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68405 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68406 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68407 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68408 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68410 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68411 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68412 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68413 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68414 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68416 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68417 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68418 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68419 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68422 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68425 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68428 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68429 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68430 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68431 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68433 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68436 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68437 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68439 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68441 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68443 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68444 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68445 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68446 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68447 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68449 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68450 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68454 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68456 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68459 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68460 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68461 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68466 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68467 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68469 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68471 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68474 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68475 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68477 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68478 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72004 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72005 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72007 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72009 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72010 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72012 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72013 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72014 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72015 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72017 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72019 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72022 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72023 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72024 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72025 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72028 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72029 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72030 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72031 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72033 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72035 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72036 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72037 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72038 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72039 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72040 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72041 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72047 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72048 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72056 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72058 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72059 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72062 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72063 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72067 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72068 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72070 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72071 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72073 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72074 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72075 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72076 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72077 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72078 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72079 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72081 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72082 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72085 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72086 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72087 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72088 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72089 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72096 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72097 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72105 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72106 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72107 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72108 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72109 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72110 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72113 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72114 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72115 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72116 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72117 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72118 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72119 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72120 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72121 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72122 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72124 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72127 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72132 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72133 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72138 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72142 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72144 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72146 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72147 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72148 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72149 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72150 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72152 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72153 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72155 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72156 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72158 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72159 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72160 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72161 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72162 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72163 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72164 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72165 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72166 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72167 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72168 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72170 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72171 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72172 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72174 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72175 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72176 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72177 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72179 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72181 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72182 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72191 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72192 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72193 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72194 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72195 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72196 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72197 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72198 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72199 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72200 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72201 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72202 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72203 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72204 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72205 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72206 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72207 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72208 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72210 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72211 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72212 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72213 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72214 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72215 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72216 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72223 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72224 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72225 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72226 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72227 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72228 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72229 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72230 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72231 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72232 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72233 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72234 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72235 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72236 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72237 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72238 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72240 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72241 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72244 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72245 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72250 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72254 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72256 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72257 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72258 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72259 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72260 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72264 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72265 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72266 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72267 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72268 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72269 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72270 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72271 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72272 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72273 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72274 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72275 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72276 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72282 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72290 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72296 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72297 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72299 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72300 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72302 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72304 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72305 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72307 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72308 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72312 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72314 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72315 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72321 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72324 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72325 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72326 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72327 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72330 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72334 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72335 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72336 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72337 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72352 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72373 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72374 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72375 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72376 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72379 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72380 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72395 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72396 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72397 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72400 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72402 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72418 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72420 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72423 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72424 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72428 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72430 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72433 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72438 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72439 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72440 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72441 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72454 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72459 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72460 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72470 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72472 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72481 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72483 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72486 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74261 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74276 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74293 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74314 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74318 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74320 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74321 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74330 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74334 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74356 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74362 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74373 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74375 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74380 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74382 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74399 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74406 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74426 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74427 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74445 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74448 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74464 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74470 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74475 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74494 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74500 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74508 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74519 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74538 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74549 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74555 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74565 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74578 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74579 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12929 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21693 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22077 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43485 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45897 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46252 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53070 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53102 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53104 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53106 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53113 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53135 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53142 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53146 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53147 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53154 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53158 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53177 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53205 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53207 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53213 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53226 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53229 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53232 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53236 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53237 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53238 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53249 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53258 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53261 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53265 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27171 | NONE0 | zlib1g-dev 1:1.3.dfsg-3.1ubuntu2.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-24049 | NONE0 | wheel 0.43.0 fixed in 0.46.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-24049 | NONE0 | wheel 0.45.1 fixed in 0.46.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53194 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64538 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-20585 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40217 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40344 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57857 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39293 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-42107 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56552 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-56788 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21984 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37906 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38242 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38440 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38717 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39754 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39884 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40139 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68296 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23181 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23469 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45949 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53108 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53352 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2017-0537 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-46272 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4010 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-68360 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-22702 | NONE0 | virtualenv 20.29.3 fixed in 20.36.1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68768 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68337 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64317 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login 1:4.13+dfsg1-4ubuntu3.2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | systemd 255.4-1ubuntu8.17 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | systemd-dev 255.4-1ubuntu8.17 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | systemd-sysv 255.4-1ubuntu8.17 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53186 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53198 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64091 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-54105 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40012 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40073 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40098 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40208 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40274 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40332 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40335 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68196 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68230 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68338 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68781 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52919 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52922 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52934 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53383 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53386 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53387 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53389 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53390 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63793 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63796 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63806 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63811 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63812 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63814 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63815 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63816 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63817 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63818 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63827 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63828 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63833 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63834 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63835 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63836 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63895 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63905 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63908 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63909 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63915 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63930 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63931 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63933 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63934 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63949 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63954 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63959 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63960 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63967 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64010 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64022 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64023 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64033 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64055 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64056 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64082 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64083 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64084 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64085 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64086 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64087 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64088 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64089 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64093 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64095 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64096 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64108 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64138 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64148 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64188 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64218 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64269 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64318 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64331 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64337 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64345 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64348 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64350 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64358 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64359 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64361 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64389 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64390 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64391 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64392 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64393 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64394 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64395 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64397 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64398 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64399 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64420 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64421 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64425 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64429 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64432 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64440 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64441 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64442 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64443 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64444 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64445 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64446 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64449 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64461 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64462 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64468 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64469 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64484 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64493 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64494 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64495 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64497 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64500 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64503 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64504 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64505 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64518 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64528 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64532 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64533 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64536 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64550 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64562 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64563 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64565 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64568 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64571 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64578 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64580 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64581 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64583 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64584 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64585 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64586 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64590 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64593 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64594 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64598 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64599 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64602 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64603 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-64604 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68081 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68082 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68083 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68084 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68088 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68097 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68124 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68151 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68179 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68192 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68199 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68203 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68213 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68220 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68221 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68223 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68225 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68280 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68302 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68303 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68314 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68327 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68340 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68359 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68361 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68370 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-68476 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72099 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72140 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72306 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72340 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72341 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72342 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72343 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72347 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72348 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72349 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72350 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72351 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72362 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72369 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72378 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72383 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72384 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72389 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72390 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72391 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72392 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72398 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72399 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72404 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72405 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72406 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72409 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72410 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72413 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72414 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72416 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72421 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72425 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72434 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72435 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72437 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72443 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72444 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72447 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72448 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72449 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72450 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72451 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72464 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72466 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72467 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72469 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72473 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72474 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72476 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72478 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72479 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72480 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72484 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72485 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72487 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72488 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72489 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72491 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72493 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72494 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72495 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72496 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72499 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72501 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-72502 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74255 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74256 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74257 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74258 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74259 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74262 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74263 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74264 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74265 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74267 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74268 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74269 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74270 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74272 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74273 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74278 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74279 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74280 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74281 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74282 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74283 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74284 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74287 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74288 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74289 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74290 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74291 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74292 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74294 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74295 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74296 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74297 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74300 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74302 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74303 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74305 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74307 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74308 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74310 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74312 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74313 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74317 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74324 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74327 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74329 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74331 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74337 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74338 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74339 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74340 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74341 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74342 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74344 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74345 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74346 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74347 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74348 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74349 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74350 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74351 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74359 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74363 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74365 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74368 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74374 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74376 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74377 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74378 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74379 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74381 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74384 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74385 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74386 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74387 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74388 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74389 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74390 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74391 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74394 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74395 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74397 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74398 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74401 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74402 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74407 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74408 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74410 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74411 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74416 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74417 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74424 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74432 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74436 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74438 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74439 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74441 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74443 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74444 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74446 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74449 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74450 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74453 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74454 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74455 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74457 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74458 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74459 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74460 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74461 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74463 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74465 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74466 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74467 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74468 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74469 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74472 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74473 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74474 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74476 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74478 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74479 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74480 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74481 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74482 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74483 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74484 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74485 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74487 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74488 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74490 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74492 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74493 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74495 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74496 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74497 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74498 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74501 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74502 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74505 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74507 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74509 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74510 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74512 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74514 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74515 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74516 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74518 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74521 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74522 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74523 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74525 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74527 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74530 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74531 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74532 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74533 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74534 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74535 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74536 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74537 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74540 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74541 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74543 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74544 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74546 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74547 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74548 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74550 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74551 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74552 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74553 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74556 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74557 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74558 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74559 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74560 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74563 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74564 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74566 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74567 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74569 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74571 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74572 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74574 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74575 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-74577 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | — | Not Applicable |
| CVE-2026-53160 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53161 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53216 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53217 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53247 | NONE0 | linux-libc-dev 6.8.0-137.137 fixed in 6.8.0-138.138 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53273 | NONE0 | linux-libc-dev 6.8.0-137.137 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| GHSA-2f96-g7mh-g2hx | NONE0 | GitPython 3.1.43 fixed in 3.1.51 | — | Not Applicable |
| GHSA-3f7w-8rr8-f37f | NONE0 | GitPython 3.1.43 fixed in 3.1.57 | — | Not Applicable |
| GHSA-3rp5-jjmw-4wv2 | NONE0 | GitPython 3.1.43 fixed in 3.1.53 | — | Not Applicable |
| GHSA-4gmw-gg2m-w46p | NONE0 | GitPython 3.1.43 fixed in 3.1.58 | — | Not Applicable |
| GHSA-6p8h-3wgx-97gf | NONE0 | GitPython 3.1.43 fixed in 3.1.54 | — | Not Applicable |
| GHSA-94p4-4cq8-9g67 | NONE0 | GitPython 3.1.43 fixed in 3.1.55 | — | Not Applicable |
| GHSA-956x-8gvw-wg5v | NONE0 | GitPython 3.1.43 fixed in 3.1.51 | — | Not Applicable |
| GHSA-9rj7-rf2p-w77r | NONE0 | GitPython 3.1.43 fixed in 3.1.58 | — | Not Applicable |
| GHSA-fjr4-x663-mwxc | NONE0 | GitPython 3.1.43 fixed in 3.1.54 | — | Not Applicable |
| GHSA-hmq2-w58f-27jc | NONE0 | GitPython 3.1.43 fixed in 3.1.58 | — | Not Applicable |
| GHSA-jm78-9fvv-mhgr | NONE0 | GitPython 3.1.43 fixed in 3.1.58 | — | Not Applicable |
| GHSA-mv93-w799-cj2w | NONE0 | GitPython 3.1.43 fixed in 3.1.50 | — | Not Applicable |
| GHSA-r9mr-m37c-5fr3 | NONE0 | GitPython 3.1.43 fixed in 3.1.54 | — | Not Applicable |
| GHSA-rwj8-pgh3-r573 | NONE0 | GitPython 3.1.43 fixed in 3.1.52 | — | Not Applicable |
| GHSA-wvpp-8hx9-p66j | NONE0 | GitPython 3.1.43 fixed in 3.1.58 | — | Not Applicable |
| GHSA-539m-9xh6-q6rr | NONE0 | GitPython 3.1.43 fixed in 3.1.57 | — | Not Applicable |
| GHSA-hh9p-6wh2-4mfc | NONE0 | GitPython 3.1.43 fixed in 3.1.58 | — | Not Applicable |
| GHSA-p538-c434-8v24 | NONE0 | GitPython 3.1.43 fixed in 3.1.56 | — | Not Applicable |
| CVE-2026-21226 | NONE0 | azure-core 1.37.0 fixed in 1.38.0 | 0.8% Theoretical Threat | Not Applicable |
| GHSA-gj48-438w-jh9v | NONE0 | bleach 6.2.0 fixed in 6.4.0 | — | Not Applicable |
| GHSA-8rfp-98v4-mmr6 | NONE0 | bleach 6.2.0 fixed in 6.4.0 | — | Not Applicable |
| CVE-2026-69247 | NONE0 | cryptography 44.0.1 fixed in 50.0.0 | — | Not Applicable |
| CVE-2026-69249 | NONE0 | cryptography 44.0.1 fixed in 49.0.0 | — | Not Applicable |
| GHSA-537c-gmf6-5ccf | NONE0 | cryptography 44.0.1 fixed in 48.0.1 | — | Not Applicable |
| CVE-2026-69248 | NONE0 | cryptography 44.0.1 fixed in 49.0.0 | — | Not Applicable |
| CVE-2026-69247 | NONE0 | cryptography 48.0.1 fixed in 50.0.0 | — | Not Applicable |
| CVE-2026-69249 | NONE0 | cryptography 48.0.1 fixed in 49.0.0 | — | Not Applicable |
| CVE-2026-69248 | NONE0 | cryptography 48.0.1 fixed in 49.0.0 | — | Not Applicable |
| CVE-2025-30167 | NONE0 | jupyter_core 5.7.2 fixed in 5.8.1 | 0.2% Theoretical Threat | Not Applicable |
| GHSA-h5v5-8746-g7mm | NONE0 | jupyterlab 4.3.4 fixed in 4.6.2, 4.5.10 | — | Not Applicable |
| GHSA-vmhf-c436-hxj4 | NONE0 | jupyterlab 4.3.4 fixed in 4.5.9 | — | Not Applicable |
| GHSA-whvh-wf3x-g77j | NONE0 | jupyterlab 4.3.4 fixed in 4.6.2, 4.5.10 | — | Not Applicable |
| CVE-2026-45134 | NONE0 | langsmith 0.6.1 fixed in 0.8.0 | 0.2% Theoretical Threat | Not Applicable |
| GHSA-f4xh-w4cj-qxq8 | NONE0 | langsmith 0.6.1 fixed in 0.8.18 | — | Not Applicable |
| CVE-2026-25528 | NONE0 | langsmith 0.6.1 fixed in 0.6.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-41182 | NONE0 | langsmith 0.6.1 fixed in 0.7.31 | 0.2% Theoretical Threat | Not Applicable |
| GHSA-69x8-hrgq-fjj8 | NONE0 | litellm 1.75.9 fixed in 1.83.0 | — | Not Applicable |
| CVE-2026-54284 | NONE0 | sqlparse 0.5.5 fixed in 0.6.0 | — | Not Applicable |
| CVE-2026-59893 | NONE0 | sqlparse 0.5.5 fixed in 0.6.0 | — | Not Applicable |
| CVE-2026-71491 | NONE0 | sqlparse 0.5.5 fixed in 0.6.0 | — | Not Applicable |
| CVE-2026-59894 | NONE0 | sqlparse 0.5.5 fixed in 0.6.0 | — | Not Applicable |
| CVE-2026-49853 | NONE0 | tornado 6.5.1 fixed in 6.5.6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-49855 | NONE0 | tornado 6.5.1 fixed in 6.5.6 | 0.6% Theoretical Threat | Not Applicable |
| GHSA-78cv-mqj4-43f7 | NONE0 | tornado 6.5.1 fixed in 6.5.5 | — | Not Applicable |
| GHSA-pw6j-qg29-8w7f | NONE0 | tornado 6.5.1 fixed in 6.5.7 | — | 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.