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 exploit CVE-2023-4863 (libwebp heap overflow) or CVE-2024-2961 (glibc iconv out-of-bounds write) to execute arbitrary code inside the container, and the outdated axios client (CVE-2025-62718) lets requests be forced to internal loopback services. The bundled Backstage scaffolder plugin offers an additional code-execution path through a tampered template. Note that CVE-2023-35926 is only exploitable by an actor who can write to a registered scaffolder template. Rebuild on a patched, supported base and current Backstage and Node dependencies before any deployment.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2024-2961 | CRITICAL10 | libc-bin 2.28-10 fixed in 2.28-10+deb10u3 | 88.3% Actively Exploited | Directly Exposed |
| CVE-2024-2961 | CRITICAL10 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u3 | 88.3% Actively Exploited | Directly Exposed |
| CVE-2024-2961 | CRITICAL10 | libc6 2.28-10 fixed in 2.28-10+deb10u3 | 88.3% Actively Exploited | Directly Exposed |
| CVE-2024-2961 | CRITICAL10 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u3 | 88.3% Actively Exploited | Directly Exposed |
| CVE-2023-4863 | CRITICAL10 | libwebpdemux2 0.6.1-2+deb10u1 fixed in 0.6.1-2+deb10u3 | 100.0% Actively Exploited | Directly Exposed |
| CVE-2023-4863 | CRITICAL10 | libwebpmux3 0.6.1-2+deb10u1 fixed in 0.6.1-2+deb10u3 | 100.0% Actively Exploited | Directly Exposed |
| CVE-2023-35926 | CRITICAL9.9 | @backstage/plugin-scaffolder-backend 0.14.2 fixed in 1.15.0 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-62718 | CRITICAL9.9 | axios 0.21.1 fixed in 1.15.0, 0.31.0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33574 | CRITICAL9.8 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23218 | CRITICAL9.8 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23219 | CRITICAL9.8 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33574 | CRITICAL9.8 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23218 | CRITICAL9.8 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23219 | CRITICAL9.8 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33574 | CRITICAL9.8 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23218 | CRITICAL9.8 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23219 | CRITICAL9.8 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33574 | CRITICAL9.8 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23218 | CRITICAL9.8 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23219 | CRITICAL9.8 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1664 | CRITICAL9.8 | libdpkg-perl 1.19.7 fixed in 1.19.8 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-22822 | CRITICAL9.8 | libexpat1 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u2 | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-22823 | CRITICAL9.8 | libexpat1 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u2 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-22824 | CRITICAL9.8 | libexpat1 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u2 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23852 | CRITICAL9.8 | libexpat1 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u2 | 4.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25235 | CRITICAL9.8 | libexpat1 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u3 | 5.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25315 | CRITICAL9.8 | libexpat1 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u3 | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-22822 | CRITICAL9.8 | libexpat1-dev 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u2 | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-22823 | CRITICAL9.8 | libexpat1-dev 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u2 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-22824 | CRITICAL9.8 | libexpat1-dev 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u2 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23852 | CRITICAL9.8 | libexpat1-dev 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u2 | 4.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25235 | CRITICAL9.8 | libexpat1-dev 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u3 | 5.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25315 | CRITICAL9.8 | libexpat1-dev 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u3 | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27404 | CRITICAL9.8 | libfreetype6 2.9.1-3+deb10u2 fixed in 2.9.1-3+deb10u3 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3515 | CRITICAL9.8 | libksba8 1.3.5-2 fixed in 1.3.5-2+deb10u1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-47629 | CRITICAL9.8 | libksba8 1.3.5-2 fixed in 1.3.5-2+deb10u2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48565 | CRITICAL9.8 | libpython2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48565 | CRITICAL9.8 | libpython2.7-stdlib 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-37454 | CRITICAL9.8 | libpython3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u4 | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48565 | CRITICAL9.8 | libpython3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u6 | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-37454 | CRITICAL9.8 | libpython3.7-stdlib 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u4 | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48565 | CRITICAL9.8 | libpython3.7-stdlib 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u6 | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-35527 | CRITICAL9.8 | libsqlite3-0 3.27.2-3+deb10u1 fixed in 3.27.2-3+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-37454 | CRITICAL9.8 | python3.7 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u4 | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48565 | CRITICAL9.8 | python3.7 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u6 | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-37454 | CRITICAL9.8 | python3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u4 | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48565 | CRITICAL9.8 | python3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u6 | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45853 | CRITICAL9.8 | zlib1g 1:1.2.11.dfsg-1 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-4279 | CRITICAL9.8 | fast-json-patch 2.2.1 fixed in 3.1.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16042 | CRITICAL9.8 | growl 1.9.2 fixed in 1.10.0 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33937 | CRITICAL9.8 | handlebars 4.7.7 fixed in 4.7.9 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-23436 | CRITICAL9.8 | immer 9.0.5 fixed in 9.0.6 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3757 | CRITICAL9.8 | immer 9.0.5 fixed in 9.0.6 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-29415 | CRITICAL9.8 | ip 1.1.5 No fix yet | 8.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-42282 | CRITICAL9.8 | ip 1.1.5 fixed in 2.0.1, 1.1.9 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3918 | CRITICAL9.8 | json-schema 0.2.3 fixed in 0.4.0 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3918 | CRITICAL9.8 | json-schema 0.3.0 fixed in 0.4.0 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21534 | CRITICAL9.8 | jsonpath-plus 0.19.0 fixed in 10.2.0 | 9.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-4800 | CRITICAL9.8 | lodash 4.17.15 fixed in 4.18.0 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-4800 | CRITICAL9.8 | lodash 4.17.21 fixed in 4.18.0 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-4800 | CRITICAL9.8 | lodash-es 4.17.15 fixed in 4.18.0 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44906 | CRITICAL9.8 | minimist 0.0.8 fixed in 1.2.6, 0.2.4 | 4.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44906 | CRITICAL9.8 | minimist 1.2.5 fixed in 1.2.6, 0.2.4 | 4.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2216 | CRITICAL9.8 | parse-url 5.0.1 fixed in 6.0.1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36665 | CRITICAL9.8 | protobufjs 6.11.2 fixed in 7.2.5, 6.11.4 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-43441 | CRITICAL9.8 | sqlite3 5.0.2 fixed in 5.1.5 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-26136 | CRITICAL9.8 | tough-cookie 2.4.3 fixed in 4.1.3 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-26136 | CRITICAL9.8 | tough-cookie 2.5.0 fixed in 4.1.3 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-26136 | CRITICAL9.8 | tough-cookie 4.0.0 fixed in 4.1.3 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-39353 | CRITICAL9.8 | xmldom 0.1.27 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-39353 | CRITICAL9.8 | xmldom 0.1.31 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-39353 | CRITICAL9.8 | xmldom 0.4.0 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-39353 | CRITICAL9.8 | xmldom 0.6.0 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24065 | CRITICAL9.8 | cookiecutter 1.7.3 fixed in 2.1.1 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-44487 | CRITICAL9.75 | libnghttp2-14 1.36.0-2+deb10u1 fixed in 1.36.0-2+deb10u2 | 100.0% Actively Exploited | Directly Exposed |
| CVE-2022-0778 | CRITICAL9.75 | libssl1.1 1.1.1d-0+deb10u6 fixed in 1.1.1d-0+deb10u8 | 73.2% Actively Exploited | Directly Exposed |
| CVE-2023-50387 | CRITICAL9.75 | libsystemd0 241-7~deb10u8 No fix yet | 100.0% Actively Exploited | Directly Exposed |
| CVE-2023-50868 | CRITICAL9.75 | libsystemd0 241-7~deb10u8 No fix yet | 73.7% Actively Exploited | Directly Exposed |
| CVE-2023-50387 | CRITICAL9.75 | libudev1 241-7~deb10u8 No fix yet | 100.0% Actively Exploited | Directly Exposed |
| CVE-2023-50868 | CRITICAL9.75 | libudev1 241-7~deb10u8 No fix yet | 73.7% Actively Exploited | Directly Exposed |
| CVE-2023-50387 | CRITICAL9.75 | libunbound8 1.9.0-2+deb10u2 fixed in 1.9.0-2+deb10u4 | 100.0% Actively Exploited | Directly Exposed |
| CVE-2023-50868 | CRITICAL9.75 | libunbound8 1.9.0-2+deb10u2 fixed in 1.9.0-2+deb10u4 | 73.7% Actively Exploited | Directly Exposed |
| CVE-2018-25032 | CRITICAL9.75 | zlib1g 1:1.2.11.dfsg-1 fixed in 1:1.2.11.dfsg-1+deb10u1 | 51.7% Actively Exploited | Directly Exposed |
| CVE-2021-3712 | CRITICAL9.62 | libssl1.1 1.1.1d-0+deb10u6 fixed in 1.1.1d-0+deb10u7 | 50.4% Actively Exploited | Directly Exposed |
| CVE-2023-0286 | CRITICAL9.62 | libssl1.1 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u4 | 59.5% Actively Exploited | Directly Exposed |
| CVE-2022-1292 | CRITICAL9.49 | libssl1.1 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u2 | 82.6% Actively Exploited | Directly Exposed |
| CVE-2022-2068 | CRITICAL9.49 | libssl1.1 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u3 | 95.4% Actively Exploited | Directly Exposed |
| CVE-2022-21824 | CRITICAL9.43 | libnode64 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u2 | 21.5% High Exploitation Risk | Directly Exposed |
| CVE-2022-21824 | CRITICAL9.43 | nodejs 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u2 | 21.5% High Exploitation Risk | Directly Exposed |
| CVE-2022-43548 | CRITICAL9.31 | libnode64 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u3 | 14.6% High Exploitation Risk | Directly Exposed |
| CVE-2022-43548 | CRITICAL9.31 | nodejs 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u3 | 14.6% High Exploitation Risk | Directly Exposed |
| CVE-2021-35942 | CRITICAL9.1 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35942 | CRITICAL9.1 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35942 | CRITICAL9.1 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35942 | CRITICAL9.1 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1586 | CRITICAL9.1 | libpcre2-8-0 10.32-5 fixed in 10.32-5+deb10u1 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1587 | CRITICAL9.1 | libpcre2-8-0 10.32-5 fixed in 10.32-5+deb10u1 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-46848 | CRITICAL9.1 | libtasn1-6 4.13-3 fixed in 4.13-3+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-46848 | CRITICAL9.1 | libtasn1-6-dev 4.13-3 fixed in 4.13-3+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2900 | CRITICAL9.1 | parse-url 5.0.1 fixed in 8.1.0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-29774 | CRITICAL9.1 | xml-crypto 2.0.0 fixed in 6.0.1, 3.2.1, 2.1.6 | 9.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-29775 | CRITICAL9.1 | xml-crypto 2.0.0 fixed in 6.0.1, 3.2.1, 2.1.6 | 9.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-21598 | HIGH8.8 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u3 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-45960 | HIGH8.8 | libexpat1 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u2 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-22825 | HIGH8.8 | libexpat1 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u2 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-22826 | HIGH8.8 | libexpat1 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u2 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-22827 | HIGH8.8 | libexpat1 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u2 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-45960 | HIGH8.8 | libexpat1-dev 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u2 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-22825 | HIGH8.8 | libexpat1-dev 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u2 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-22826 | HIGH8.8 | libexpat1-dev 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u2 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-22827 | HIGH8.8 | libexpat1-dev 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u2 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libgssapi-krb5-2 1.17-3+deb10u1 fixed in 1.17-3+deb10u5 | 6.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libgssrpc4 1.17-3+deb10u1 fixed in 1.17-3+deb10u5 | 6.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-19498 | HIGH8.8 | libheif1 1.3.2-2~deb10u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-19499 | HIGH8.8 | libheif1 1.3.2-2~deb10u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libk5crypto3 1.17-3+deb10u1 fixed in 1.17-3+deb10u5 | 6.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libkadm5clnt-mit11 1.17-3+deb10u1 fixed in 1.17-3+deb10u5 | 6.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libkadm5srv-mit11 1.17-3+deb10u1 fixed in 1.17-3+deb10u5 | 6.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libkdb5-9 1.17-3+deb10u1 fixed in 1.17-3+deb10u5 | 6.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libkrb5-3 1.17-3+deb10u1 fixed in 1.17-3+deb10u5 | 6.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libkrb5-dev 1.17-3+deb10u1 fixed in 1.17-3+deb10u5 | 6.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libkrb5support0 1.17-3+deb10u1 fixed in 1.17-3+deb10u5 | 6.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1271 | HIGH8.8 | liblzma-dev 5.2.4-1 fixed in 5.2.4-1+deb10u1 | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1271 | HIGH8.8 | liblzma5 5.2.4-1 fixed in 5.2.4-1+deb10u1 | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-44638 | HIGH8.8 | libpixman-1-0 0.36.0-1 fixed in 0.36.0-1+deb10u1 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-44638 | HIGH8.8 | libpixman-1-dev 0.36.0-1 fixed in 0.36.0-1+deb10u1 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39417 | HIGH8.8 | libpq-dev 11.12-0+deb10u1 fixed in 11.21-0+deb10u2 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5869 | HIGH8.8 | libpq-dev 11.12-0+deb10u1 fixed in 11.22-0+deb10u1 | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39417 | HIGH8.8 | libpq5 11.12-0+deb10u1 fixed in 11.21-0+deb10u2 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5869 | HIGH8.8 | libpq5 11.12-0+deb10u1 fixed in 11.22-0+deb10u1 | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24407 | HIGH8.8 | libsasl2-2 2.1.27+dfsg-1+deb10u1 fixed in 2.1.27+dfsg-1+deb10u2 | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24407 | HIGH8.8 | libsasl2-modules-db 2.1.27+dfsg-1+deb10u1 fixed in 2.1.27+dfsg-1+deb10u2 | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3970 | HIGH8.8 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3970 | HIGH8.8 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-46175 | HIGH8.8 | json5 2.2.0 fixed in 2.2.2, 1.0.2 | 9.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-36222 | HIGH8.62 | libgssapi-krb5-2 1.17-3+deb10u1 fixed in 1.17-3+deb10u2 | 10.3% High Exploitation Risk | Directly Exposed |
| CVE-2021-36222 | HIGH8.62 | libgssrpc4 1.17-3+deb10u1 fixed in 1.17-3+deb10u2 | 10.3% High Exploitation Risk | Directly Exposed |
| CVE-2021-36222 | HIGH8.62 | libk5crypto3 1.17-3+deb10u1 fixed in 1.17-3+deb10u2 | 10.3% High Exploitation Risk | Directly Exposed |
| CVE-2021-36222 | HIGH8.62 | libkadm5clnt-mit11 1.17-3+deb10u1 fixed in 1.17-3+deb10u2 | 10.3% High Exploitation Risk | Directly Exposed |
| CVE-2021-36222 | HIGH8.62 | libkadm5srv-mit11 1.17-3+deb10u1 fixed in 1.17-3+deb10u2 | 10.3% High Exploitation Risk | Directly Exposed |
| CVE-2021-36222 | HIGH8.62 | libkdb5-9 1.17-3+deb10u1 fixed in 1.17-3+deb10u2 | 10.3% High Exploitation Risk | Directly Exposed |
| CVE-2021-36222 | HIGH8.62 | libkrb5-3 1.17-3+deb10u1 fixed in 1.17-3+deb10u2 | 10.3% High Exploitation Risk | Directly Exposed |
| CVE-2021-36222 | HIGH8.62 | libkrb5-dev 1.17-3+deb10u1 fixed in 1.17-3+deb10u2 | 10.3% High Exploitation Risk | Directly Exposed |
| CVE-2021-36222 | HIGH8.62 | libkrb5support0 1.17-3+deb10u1 fixed in 1.17-3+deb10u2 | 10.3% High Exploitation Risk | Directly Exposed |
| CVE-2021-22940 | HIGH8.62 | libnode64 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u2 | 13.9% High Exploitation Risk | Directly Exposed |
| CVE-2021-3737 | HIGH8.62 | libpython2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 11.6% High Exploitation Risk | Directly Exposed |
| CVE-2023-24329 | HIGH8.62 | libpython2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 20.5% High Exploitation Risk | Directly Exposed |
| CVE-2021-3737 | HIGH8.62 | libpython2.7-stdlib 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 11.6% High Exploitation Risk | Directly Exposed |
| CVE-2023-24329 | HIGH8.62 | libpython2.7-stdlib 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 20.5% High Exploitation Risk | Directly Exposed |
| CVE-2021-3737 | HIGH8.62 | libpython3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 11.6% High Exploitation Risk | Directly Exposed |
| CVE-2023-24329 | HIGH8.62 | libpython3.7-minimal 3.7.3-2+deb10u3 No fix yet | 20.5% High Exploitation Risk | Directly Exposed |
| CVE-2021-3737 | HIGH8.62 | libpython3.7-stdlib 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 11.6% High Exploitation Risk | Directly Exposed |
| CVE-2023-24329 | HIGH8.62 | libpython3.7-stdlib 3.7.3-2+deb10u3 No fix yet | 20.5% High Exploitation Risk | Directly Exposed |
| CVE-2022-4450 | HIGH8.62 | libssl1.1 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u4 | 20.4% High Exploitation Risk | Directly Exposed |
| CVE-2022-40303 | HIGH8.62 | libxml2 2.9.4+dfsg1-7+deb10u2 fixed in 2.9.4+dfsg1-7+deb10u5 | 41.4% High Exploitation Risk | Directly Exposed |
| CVE-2022-40303 | HIGH8.62 | libxml2-dev 2.9.4+dfsg1-7+deb10u2 fixed in 2.9.4+dfsg1-7+deb10u5 | 41.4% High Exploitation Risk | Directly Exposed |
| CVE-2021-22940 | HIGH8.62 | nodejs 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u2 | 13.9% High Exploitation Risk | Directly Exposed |
| CVE-2021-3737 | HIGH8.62 | python3.7 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 11.6% High Exploitation Risk | Directly Exposed |
| CVE-2023-24329 | HIGH8.62 | python3.7 3.7.3-2+deb10u3 No fix yet | 20.5% High Exploitation Risk | Directly Exposed |
| CVE-2021-3737 | HIGH8.62 | python3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 11.6% High Exploitation Risk | Directly Exposed |
| CVE-2023-24329 | HIGH8.62 | python3.7-minimal 3.7.3-2+deb10u3 No fix yet | 20.5% High Exploitation Risk | Directly Exposed |
| CVE-2022-38900 | HIGH8.62 | decode-uri-component 0.2.0 fixed in 0.2.1 | 23.8% High Exploitation Risk | Directly Exposed |
| CVE-2022-24999 | HIGH8.62 | qs 6.10.1 fixed in 6.10.3, 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, 6.2.4 | 15.6% High Exploitation Risk | Directly Exposed |
| CVE-2022-24999 | HIGH8.62 | qs 6.5.2 fixed in 6.10.3, 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, 6.2.4 | 15.6% High Exploitation Risk | Directly Exposed |
| CVE-2022-24999 | HIGH8.62 | qs 6.7.0 fixed in 6.10.3, 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, 6.2.4 | 15.6% High Exploitation Risk | Directly Exposed |
| CVE-2021-40978 | HIGH8.62 | mkdocs 1.2.2 fixed in 1.2.3 | 15.1% High Exploitation Risk | Directly Exposed |
| CVE-2022-4904 | HIGH8.6 | libc-ares2 1.14.0-1 fixed in 1.14.0-1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-23434 | HIGH8.6 | object-path 0.11.5 fixed in 0.11.6 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42043 | HIGH8.5 | axios 0.21.1 fixed in 1.15.1, 0.31.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-43783 | HIGH8.5 | @backstage/plugin-scaffolder-backend 0.14.2 fixed in 0.15.14 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-44267 | HIGH8.45 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 76.6% Actively Exploited | Directly Exposed |
| CVE-2022-44268 | HIGH8.45 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 89.9% Actively Exploited | Directly Exposed |
| CVE-2022-44267 | HIGH8.45 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 76.6% Actively Exploited | Directly Exposed |
| CVE-2022-44268 | HIGH8.45 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 89.9% Actively Exploited | Directly Exposed |
| CVE-2022-44267 | HIGH8.45 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 76.6% Actively Exploited | Directly Exposed |
| CVE-2022-44268 | HIGH8.45 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 89.9% Actively Exploited | Directly Exposed |
| CVE-2022-44267 | HIGH8.45 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 76.6% Actively Exploited | Directly Exposed |
| CVE-2022-44268 | HIGH8.45 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 89.9% Actively Exploited | Directly Exposed |
| CVE-2022-44267 | HIGH8.45 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 76.6% Actively Exploited | Directly Exposed |
| CVE-2022-44268 | HIGH8.45 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 89.9% Actively Exploited | Directly Exposed |
| CVE-2022-44267 | HIGH8.45 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 76.6% Actively Exploited | Directly Exposed |
| CVE-2022-44268 | HIGH8.45 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 89.9% Actively Exploited | Directly Exposed |
| CVE-2022-44267 | HIGH8.45 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 76.6% Actively Exploited | Directly Exposed |
| CVE-2022-44268 | HIGH8.45 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 89.9% Actively Exploited | Directly Exposed |
| CVE-2022-44267 | HIGH8.45 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 76.6% Actively Exploited | Directly Exposed |
| CVE-2022-44268 | HIGH8.45 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 89.9% Actively Exploited | Directly Exposed |
| CVE-2022-44267 | HIGH8.45 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 76.6% Actively Exploited | Directly Exposed |
| CVE-2022-44268 | HIGH8.45 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 89.9% Actively Exploited | Directly Exposed |
| CVE-2023-2650 | HIGH8.45 | libssl1.1 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u5 | 75.1% Actively Exploited | Directly Exposed |
| CVE-2026-41242 | HIGH8.33 | protobufjs 6.11.2 fixed in 8.0.1, 7.5.5 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-37920 | HIGH8.33 | certifi 2021.5.30 fixed in 2023.7.22 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-23337 | HIGH8.28 | lodash 4.17.15 fixed in 4.17.21 | 21.3% High Exploitation Risk | Directly Exposed |
| CVE-2021-23337 | HIGH8.28 | lodash-es 4.17.15 fixed in 4.17.21 | 21.3% High Exploitation Risk | Directly Exposed |
| CVE-2018-12886 | HIGH8.1 | gcc-8-base 8.3.0-6 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-12886 | HIGH8.1 | libasan5 8.3.0-6 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-12886 | HIGH8.1 | libatomic1 8.3.0-6 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-6096 | HIGH8.1 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 5.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-6096 | HIGH8.1 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 5.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-6096 | HIGH8.1 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 5.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-6096 | HIGH8.1 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 5.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-12886 | HIGH8.1 | libcc1-0 8.3.0-6 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-40674 | HIGH8.1 | libexpat1 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u5 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-40674 | HIGH8.1 | libexpat1-dev 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u5 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-12886 | HIGH8.1 | libgcc-8-dev 8.3.0-6 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-12886 | HIGH8.1 | libgcc1 1:8.3.0-6 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-12886 | HIGH8.1 | libgomp1 8.3.0-6 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-23109 | HIGH8.1 | libheif1 1.3.2-2~deb10u1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-12886 | HIGH8.1 | libitm1 8.3.0-6 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-12886 | HIGH8.1 | liblsan0 8.3.0-6 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-17543 | HIGH8.1 | liblz4-1 1.8.3-1+deb10u1 No fix yet | 9.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-12886 | HIGH8.1 | libmpx2 8.3.0-6 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32212 | HIGH8.1 | libnode64 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u2 | 6.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-31484 | HIGH8.1 | libperl5.28 5.28.1-6+deb10u1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-23214 | HIGH8.1 | libpq-dev 11.12-0+deb10u1 fixed in 11.14-0+deb10u1 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-23214 | HIGH8.1 | libpq5 11.12-0+deb10u1 fixed in 11.14-0+deb10u1 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2018-12886 | HIGH8.1 | libquadmath0 8.3.0-6 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-12886 | HIGH8.1 | libstdc++-8-dev 8.3.0-6 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-12886 | HIGH8.1 | libstdc++6 8.3.0-6 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-12886 | HIGH8.1 | libtsan0 8.3.0-6 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-12886 | HIGH8.1 | libubsan1 8.3.0-6 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32212 | HIGH8.1 | nodejs 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u2 | 6.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-31484 | HIGH8.1 | perl-modules-5.28 5.28.1-6+deb10u1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-106501 | HIGH8.1 | @backstage/plugin-scaffolder-backend 0.14.2 fixed in 3.3.1, 3.4.1, 4.0.3, 4.1.0 | — | Directly Exposed |
| CVE-2026-106503 | HIGH8.1 | @backstage/plugin-scaffolder-backend 0.14.2 fixed in 3.3.1, 3.4.1, 4.0.3, 4.1.0 | — | Directly Exposed |
| CVE-2022-39299 | HIGH8.1 | passport-saml 2.0.5 fixed in 3.2.2 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-43804 | HIGH8.1 | urllib3 1.26.6 fixed in 2.0.6, 1.26.17 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-22930 | HIGH8 | libnode64 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u2 | 36.5% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2021-22930 | HIGH8 | nodejs 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u2 | 36.5% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2025-1302 | HIGH8 | jsonpath-plus 0.19.0 fixed in 10.3.0 | 10.4% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-2625 | HIGH8 | libpq-dev 11.12-0+deb10u1 fixed in 11.17-0+deb10u1 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0985 | HIGH8 | libpq-dev 11.12-0+deb10u1 fixed in 11.22-0+deb10u2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2625 | HIGH8 | libpq5 11.12-0+deb10u1 fixed in 11.17-0+deb10u1 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0985 | HIGH8 | libpq5 11.12-0+deb10u1 fixed in 11.22-0+deb10u2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2020-19667 | HIGH7.8 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27766 | HIGH7.8 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-29599 | HIGH7.8 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 7.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28463 | HIGH7.8 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32545 | HIGH7.8 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32546 | HIGH7.8 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32547 | HIGH7.8 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-19667 | HIGH7.8 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27766 | HIGH7.8 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-29599 | HIGH7.8 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 7.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28463 | HIGH7.8 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32545 | HIGH7.8 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32546 | HIGH7.8 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32547 | HIGH7.8 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-19667 | HIGH7.8 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27766 | HIGH7.8 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-29599 | HIGH7.8 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 7.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28463 | HIGH7.8 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32545 | HIGH7.8 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32546 | HIGH7.8 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32547 | HIGH7.8 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1304 | HIGH7.8 | libcom-err2 1.44.5-1+deb10u3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-46143 | HIGH7.8 | libexpat1 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u2 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-46143 | HIGH7.8 | libexpat1-dev 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u2 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1304 | HIGH7.8 | libext2fs2 1.44.5-1+deb10u3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-19667 | HIGH7.8 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27766 | HIGH7.8 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-29599 | HIGH7.8 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 7.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28463 | HIGH7.8 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32545 | HIGH7.8 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32546 | HIGH7.8 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32547 | HIGH7.8 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-19667 | HIGH7.8 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27766 | HIGH7.8 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-29599 | HIGH7.8 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 7.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28463 | HIGH7.8 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32545 | HIGH7.8 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32546 | HIGH7.8 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32547 | HIGH7.8 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-19667 | HIGH7.8 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27766 | HIGH7.8 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-29599 | HIGH7.8 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 7.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28463 | HIGH7.8 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32545 | HIGH7.8 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32546 | HIGH7.8 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32547 | HIGH7.8 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-19667 | HIGH7.8 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27766 | HIGH7.8 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-29599 | HIGH7.8 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 7.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28463 | HIGH7.8 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32545 | HIGH7.8 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32546 | HIGH7.8 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32547 | HIGH7.8 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-19667 | HIGH7.8 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27766 | HIGH7.8 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-29599 | HIGH7.8 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 7.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28463 | HIGH7.8 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32545 | HIGH7.8 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32546 | HIGH7.8 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32547 | HIGH7.8 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-19667 | HIGH7.8 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27766 | HIGH7.8 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-29599 | HIGH7.8 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 7.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-28463 | HIGH7.8 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32545 | HIGH7.8 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32546 | HIGH7.8 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32547 | HIGH7.8 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3575 | HIGH7.8 | libopenjp2-7 2.3.0-2+deb10u2 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3575 | HIGH7.8 | libopenjp2-7-dev 2.3.0-2+deb10u2 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1304 | HIGH7.8 | libss2 1.44.5-1+deb10u3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-26604 | HIGH7.8 | libsystemd0 241-7~deb10u8 fixed in 241-7~deb10u9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-26604 | HIGH7.8 | libudev1 241-7~deb10u8 fixed in 241-7~deb10u9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-40304 | HIGH7.8 | libxml2 2.9.4+dfsg1-7+deb10u2 fixed in 2.9.4+dfsg1-7+deb10u5 | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-40304 | HIGH7.8 | libxml2-dev 2.9.4+dfsg1-7+deb10u2 fixed in 2.9.4+dfsg1-7+deb10u5 | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-43138 | HIGH7.8 | async 2.6.3 fixed in 3.2.2, 2.6.4 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-43138 | HIGH7.8 | async 3.2.0 fixed in 3.2.2, 2.6.4 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-24046 | HIGH7.73 | @backstage/plugin-scaffolder-backend 0.14.2 fixed in 2.2.2, 3.0.2, 3.1.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33896 | HIGH7.73 | node-forge 0.10.0 fixed in 1.4.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33896 | HIGH7.73 | node-forge 0.8.5 fixed in 1.4.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-9288 | HIGH7.73 | sha.js 2.4.11 fixed in 2.4.12 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-44495 | HIGH7.7 | axios 0.21.1 fixed in 1.15.2, 0.31.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc-bin 2.28-10 fixed in 2.28-10+deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc6 2.28-10 fixed in 2.28-10+deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2015-20107 | HIGH7.6 | libpython2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 7.1% Low-Moderate Risk | Directly Exposed |
| CVE-2015-20107 | HIGH7.6 | libpython2.7-stdlib 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 7.1% Low-Moderate Risk | Directly Exposed |
| CVE-2015-20107 | HIGH7.6 | libpython3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 7.1% Low-Moderate Risk | Directly Exposed |
| CVE-2015-20107 | HIGH7.6 | libpython3.7-stdlib 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 7.1% Low-Moderate Risk | Directly Exposed |
| CVE-2015-20107 | HIGH7.6 | python3.7 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 7.1% Low-Moderate Risk | Directly Exposed |
| CVE-2015-20107 | HIGH7.6 | python3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 7.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15847 | HIGH7.5 | gcc-8-base 8.3.0-6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20309 | HIGH7.5 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20312 | HIGH7.5 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20313 | HIGH7.5 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20309 | HIGH7.5 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20312 | HIGH7.5 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20313 | HIGH7.5 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20309 | HIGH7.5 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20312 | HIGH7.5 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20313 | HIGH7.5 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15847 | HIGH7.5 | libasan5 8.3.0-6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15847 | HIGH7.5 | libatomic1 8.3.0-6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-32067 | HIGH7.5 | libc-ares2 1.14.0-1 fixed in 1.14.0-1+deb10u3 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3326 | HIGH7.5 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3326 | HIGH7.5 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3326 | HIGH7.5 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3326 | HIGH7.5 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15847 | HIGH7.5 | libcc1-0 8.3.0-6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-18804 | HIGH7.5 | libdjvulibre-dev 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-18804 | HIGH7.5 | libdjvulibre-text 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-18804 | HIGH7.5 | libdjvulibre21 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23990 | HIGH7.5 | libexpat1 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u2 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25314 | HIGH7.5 | libexpat1 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u3 | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-43680 | HIGH7.5 | libexpat1 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u6 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52425 | HIGH7.5 | libexpat1 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u7 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23990 | HIGH7.5 | libexpat1-dev 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u2 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25314 | HIGH7.5 | libexpat1-dev 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u3 | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-43680 | HIGH7.5 | libexpat1-dev 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u6 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52425 | HIGH7.5 | libexpat1-dev 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u7 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27405 | HIGH7.5 | libfreetype6 2.9.1-3+deb10u2 fixed in 2.9.1-3+deb10u3 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27406 | HIGH7.5 | libfreetype6 2.9.1-3+deb10u2 fixed in 2.9.1-3+deb10u3 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15847 | HIGH7.5 | libgcc-8-dev 8.3.0-6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15847 | HIGH7.5 | libgcc1 1:8.3.0-6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33560 | HIGH7.5 | libgcrypt20 1.8.4-5+deb10u1 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-43618 | HIGH7.5 | libgmp-dev 2:6.1.2+dfsg-4 fixed in 2:6.1.2+dfsg-4+deb10u1 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-43618 | HIGH7.5 | libgmp10 2:6.1.2+dfsg-4 fixed in 2:6.1.2+dfsg-4+deb10u1 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-43618 | HIGH7.5 | libgmpxx4ldbl 2:6.1.2+dfsg-4 fixed in 2:6.1.2+dfsg-4+deb10u1 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2509 | HIGH7.5 | libgnutls-dane0 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u9 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0553 | HIGH7.5 | libgnutls-dane0 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u12 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2509 | HIGH7.5 | libgnutls-openssl27 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u9 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0553 | HIGH7.5 | libgnutls-openssl27 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u12 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2509 | HIGH7.5 | libgnutls28-dev 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u9 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0553 | HIGH7.5 | libgnutls28-dev 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u12 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2509 | HIGH7.5 | libgnutls30 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u9 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0553 | HIGH7.5 | libgnutls30 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u12 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2509 | HIGH7.5 | libgnutlsxx28 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u9 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0553 | HIGH7.5 | libgnutlsxx28 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u12 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15847 | HIGH7.5 | libgomp1 8.3.0-6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-25193 | HIGH7.5 | libharfbuzz0b 2.3.1-1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12290 | HIGH7.5 | libidn2-0 2.0.5-1+deb10u1 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12290 | HIGH7.5 | libidn2-dev 2.0.5-1+deb10u1 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15847 | HIGH7.5 | libitm1 8.3.0-6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2953 | HIGH7.5 | libldap-2.4-2 2.4.47+dfsg-3+deb10u6 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2953 | HIGH7.5 | libldap-common 2.4.47+dfsg-3+deb10u6 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15847 | HIGH7.5 | liblsan0 8.3.0-6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20309 | HIGH7.5 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20312 | HIGH7.5 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20313 | HIGH7.5 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20309 | HIGH7.5 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20312 | HIGH7.5 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20313 | HIGH7.5 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20309 | HIGH7.5 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20312 | HIGH7.5 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20313 | HIGH7.5 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20309 | HIGH7.5 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20312 | HIGH7.5 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20313 | HIGH7.5 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20309 | HIGH7.5 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20312 | HIGH7.5 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20313 | HIGH7.5 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20309 | HIGH7.5 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20312 | HIGH7.5 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20313 | HIGH7.5 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-46669 | HIGH7.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27376 | HIGH7.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27377 | HIGH7.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27378 | HIGH7.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27379 | HIGH7.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27380 | HIGH7.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27381 | HIGH7.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27383 | HIGH7.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27384 | HIGH7.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27386 | HIGH7.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27387 | HIGH7.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27445 | HIGH7.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27447 | HIGH7.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27448 | HIGH7.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27449 | HIGH7.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27452 | HIGH7.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27456 | HIGH7.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32083 | HIGH7.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32084 | HIGH7.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32085 | HIGH7.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32087 | HIGH7.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32088 | HIGH7.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32091 | HIGH7.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15847 | HIGH7.5 | libmpx2 8.3.0-6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-11080 | HIGH7.5 | libnghttp2-14 1.36.0-2+deb10u1 fixed in 1.36.0-2+deb10u2 | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-30590 | HIGH7.5 | libnode64 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u4 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20298 | HIGH7.5 | libopenexr-dev 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20299 | HIGH7.5 | libopenexr-dev 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20298 | HIGH7.5 | libopenexr23 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20299 | HIGH7.5 | libopenexr23 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20454 | HIGH7.5 | libpcre2-8-0 10.32-5 fixed in 10.32-5+deb10u1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20907 | HIGH7.5 | libpython2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 6.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10735 | HIGH7.5 | libpython2.7-minimal 2.7.16-2+deb10u1 No fix yet | 7.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0391 | HIGH7.5 | libpython2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 8.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-45061 | HIGH7.5 | libpython2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48560 | HIGH7.5 | libpython2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20907 | HIGH7.5 | libpython2.7-stdlib 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 6.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10735 | HIGH7.5 | libpython2.7-stdlib 2.7.16-2+deb10u1 No fix yet | 7.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0391 | HIGH7.5 | libpython2.7-stdlib 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 8.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-45061 | HIGH7.5 | libpython2.7-stdlib 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48560 | HIGH7.5 | libpython2.7-stdlib 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10735 | HIGH7.5 | libpython3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 7.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0391 | HIGH7.5 | libpython3.7-minimal 3.7.3-2+deb10u3 No fix yet | 8.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-45061 | HIGH7.5 | libpython3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48560 | HIGH7.5 | libpython3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u6 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10735 | HIGH7.5 | libpython3.7-stdlib 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 7.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0391 | HIGH7.5 | libpython3.7-stdlib 3.7.3-2+deb10u3 No fix yet | 8.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-45061 | HIGH7.5 | libpython3.7-stdlib 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48560 | HIGH7.5 | libpython3.7-stdlib 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u6 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15847 | HIGH7.5 | libquadmath0 8.3.0-6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19603 | HIGH7.5 | libsqlite3-0 3.27.2-3+deb10u1 No fix yet | 8.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-35525 | HIGH7.5 | libsqlite3-0 3.27.2-3+deb10u1 fixed in 3.27.2-3+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0215 | HIGH7.5 | libssl1.1 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u4 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0464 | HIGH7.5 | libssl1.1 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u5 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15847 | HIGH7.5 | libstdc++-8-dev 8.3.0-6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15847 | HIGH7.5 | libstdc++6 8.3.0-6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24070 | HIGH7.5 | libsvn1 1.10.4-1+deb10u2 fixed in 1.10.4-1+deb10u3 | 9.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52355 | HIGH7.5 | libtiff5 4.1.0+git191117-2~deb10u2 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52356 | HIGH7.5 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u9 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52355 | HIGH7.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52356 | HIGH7.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u9 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15847 | HIGH7.5 | libtsan0 8.3.0-6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15847 | HIGH7.5 | libubsan1 8.3.0-6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3204 | HIGH7.5 | libunbound8 1.9.0-2+deb10u2 fixed in 1.9.0-2+deb10u3 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3138 | HIGH7.5 | libx11-6 2:1.6.7-1+deb10u2 fixed in 2:1.6.7-1+deb10u3 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3138 | HIGH7.5 | libx11-data 2:1.6.7-1+deb10u2 fixed in 2:1.6.7-1+deb10u3 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3138 | HIGH7.5 | libx11-dev 2:1.6.7-1+deb10u2 fixed in 2:1.6.7-1+deb10u3 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16932 | HIGH7.5 | libxml2 2.9.4+dfsg1-7+deb10u2 No fix yet | 5.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2309 | HIGH7.5 | libxml2 2.9.4+dfsg1-7+deb10u2 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23308 | HIGH7.5 | libxml2 2.9.4+dfsg1-7+deb10u2 fixed in 2.9.4+dfsg1-7+deb10u3 | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-25062 | HIGH7.5 | libxml2 2.9.4+dfsg1-7+deb10u2 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16932 | HIGH7.5 | libxml2-dev 2.9.4+dfsg1-7+deb10u2 No fix yet | 5.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2309 | HIGH7.5 | libxml2-dev 2.9.4+dfsg1-7+deb10u2 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23308 | HIGH7.5 | libxml2-dev 2.9.4+dfsg1-7+deb10u2 fixed in 2.9.4+dfsg1-7+deb10u3 | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-25062 | HIGH7.5 | libxml2-dev 2.9.4+dfsg1-7+deb10u2 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-5815 | HIGH7.5 | libxslt1-dev 1.1.32-2.2~deb10u1 fixed in 1.1.32-2.2~deb10u2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-5815 | HIGH7.5 | libxslt1.1 1.1.32-2.2~deb10u1 fixed in 1.1.32-2.2~deb10u2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-46669 | HIGH7.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27376 | HIGH7.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27377 | HIGH7.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27378 | HIGH7.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27379 | HIGH7.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27380 | HIGH7.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27381 | HIGH7.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27383 | HIGH7.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27384 | HIGH7.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27386 | HIGH7.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27387 | HIGH7.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27445 | HIGH7.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27447 | HIGH7.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27448 | HIGH7.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27449 | HIGH7.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27452 | HIGH7.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27456 | HIGH7.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32083 | HIGH7.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32084 | HIGH7.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32085 | HIGH7.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32087 | HIGH7.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32088 | HIGH7.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32091 | HIGH7.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-30590 | HIGH7.5 | nodejs 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u4 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10735 | HIGH7.5 | python3.7 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 7.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0391 | HIGH7.5 | python3.7 3.7.3-2+deb10u3 No fix yet | 8.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-45061 | HIGH7.5 | python3.7 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48560 | HIGH7.5 | python3.7 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u6 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10735 | HIGH7.5 | python3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 7.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0391 | HIGH7.5 | python3.7-minimal 3.7.3-2+deb10u3 No fix yet | 8.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-45061 | HIGH7.5 | python3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48560 | HIGH7.5 | python3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u6 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3807 | HIGH7.5 | ansi-regex 3.0.0 fixed in 6.0.1, 5.0.1, 4.1.1, 3.0.1 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3807 | HIGH7.5 | ansi-regex 4.1.0 fixed in 6.0.1, 5.0.1, 4.1.1, 3.0.1 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3807 | HIGH7.5 | ansi-regex 5.0.0 fixed in 6.0.1, 5.0.1, 4.1.1, 3.0.1 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3749 | HIGH7.5 | axios 0.21.1 fixed in 0.21.2 | 8.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-25639 | HIGH7.5 | axios 0.21.1 fixed in 1.13.5, 0.30.3 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4068 | HIGH7.5 | braces 3.0.2 fixed in 3.0.3 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-26289 | HIGH7.5 | date-and-time 0.6.3 fixed in 0.14.2 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-20165 | HIGH7.5 | debug 2.2.0 fixed in 3.1.0, 2.6.9 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24434 | HIGH7.5 | dicer 0.3.0 No fix yet | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25881 | HIGH7.5 | http-cache-semantics 3.8.1 fixed in 4.1.1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25881 | HIGH7.5 | http-cache-semantics 4.1.0 fixed in 4.1.1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21536 | HIGH7.5 | http-proxy-middleware 2.0.0 fixed in 2.0.7, 3.0.3 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-8237 | HIGH7.5 | json-bigint 0.3.1 fixed in 1.0.0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2016-20018 | HIGH7.5 | knex 0.95.6 fixed in 2.4.0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-22467 | HIGH7.5 | luxon 1.27.0 fixed in 1.28.1, 2.5.2, 3.2.1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2016-10540 | HIGH7.5 | minimatch 0.3.0 fixed in 3.0.2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3517 | HIGH7.5 | minimatch 0.3.0 fixed in 3.0.5 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3517 | HIGH7.5 | minimatch 3.0.4 fixed in 3.0.5 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24772 | HIGH7.5 | node-forge 0.10.0 fixed in 1.3.0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24772 | HIGH7.5 | node-forge 0.8.5 fixed in 1.3.0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33502 | HIGH7.5 | normalize-url 4.5.0 fixed in 4.5.1, 5.3.1, 6.0.1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3805 | HIGH7.5 | object-path 0.11.5 fixed in 0.11.8 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0722 | HIGH7.5 | parse-url 5.0.1 fixed in 6.0.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-39171 | HIGH7.5 | passport-saml 2.0.5 fixed in 3.1.0 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-23343 | HIGH7.5 | path-parse 1.0.6 fixed in 1.0.7 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25878 | HIGH7.5 | protobufjs 6.11.2 fixed in 6.11.3, 6.10.3 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25883 | HIGH7.5 | semver 5.3.0 fixed in 7.5.2, 6.3.1, 5.7.2 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25883 | HIGH7.5 | semver 5.7.1 fixed in 7.5.2, 6.3.1, 5.7.2 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25883 | HIGH7.5 | semver 6.3.0 fixed in 7.5.2, 6.3.1, 5.7.2 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25883 | HIGH7.5 | semver 7.3.5 fixed in 7.5.2, 6.3.1, 5.7.2 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0355 | HIGH7.5 | simple-get 3.1.0 fixed in 4.0.1, 3.1.1, 2.8.2 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21227 | HIGH7.5 | sqlite3 5.0.2 fixed in 5.0.3 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12905 | HIGH7.5 | tar-fs 2.0.1 fixed in 1.16.4, 2.1.2, 3.0.7 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12905 | HIGH7.5 | tar-fs 2.1.1 fixed in 1.16.4, 2.1.2, 3.0.7 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3765 | HIGH7.5 | validator 8.2.0 fixed in 13.7.0 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-26115 | HIGH7.5 | word-wrap 1.2.3 fixed in 1.2.4 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-39689 | HIGH7.5 | certifi 2021.5.30 fixed in 2024.7.4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-3651 | HIGH7.5 | idna 3.2 fixed in 3.7 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-32309 | HIGH7.5 | pymdown-extensions 7.1 fixed in 10.0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-21441 | HIGH7.5 | urllib3 1.26.6 fixed in 2.6.3 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97689 | HIGH7.5 | urllib3 1.26.6 fixed in 2.8.0 | — | Directly Exposed |
| CVE-2023-27103 | HIGH7.48 | libde265-0 1.0.3-1+b1 fixed in 1.0.11-0+deb10u5 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-49465 | HIGH7.48 | libde265-0 1.0.3-1+b1 fixed in 1.0.11-0+deb10u6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-49467 | HIGH7.48 | libde265-0 1.0.3-1+b1 fixed in 1.0.11-0+deb10u6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-49468 | HIGH7.48 | libde265-0 1.0.3-1+b1 fixed in 1.0.11-0+deb10u6 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-25434 | HIGH7.48 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-25434 | HIGH7.48 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-44293 | HIGH7.48 | protobufjs 6.11.2 fixed in 7.5.6, 8.0.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-56201 | HIGH7.48 | Jinja2 3.0.1 fixed in 3.1.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-27516 | HIGH7.48 | Jinja2 3.0.1 fixed in 3.1.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-8871 | HIGH7.47 | libcroco3 0.6.12-3 No fix yet | 13.0% High Exploitation Risk | Directly Exposed |
| CVE-2023-0361 | HIGH7.4 | libgnutls-dane0 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u10 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0361 | HIGH7.4 | libgnutls-openssl27 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u10 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0361 | HIGH7.4 | libgnutls28-dev 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u10 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0361 | HIGH7.4 | libgnutls30 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u10 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0361 | HIGH7.4 | libgnutlsxx28 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u10 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44531 | HIGH7.4 | libnode64 10.24.0~dfsg-1~deb10u1 No fix yet | 8.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44531 | HIGH7.4 | nodejs 10.24.0~dfsg-1~deb10u1 No fix yet | 8.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-8203 | HIGH7.4 | lodash 4.17.15 fixed in 4.17.19 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-8203 | HIGH7.4 | lodash-es 4.17.15 fixed in 4.17.20 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97687 | HIGH7.4 | urllib3 1.26.6 fixed in 2.8.0 | — | Directly Exposed |
| CVE-2025-12816 | HIGH7.39 | node-forge 0.10.0 fixed in 1.3.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-12816 | HIGH7.39 | node-forge 0.8.5 fixed in 1.3.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-44492 | HIGH7.31 | axios 0.21.1 fixed in 1.16.0, 0.32.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-55602 | HIGH7.31 | http-proxy-middleware 2.0.0 fixed in 3.0.6, 4.1.0, 2.0.10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-7104 | HIGH7.3 | libsqlite3-0 3.27.2-3+deb10u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-24806 | HIGH7.3 | libuv1 1.24.1-1+deb10u1 fixed in 1.24.1-1+deb10u2 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-7720 | HIGH7.3 | node-forge 0.8.5 fixed in 0.10.0 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2454 | HIGH7.2 | libpq-dev 11.12-0+deb10u1 fixed in 11.20-0+deb10u1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2454 | HIGH7.2 | libpq5 11.12-0+deb10u1 fixed in 11.20-0+deb10u1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-26116 | HIGH7.2 | libpython2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-26116 | HIGH7.2 | libpython2.7-stdlib 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27752 | HIGH7.1 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48541 | HIGH7.1 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u7 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27752 | HIGH7.1 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48541 | HIGH7.1 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u7 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27752 | HIGH7.1 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48541 | HIGH7.1 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u7 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-12825 | HIGH7.1 | libcroco3 0.6.12-3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27752 | HIGH7.1 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48541 | HIGH7.1 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u7 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27752 | HIGH7.1 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48541 | HIGH7.1 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u7 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27752 | HIGH7.1 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48541 | HIGH7.1 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u7 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27752 | HIGH7.1 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48541 | HIGH7.1 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u7 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27752 | HIGH7.1 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48541 | HIGH7.1 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u7 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27752 | HIGH7.1 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48541 | HIGH7.1 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u7 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-2389 | HIGH7.1 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.31-0+deb10u1 | 8.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0891 | HIGH7.1 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u4 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0891 | HIGH7.1 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u4 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-2389 | HIGH7.1 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.31-0+deb10u1 | 8.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-106500 | HIGH7.1 | @backstage/plugin-scaffolder-backend 0.14.2 fixed in 4.1.0 | — | Directly Exposed |
| CVE-2026-44490 | MEDIUM6.97 | axios 0.21.1 fixed in 1.16.0, 0.32.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33941 | MEDIUM6.97 | handlebars 4.7.7 fixed in 4.7.9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44705 | MEDIUM6.97 | tmp 0.0.33 fixed in 0.2.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44705 | MEDIUM6.97 | tmp 0.2.1 fixed in 0.2.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-28182 | MEDIUM6.89 | libnghttp2-14 1.36.0-2+deb10u1 fixed in 1.36.0-2+deb10u3 | 85.0% Actively Exploited | Directly Exposed |
| CVE-2023-43887 | MEDIUM6.88 | libde265-0 1.0.3-1+b1 fixed in 1.0.11-0+deb10u5 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-33938 | MEDIUM6.88 | handlebars 4.7.7 fixed in 4.7.9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33940 | MEDIUM6.88 | handlebars 4.7.7 fixed in 4.7.9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-23539 | MEDIUM6.88 | jsonwebtoken 8.5.1 fixed in 9.0.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44291 | MEDIUM6.88 | protobufjs 6.11.2 fixed in 7.5.6, 8.0.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-83605 | MEDIUM6.88 | xmldom 0.1.27 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83607 | MEDIUM6.88 | xmldom 0.1.27 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83605 | MEDIUM6.88 | xmldom 0.1.31 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83607 | MEDIUM6.88 | xmldom 0.1.31 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83605 | MEDIUM6.88 | xmldom 0.4.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83607 | MEDIUM6.88 | xmldom 0.4.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83605 | MEDIUM6.88 | xmldom 0.6.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83607 | MEDIUM6.88 | xmldom 0.6.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-23336 | MEDIUM6.79 | libpython2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 40.7% High Exploitation Risk | Directly Exposed |
| CVE-2021-23336 | MEDIUM6.79 | libpython2.7-stdlib 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 40.7% High Exploitation Risk | Directly Exposed |
| CVE-2021-23336 | MEDIUM6.79 | libpython3.7-minimal 3.7.3-2+deb10u3 No fix yet | 40.7% High Exploitation Risk | Directly Exposed |
| CVE-2021-23336 | MEDIUM6.79 | libpython3.7-stdlib 3.7.3-2+deb10u3 No fix yet | 40.7% High Exploitation Risk | Directly Exposed |
| CVE-2022-4304 | MEDIUM6.79 | libssl1.1 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u4 | 16.2% High Exploitation Risk | Directly Exposed |
| CVE-2021-23336 | MEDIUM6.79 | python3.7 3.7.3-2+deb10u3 No fix yet | 40.7% High Exploitation Risk | Directly Exposed |
| CVE-2021-23336 | MEDIUM6.79 | python3.7-minimal 3.7.3-2+deb10u3 No fix yet | 40.7% High Exploitation Risk | Directly Exposed |
| CVE-2021-3999 | MEDIUM6.63 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-3999 | MEDIUM6.63 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-3999 | MEDIUM6.63 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-3999 | MEDIUM6.63 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-36409 | MEDIUM6.63 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-47655 | MEDIUM6.63 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47664 | MEDIUM6.63 | libde265-0 1.0.3-1+b1 fixed in 1.0.11-0+deb10u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-47665 | MEDIUM6.63 | libde265-0 1.0.3-1+b1 fixed in 1.0.11-0+deb10u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-25221 | MEDIUM6.63 | libde265-0 1.0.3-1+b1 fixed in 1.0.11-0+deb10u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-32490 | MEDIUM6.63 | libdjvulibre-dev 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-32491 | MEDIUM6.63 | libdjvulibre-dev 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-32492 | MEDIUM6.63 | libdjvulibre-dev 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-32493 | MEDIUM6.63 | libdjvulibre-dev 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-3500 | MEDIUM6.63 | libdjvulibre-dev 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-32490 | MEDIUM6.63 | libdjvulibre-text 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-32491 | MEDIUM6.63 | libdjvulibre-text 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-32492 | MEDIUM6.63 | libdjvulibre-text 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-32493 | MEDIUM6.63 | libdjvulibre-text 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-3500 | MEDIUM6.63 | libdjvulibre-text 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-32490 | MEDIUM6.63 | libdjvulibre21 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-32491 | MEDIUM6.63 | libdjvulibre21 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-32492 | MEDIUM6.63 | libdjvulibre21 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-32493 | MEDIUM6.63 | libdjvulibre21 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-3500 | MEDIUM6.63 | libdjvulibre21 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-25308 | MEDIUM6.63 | libfribidi0 1.0.5-3.1+deb10u1 fixed in 1.0.5-3.1+deb10u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-48622 | MEDIUM6.63 | libgdk-pixbuf2.0-0 2.38.1+dfsg-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-48622 | MEDIUM6.63 | libgdk-pixbuf2.0-bin 2.38.1+dfsg-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-48622 | MEDIUM6.63 | libgdk-pixbuf2.0-common 2.38.1+dfsg-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0996 | MEDIUM6.63 | libheif1 1.3.2-2~deb10u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-24048 | MEDIUM6.63 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-24050 | MEDIUM6.63 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-24051 | MEDIUM6.63 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-24052 | MEDIUM6.63 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2020-16156 | MEDIUM6.63 | libperl5.28 5.28.1-6+deb10u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-42919 | MEDIUM6.63 | libpython3.7-minimal 3.7.3-2+deb10u3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-6597 | MEDIUM6.63 | libpython3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-42919 | MEDIUM6.63 | libpython3.7-stdlib 3.7.3-2+deb10u3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-6597 | MEDIUM6.63 | libpython3.7-stdlib 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-3843 | MEDIUM6.63 | libsystemd0 241-7~deb10u8 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2019-3844 | MEDIUM6.63 | libsystemd0 241-7~deb10u8 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2019-3843 | MEDIUM6.63 | libudev1 241-7~deb10u8 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2019-3844 | MEDIUM6.63 | libudev1 241-7~deb10u8 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-43787 | MEDIUM6.63 | libx11-6 2:1.6.7-1+deb10u2 fixed in 2:1.6.7-1+deb10u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-43787 | MEDIUM6.63 | libx11-data 2:1.6.7-1+deb10u2 fixed in 2:1.6.7-1+deb10u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-43787 | MEDIUM6.63 | libx11-dev 2:1.6.7-1+deb10u2 fixed in 2:1.6.7-1+deb10u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-24048 | MEDIUM6.63 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-24050 | MEDIUM6.63 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-24051 | MEDIUM6.63 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-24052 | MEDIUM6.63 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2020-16156 | MEDIUM6.63 | perl-modules-5.28 5.28.1-6+deb10u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-42919 | MEDIUM6.63 | python3.7 3.7.3-2+deb10u3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-6597 | MEDIUM6.63 | python3.7 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-42919 | MEDIUM6.63 | python3.7-minimal 3.7.3-2+deb10u3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-6597 | MEDIUM6.63 | python3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-3596 | MEDIUM6.5 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3596 | MEDIUM6.5 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3596 | MEDIUM6.5 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25147 | MEDIUM6.5 | libaprutil1 1.6.1-4 fixed in 1.6.1-4+deb10u1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6461 | MEDIUM6.5 | libcairo-gobject2 1.16.0-4+deb10u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6462 | MEDIUM6.5 | libcairo-gobject2 1.16.0-4+deb10u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6461 | MEDIUM6.5 | libcairo-script-interpreter2 1.16.0-4+deb10u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6462 | MEDIUM6.5 | libcairo-script-interpreter2 1.16.0-4+deb10u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6461 | MEDIUM6.5 | libcairo2 1.16.0-4+deb10u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6462 | MEDIUM6.5 | libcairo2 1.16.0-4+deb10u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-8834 | MEDIUM6.5 | libcroco3 0.6.12-3 No fix yet | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2020-21595 | MEDIUM6.5 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-21596 | MEDIUM6.5 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u3 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-21597 | MEDIUM6.5 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u3 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-21599 | MEDIUM6.5 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-21600 | MEDIUM6.5 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-21601 | MEDIUM6.5 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-21602 | MEDIUM6.5 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-21603 | MEDIUM6.5 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-21604 | MEDIUM6.5 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-21605 | MEDIUM6.5 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-21606 | MEDIUM6.5 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35452 | MEDIUM6.5 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-46310 | MEDIUM6.5 | libdjvulibre-dev 3.5.27.1-10 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-46312 | MEDIUM6.5 | libdjvulibre-dev 3.5.27.1-10 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-46310 | MEDIUM6.5 | libdjvulibre-text 3.5.27.1-10 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-46312 | MEDIUM6.5 | libdjvulibre-text 3.5.27.1-10 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-46310 | MEDIUM6.5 | libdjvulibre21 3.5.27.1-10 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-46312 | MEDIUM6.5 | libdjvulibre21 3.5.27.1-10 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25313 | MEDIUM6.5 | libexpat1 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u3 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25313 | MEDIUM6.5 | libexpat1-dev 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u3 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-4209 | MEDIUM6.5 | libgnutls-dane0 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u9 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-4209 | MEDIUM6.5 | libgnutls-openssl27 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u9 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-4209 | MEDIUM6.5 | libgnutls28-dev 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u9 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-4209 | MEDIUM6.5 | libgnutls30 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u9 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-4209 | MEDIUM6.5 | libgnutlsxx28 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u9 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-37750 | MEDIUM6.5 | libgssapi-krb5-2 1.17-3+deb10u1 fixed in 1.17-3+deb10u3 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libgssapi-krb5-2 1.17-3+deb10u1 fixed in 1.17-3+deb10u6 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-37750 | MEDIUM6.5 | libgssrpc4 1.17-3+deb10u1 fixed in 1.17-3+deb10u3 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libgssrpc4 1.17-3+deb10u1 fixed in 1.17-3+deb10u6 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-37750 | MEDIUM6.5 | libk5crypto3 1.17-3+deb10u1 fixed in 1.17-3+deb10u3 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libk5crypto3 1.17-3+deb10u1 fixed in 1.17-3+deb10u6 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-37750 | MEDIUM6.5 | libkadm5clnt-mit11 1.17-3+deb10u1 fixed in 1.17-3+deb10u3 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libkadm5clnt-mit11 1.17-3+deb10u1 fixed in 1.17-3+deb10u6 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-37750 | MEDIUM6.5 | libkadm5srv-mit11 1.17-3+deb10u1 fixed in 1.17-3+deb10u3 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libkadm5srv-mit11 1.17-3+deb10u1 fixed in 1.17-3+deb10u6 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-37750 | MEDIUM6.5 | libkdb5-9 1.17-3+deb10u1 fixed in 1.17-3+deb10u3 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libkdb5-9 1.17-3+deb10u1 fixed in 1.17-3+deb10u6 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-37750 | MEDIUM6.5 | libkrb5-3 1.17-3+deb10u1 fixed in 1.17-3+deb10u3 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libkrb5-3 1.17-3+deb10u1 fixed in 1.17-3+deb10u6 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-37750 | MEDIUM6.5 | libkrb5-dev 1.17-3+deb10u1 fixed in 1.17-3+deb10u3 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libkrb5-dev 1.17-3+deb10u1 fixed in 1.17-3+deb10u6 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-37750 | MEDIUM6.5 | libkrb5support0 1.17-3+deb10u1 fixed in 1.17-3+deb10u3 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libkrb5support0 1.17-3+deb10u1 fixed in 1.17-3+deb10u6 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3596 | MEDIUM6.5 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3596 | MEDIUM6.5 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3596 | MEDIUM6.5 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3596 | MEDIUM6.5 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3596 | MEDIUM6.5 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3596 | MEDIUM6.5 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-47015 | MEDIUM6.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.39-0+deb10u1 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-22025 | MEDIUM6.5 | libnode64 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6988 | MEDIUM6.5 | libopenjp2-7 2.3.0-2+deb10u2 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6988 | MEDIUM6.5 | libopenjp2-7-dev 2.3.0-2+deb10u2 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3677 | MEDIUM6.5 | libpq-dev 11.12-0+deb10u1 fixed in 11.13-0+deb10u1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3677 | MEDIUM6.5 | libpq5 11.12-0+deb10u1 fixed in 11.13-0+deb10u1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-8492 | MEDIUM6.5 | libpython2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 6.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3733 | MEDIUM6.5 | libpython2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-8492 | MEDIUM6.5 | libpython2.7-stdlib 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 6.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3733 | MEDIUM6.5 | libpython2.7-stdlib 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3733 | MEDIUM6.5 | libpython3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48564 | MEDIUM6.5 | libpython3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u6 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3733 | MEDIUM6.5 | libpython3.7-stdlib 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48564 | MEDIUM6.5 | libpython3.7-stdlib 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u6 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20446 | MEDIUM6.5 | librsvg2-2 2.44.10-2.1 fixed in 2.44.10-2.1+deb10u1 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20446 | MEDIUM6.5 | librsvg2-common 2.44.10-2.1 fixed in 2.44.10-2.1+deb10u1 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-19143 | MEDIUM6.5 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u3 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0865 | MEDIUM6.5 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u4 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2056 | MEDIUM6.5 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2057 | MEDIUM6.5 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2058 | MEDIUM6.5 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-34526 | MEDIUM6.5 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3597 | MEDIUM6.5 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3598 | MEDIUM6.5 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3599 | MEDIUM6.5 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3626 | MEDIUM6.5 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3627 | MEDIUM6.5 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3316 | MEDIUM6.5 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u8 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3618 | MEDIUM6.5 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u8 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-40745 | MEDIUM6.5 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u8 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-41175 | MEDIUM6.5 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u8 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6277 | MEDIUM6.5 | libtiff5 4.1.0+git191117-2~deb10u2 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1210 | MEDIUM6.5 | libtiff5 4.1.0+git191117-2~deb10u2 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2020-19143 | MEDIUM6.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u3 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0865 | MEDIUM6.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u4 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2056 | MEDIUM6.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2057 | MEDIUM6.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2058 | MEDIUM6.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-34526 | MEDIUM6.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3597 | MEDIUM6.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3598 | MEDIUM6.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3599 | MEDIUM6.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3626 | MEDIUM6.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3627 | MEDIUM6.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3316 | MEDIUM6.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u8 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3618 | MEDIUM6.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u8 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-40745 | MEDIUM6.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u8 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-41175 | MEDIUM6.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u8 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6277 | MEDIUM6.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1210 | MEDIUM6.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30698 | MEDIUM6.5 | libunbound8 1.9.0-2+deb10u2 fixed in 1.9.0-2+deb10u3 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30699 | MEDIUM6.5 | libunbound8 1.9.0-2+deb10u2 fixed in 1.9.0-2+deb10u3 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29824 | MEDIUM6.5 | libxml2 2.9.4+dfsg1-7+deb10u2 fixed in 2.9.4+dfsg1-7+deb10u4 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29469 | MEDIUM6.5 | libxml2 2.9.4+dfsg1-7+deb10u2 fixed in 2.9.4+dfsg1-7+deb10u6 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29824 | MEDIUM6.5 | libxml2-dev 2.9.4+dfsg1-7+deb10u2 fixed in 2.9.4+dfsg1-7+deb10u4 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29469 | MEDIUM6.5 | libxml2-dev 2.9.4+dfsg1-7+deb10u2 fixed in 2.9.4+dfsg1-7+deb10u6 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-47015 | MEDIUM6.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.39-0+deb10u1 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-22025 | MEDIUM6.5 | nodejs 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3733 | MEDIUM6.5 | python3.7 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48564 | MEDIUM6.5 | python3.7 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u6 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3733 | MEDIUM6.5 | python3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48564 | MEDIUM6.5 | python3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u6 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-106504 | MEDIUM6.5 | @backstage/plugin-scaffolder-backend 0.14.2 fixed in 4.1.0 | — | Directly Exposed |
| CVE-2026-106489 | MEDIUM6.5 | @backstage/plugin-techdocs-backend 0.9.1 fixed in 2.2.4 | — | Directly Exposed |
| CVE-2022-0155 | MEDIUM6.5 | follow-redirects 1.13.0 fixed in 1.14.7 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28849 | MEDIUM6.5 | follow-redirects 1.13.0 fixed in 1.15.6 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-32723 | MEDIUM6.5 | prismjs 1.23.0 fixed in 1.24.0 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3801 | MEDIUM6.5 | prismjs 1.23.0 fixed in 1.25.0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37891 | MEDIUM6.5 | urllib3 1.26.6 fixed in 1.26.19, 2.2.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23540 | MEDIUM6.46 | jsonwebtoken 8.5.1 fixed in 9.0.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-106462 | MEDIUM6.4 | @backstage/plugin-scaffolder-backend 0.14.2 fixed in 4.1.0 | — | Directly Exposed |
| CVE-2021-40211 | MEDIUM6.38 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-40211 | MEDIUM6.38 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-40211 | MEDIUM6.38 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-29499 | MEDIUM6.38 | libglib2.0-0 2.58.3-2+deb10u3 fixed in 2.58.3-2+deb10u5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-29499 | MEDIUM6.38 | libglib2.0-bin 2.58.3-2+deb10u3 fixed in 2.58.3-2+deb10u5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-29499 | MEDIUM6.38 | libglib2.0-data 2.58.3-2+deb10u3 fixed in 2.58.3-2+deb10u5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-29499 | MEDIUM6.38 | libglib2.0-dev-bin 2.58.3-2+deb10u3 fixed in 2.58.3-2+deb10u5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-40211 | MEDIUM6.38 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-40211 | MEDIUM6.38 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-40211 | MEDIUM6.38 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-40211 | MEDIUM6.38 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-40211 | MEDIUM6.38 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-40211 | MEDIUM6.38 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-1999 | MEDIUM6.38 | libwebp-dev 0.6.1-2+deb10u1 fixed in 0.6.1-2+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-1999 | MEDIUM6.38 | libwebp6 0.6.1-2+deb10u1 fixed in 0.6.1-2+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-1999 | MEDIUM6.38 | libwebpdemux2 0.6.1-2+deb10u1 fixed in 0.6.1-2+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-1999 | MEDIUM6.38 | libwebpmux3 0.6.1-2+deb10u1 fixed in 0.6.1-2+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-26150 | MEDIUM6.38 | @backstage/backend-common 0.8.8 fixed in 0.21.1, 0.19.10, 0.20.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-32236 | MEDIUM6.38 | @backstage/plugin-auth-backend 0.3.19 fixed in 0.27.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48068 | MEDIUM6.38 | @grpc/grpc-js 1.3.2 fixed in 1.9.16, 1.10.12, 1.11.4, 1.12.7, 1.13.5, 1.14.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-48069 | MEDIUM6.38 | @grpc/grpc-js 1.3.2 fixed in 1.9.16, 1.10.12, 1.11.4, 1.12.7, 1.13.5, 1.14.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-69873 | MEDIUM6.38 | ajv 6.12.6 fixed in 8.18.0, 6.14.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69873 | MEDIUM6.38 | ajv 7.0.3 fixed in 8.18.0, 6.14.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44486 | MEDIUM6.38 | axios 0.21.1 fixed in 1.16.0, 0.32.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-44487 | MEDIUM6.38 | axios 0.21.1 fixed in 1.16.0, 0.32.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-44496 | MEDIUM6.38 | axios 0.21.1 fixed in 1.16.0, 0.32.0 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42038 | MEDIUM6.38 | axios 0.21.1 fixed in 1.15.1, 0.31.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42039 | MEDIUM6.38 | axios 0.21.1 fixed in 1.15.1, 0.31.1 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-45590 | MEDIUM6.38 | body-parser 1.19.0 fixed in 1.20.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-102276 | MEDIUM6.38 | brace-expansion 1.1.11 fixed in 5.0.10, 3.0.7, 2.1.5, 1.1.19 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102278 | MEDIUM6.38 | brace-expansion 1.1.11 fixed in 5.0.11, 3.0.8, 2.1.6, 1.1.20 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13149 | MEDIUM6.38 | brace-expansion 1.1.11 fixed in 5.0.7, 1.1.16, 2.1.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-14257 | MEDIUM6.38 | brace-expansion 1.1.11 fixed in 5.0.8, 3.0.3, 2.1.3, 1.1.17 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-69152 | MEDIUM6.38 | brace-expansion 1.1.11 fixed in 1.1.18, 2.1.4, 3.0.6, 5.0.9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33750 | MEDIUM6.38 | brace-expansion 1.1.11 fixed in 5.0.5, 3.0.2, 2.0.3, 1.1.13 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-93687 | MEDIUM6.38 | braces 3.0.2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-87776 | MEDIUM6.38 | compression 1.7.4 fixed in 1.8.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45822 | MEDIUM6.38 | decode-uri-component 0.2.0 fixed in 0.5.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-24001 | MEDIUM6.38 | diff 1.4.0 fixed in 8.0.3, 5.2.2, 4.0.4, 3.5.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-24001 | MEDIUM6.38 | diff 4.0.2 fixed in 8.0.3, 5.2.2, 4.0.4, 3.5.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-12143 | MEDIUM6.38 | form-data 2.3.2 fixed in 2.5.6, 3.0.5, 4.0.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-12143 | MEDIUM6.38 | form-data 2.3.3 fixed in 2.5.6, 3.0.5, 4.0.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-12143 | MEDIUM6.38 | form-data 2.5.1 fixed in 2.5.6, 3.0.5, 4.0.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-12143 | MEDIUM6.38 | form-data 3.0.0 fixed in 2.5.6, 3.0.5, 4.0.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-12143 | MEDIUM6.38 | form-data 4.0.0 fixed in 2.5.6, 3.0.5, 4.0.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-33939 | MEDIUM6.38 | handlebars 4.7.7 fixed in 4.7.9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-93748 | MEDIUM6.38 | http-cache-semantics 3.8.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-93748 | MEDIUM6.38 | http-cache-semantics 4.1.0 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46625 | MEDIUM6.38 | js-cookie 2.2.1 fixed in 3.0.7 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-59869 | MEDIUM6.38 | js-yaml 3.13.1 fixed in 3.15.0, 4.3.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-84375 | MEDIUM6.38 | js-yaml 3.13.1 fixed in 4.3.2, 3.15.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59869 | MEDIUM6.38 | js-yaml 3.14.1 fixed in 3.15.0, 4.3.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-84375 | MEDIUM6.38 | js-yaml 3.14.1 fixed in 4.3.2, 3.15.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59869 | MEDIUM6.38 | js-yaml 4.1.0 fixed in 3.15.0, 4.3.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-84375 | MEDIUM6.38 | js-yaml 4.1.0 fixed in 4.3.2, 3.15.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-65945 | MEDIUM6.38 | jws 3.2.2 fixed in 3.2.3, 4.0.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-65945 | MEDIUM6.38 | jws 4.0.0 fixed in 3.2.3, 4.0.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-26996 | MEDIUM6.38 | minimatch 0.3.0 fixed in 10.2.1, 9.0.6, 8.0.5, 7.4.7, 6.2.1, 5.1.7, 4.2.4, 3.1.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-26996 | MEDIUM6.38 | minimatch 3.0.4 fixed in 10.2.1, 9.0.6, 8.0.5, 7.4.7, 6.2.1, 5.1.7, 4.2.4, 3.1.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-24771 | MEDIUM6.38 | node-forge 0.10.0 fixed in 1.3.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-66031 | MEDIUM6.38 | node-forge 0.10.0 fixed in 1.3.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33891 | MEDIUM6.38 | node-forge 0.10.0 fixed in 1.4.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-33894 | MEDIUM6.38 | node-forge 0.10.0 fixed in 1.4.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33895 | MEDIUM6.38 | node-forge 0.10.0 fixed in 1.4.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-85393 | MEDIUM6.38 | node-forge 0.10.0 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-24771 | MEDIUM6.38 | node-forge 0.8.5 fixed in 1.3.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-66031 | MEDIUM6.38 | node-forge 0.8.5 fixed in 1.3.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33891 | MEDIUM6.38 | node-forge 0.8.5 fixed in 1.4.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-33894 | MEDIUM6.38 | node-forge 0.8.5 fixed in 1.4.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33895 | MEDIUM6.38 | node-forge 0.8.5 fixed in 1.4.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-85393 | MEDIUM6.38 | node-forge 0.8.5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44289 | MEDIUM6.38 | protobufjs 6.11.2 fixed in 7.5.6, 8.0.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-44290 | MEDIUM6.38 | protobufjs 6.11.2 fixed in 7.5.6, 8.0.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48712 | MEDIUM6.38 | protobufjs 6.11.2 fixed in 7.6.1, 8.4.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44292 | MEDIUM6.38 | protobufjs 6.11.2 fixed in 7.5.6, 8.0.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45740 | MEDIUM6.38 | protobufjs 6.11.2 fixed in 7.5.8, 8.2.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-90711 | MEDIUM6.38 | proxy-addr 2.0.6 fixed in 2.0.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15284 | MEDIUM6.38 | qs 6.10.1 fixed in 6.14.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-82417 | MEDIUM6.38 | qs 6.10.1 fixed in 6.16.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2391 | MEDIUM6.38 | qs 6.10.1 fixed in 6.14.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15284 | MEDIUM6.38 | qs 6.5.2 fixed in 6.14.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-82417 | MEDIUM6.38 | qs 6.5.2 fixed in 6.16.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15284 | MEDIUM6.38 | qs 6.7.0 fixed in 6.14.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-82417 | MEDIUM6.38 | qs 6.7.0 fixed in 6.16.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2391 | MEDIUM6.38 | qs 6.7.0 fixed in 6.14.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-59343 | MEDIUM6.38 | tar-fs 2.0.1 fixed in 3.1.1, 2.1.4, 1.16.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-59343 | MEDIUM6.38 | tar-fs 2.1.1 fixed in 3.1.1, 2.1.4, 1.16.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-41907 | MEDIUM6.38 | uuid 3.3.2 fixed in 11.1.1, 12.0.1, 13.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41907 | MEDIUM6.38 | uuid 3.3.3 fixed in 11.1.1, 12.0.1, 13.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41907 | MEDIUM6.38 | uuid 3.4.0 fixed in 11.1.1, 12.0.1, 13.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41907 | MEDIUM6.38 | uuid 7.0.3 fixed in 11.1.1, 12.0.1, 13.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41907 | MEDIUM6.38 | uuid 8.3.2 fixed in 11.1.1, 12.0.1, 13.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48779 | MEDIUM6.38 | ws 7.5.0 fixed in 5.2.5, 6.2.4, 7.5.11, 8.21.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-34601 | MEDIUM6.38 | xmldom 0.1.27 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-41672 | MEDIUM6.38 | xmldom 0.1.27 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-41673 | MEDIUM6.38 | xmldom 0.1.27 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-41674 | MEDIUM6.38 | xmldom 0.1.27 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-41675 | MEDIUM6.38 | xmldom 0.1.27 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83613 | MEDIUM6.38 | xmldom 0.1.27 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83615 | MEDIUM6.38 | xmldom 0.1.27 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83616 | MEDIUM6.38 | xmldom 0.1.27 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34601 | MEDIUM6.38 | xmldom 0.1.31 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-41672 | MEDIUM6.38 | xmldom 0.1.31 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-41673 | MEDIUM6.38 | xmldom 0.1.31 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-41674 | MEDIUM6.38 | xmldom 0.1.31 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-41675 | MEDIUM6.38 | xmldom 0.1.31 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83613 | MEDIUM6.38 | xmldom 0.1.31 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83615 | MEDIUM6.38 | xmldom 0.1.31 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83616 | MEDIUM6.38 | xmldom 0.1.31 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34601 | MEDIUM6.38 | xmldom 0.4.0 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-41672 | MEDIUM6.38 | xmldom 0.4.0 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-41673 | MEDIUM6.38 | xmldom 0.4.0 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-41674 | MEDIUM6.38 | xmldom 0.4.0 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-41675 | MEDIUM6.38 | xmldom 0.4.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83613 | MEDIUM6.38 | xmldom 0.4.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83614 | MEDIUM6.38 | xmldom 0.4.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83615 | MEDIUM6.38 | xmldom 0.4.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83616 | MEDIUM6.38 | xmldom 0.4.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34601 | MEDIUM6.38 | xmldom 0.6.0 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-41672 | MEDIUM6.38 | xmldom 0.6.0 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-41673 | MEDIUM6.38 | xmldom 0.6.0 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-41674 | MEDIUM6.38 | xmldom 0.6.0 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-41675 | MEDIUM6.38 | xmldom 0.6.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83613 | MEDIUM6.38 | xmldom 0.6.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83614 | MEDIUM6.38 | xmldom 0.6.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83615 | MEDIUM6.38 | xmldom 0.6.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83616 | MEDIUM6.38 | xmldom 0.6.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | Markdown 3.3.4 fixed in 3.8.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-23491 | MEDIUM6.38 | certifi 2021.5.30 fixed in 2022.12.07 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59939 | MEDIUM6.38 | httplib2 0.19.1 fixed in 0.32.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-67422 | MEDIUM6.38 | pymdown-extensions 7.1 fixed in 11.0.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-66418 | MEDIUM6.38 | urllib3 1.26.6 fixed in 2.6.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-66471 | MEDIUM6.38 | urllib3 1.26.6 fixed in 2.6.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-101916 | MEDIUM6.29 | @grpc/grpc-js 1.3.2 fixed in 1.13.6, 1.14.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42033 | MEDIUM6.29 | axios 0.21.1 fixed in 1.15.1, 0.31.1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-42035 | MEDIUM6.29 | axios 0.21.1 fixed in 1.15.1, 0.31.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-67316 | MEDIUM6.29 | axios 0.21.1 fixed in 1.18.0, 0.33.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-54419 | MEDIUM6.29 | passport-saml 2.0.5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0624 | MEDIUM6.21 | parse-path 4.0.1 fixed in 5.0.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-48387 | MEDIUM6.21 | tar-fs 2.0.1 fixed in 1.16.5, 2.1.3, 3.0.9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-48387 | MEDIUM6.21 | tar-fs 2.1.1 fixed in 1.16.5, 2.1.3, 3.0.9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-23521 | MEDIUM6.11 | git 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u7 | 56.3% Actively Exploited | Post-ExploitContext importance: MEDIUM |
| CVE-2023-28370 | MEDIUM6.1 | python3-tornado 5.1.1-4 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0235 | MEDIUM6.1 | node-fetch 2.6.1 fixed in 3.1.1, 2.6.7 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2217 | MEDIUM6.1 | parse-url 5.0.1 fixed in 6.0.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23647 | MEDIUM6.1 | prismjs 1.23.0 fixed in 1.27.0 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-32681 | MEDIUM6.1 | requests 2.26.0 fixed in 2.31.0 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-22939 | MEDIUM6.09 | libnode64 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u2 | 14.7% High Exploitation Risk | Directly Exposed |
| CVE-2021-44532 | MEDIUM6.09 | libnode64 10.24.0~dfsg-1~deb10u1 No fix yet | 10.4% High Exploitation Risk | Directly Exposed |
| CVE-2021-22939 | MEDIUM6.09 | nodejs 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u2 | 14.7% High Exploitation Risk | Directly Exposed |
| CVE-2021-44532 | MEDIUM6.09 | nodejs 10.24.0~dfsg-1~deb10u1 No fix yet | 10.4% High Exploitation Risk | Directly Exposed |
| CVE-2022-0144 | MEDIUM6.03 | shelljs 0.8.4 fixed in 0.8.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-1751 | MEDIUM5.95 | libc-bin 2.28-10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-1752 | MEDIUM5.95 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-1751 | MEDIUM5.95 | libc-dev-bin 2.28-10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-1752 | MEDIUM5.95 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-1751 | MEDIUM5.95 | libc6 2.28-10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-1752 | MEDIUM5.95 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-1751 | MEDIUM5.95 | libc6-dev 2.28-10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-1752 | MEDIUM5.95 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2016-10228 | MEDIUM5.9 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-25013 | MEDIUM5.9 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc-bin 2.28-10 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc-bin 2.28-10 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2016-10228 | MEDIUM5.9 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-25013 | MEDIUM5.9 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc-dev-bin 2.28-10 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc-dev-bin 2.28-10 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2016-10228 | MEDIUM5.9 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-25013 | MEDIUM5.9 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc6 2.28-10 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc6 2.28-10 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2016-10228 | MEDIUM5.9 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-25013 | MEDIUM5.9 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc6-dev 2.28-10 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc6-dev 2.28-10 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5981 | MEDIUM5.9 | libgnutls-dane0 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u11 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5981 | MEDIUM5.9 | libgnutls-openssl27 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u11 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5981 | MEDIUM5.9 | libgnutls28-dev 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u11 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5981 | MEDIUM5.9 | libgnutls30 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u11 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5981 | MEDIUM5.9 | libgnutlsxx28 3.6.7-4+deb10u7 fixed in 3.6.7-4+deb10u11 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-46809 | MEDIUM5.9 | libnode64 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-23222 | MEDIUM5.9 | libpq-dev 11.12-0+deb10u1 fixed in 11.14-0+deb10u1 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-23222 | MEDIUM5.9 | libpq5 11.12-0+deb10u1 fixed in 11.14-0+deb10u1 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48566 | MEDIUM5.9 | libpython2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48566 | MEDIUM5.9 | libpython2.7-stdlib 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48566 | MEDIUM5.9 | libpython3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u6 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48566 | MEDIUM5.9 | libpython3.7-stdlib 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u6 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-4160 | MEDIUM5.9 | libssl1.1 1.1.1d-0+deb10u6 fixed in 1.1.1d-0+deb10u8 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-46809 | MEDIUM5.9 | nodejs 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48566 | MEDIUM5.9 | python3.7 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u6 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48566 | MEDIUM5.9 | python3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u6 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0536 | MEDIUM5.9 | follow-redirects 1.13.0 fixed in 1.14.8 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28176 | MEDIUM5.9 | jose 1.28.1 fixed in 4.15.5, 2.0.7 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28176 | MEDIUM5.9 | jose 2.0.5 fixed in 4.15.5, 2.0.7 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37890 | MEDIUM5.9 | ws 7.5.0 fixed in 5.2.4, 6.2.3, 7.5.10, 8.17.1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-32221 | MEDIUM5.88 | libcurl3-gnutls 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u4 | 4.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-32221 | MEDIUM5.88 | libcurl4 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u4 | 4.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-32221 | MEDIUM5.88 | libcurl4-openssl-dev 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u4 | 4.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48565 | MEDIUM5.88 | python2.7 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 5.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48565 | MEDIUM5.88 | python2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 5.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-21300 | MEDIUM5.85 | git 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u4 | 88.5% Actively Exploited | Post-Exploit |
| CVE-2023-25652 | MEDIUM5.85 | git 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u9 | 51.9% Actively Exploited | Post-Exploit |
| CVE-2022-0778 | MEDIUM5.85 | openssl 1.1.1d-0+deb10u6 fixed in 1.1.1d-0+deb10u8 | 73.2% Actively Exploited | Post-Exploit |
| CVE-2021-3712 | MEDIUM5.77 | openssl 1.1.1d-0+deb10u6 fixed in 1.1.1d-0+deb10u7 | 50.4% Actively Exploited | Post-Exploit |
| CVE-2023-0286 | MEDIUM5.77 | openssl 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u4 | 59.5% Actively Exploited | Post-Exploit |
| CVE-2021-3426 | MEDIUM5.7 | libpython3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3426 | MEDIUM5.7 | libpython3.7-stdlib 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3426 | MEDIUM5.7 | python3.7 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3426 | MEDIUM5.7 | python3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1292 | MEDIUM5.69 | openssl 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u2 | 82.6% Actively Exploited | Post-Exploit |
| CVE-2022-2068 | MEDIUM5.69 | openssl 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u3 | 95.4% Actively Exploited | Post-Exploit |
| CVE-2021-3672 | MEDIUM5.6 | libc-ares2 1.14.0-1 fixed in 1.14.0-1+deb10u1 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | libssl1.1 1.1.1d-0+deb10u6 No fix yet | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2020-7598 | MEDIUM5.6 | minimist 0.0.8 fixed in 0.2.1, 1.2.3 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2019-13115 | MEDIUM5.59 | libssh2-1 1.8.0-2.1 fixed in 1.8.0-2.1+deb10u1 | 11.7% High Exploitation Risk | Post-Exploit |
| CVE-2021-32804 | MEDIUM5.59 | tar 2.2.2 fixed in 3.2.2, 4.4.14, 5.0.6, 6.1.1 | 15.1% High Exploitation Risk | Post-Exploit |
| CVE-2021-32804 | MEDIUM5.59 | tar 4.4.13 fixed in 3.2.2, 4.4.14, 5.0.6, 6.1.1 | 15.1% High Exploitation Risk | Post-Exploit |
| CVE-2022-43235 | MEDIUM5.52 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-43236 | MEDIUM5.52 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-43237 | MEDIUM5.52 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-43238 | MEDIUM5.52 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-43239 | MEDIUM5.52 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-43240 | MEDIUM5.52 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-43241 | MEDIUM5.52 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-43242 | MEDIUM5.52 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-43243 | MEDIUM5.52 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-43244 | MEDIUM5.52 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-43245 | MEDIUM5.52 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-43248 | MEDIUM5.52 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-43249 | MEDIUM5.52 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-43250 | MEDIUM5.52 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-43252 | MEDIUM5.52 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-43253 | MEDIUM5.52 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-24751 | MEDIUM5.52 | libde265-0 1.0.3-1+b1 fixed in 1.0.11-0+deb10u4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-27102 | MEDIUM5.52 | libde265-0 1.0.3-1+b1 fixed in 1.0.11-0+deb10u5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-47471 | MEDIUM5.52 | libde265-0 1.0.3-1+b1 fixed in 1.0.11-0+deb10u5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-29659 | MEDIUM5.52 | libheif1 1.3.2-2~deb10u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-3941 | MEDIUM5.52 | libopenexr-dev 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-3941 | MEDIUM5.52 | libopenexr23 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-40090 | MEDIUM5.52 | libtiff5 4.1.0+git191117-2~deb10u2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-40090 | MEDIUM5.52 | libtiffxx5 4.1.0+git191117-2~deb10u2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-28484 | MEDIUM5.52 | libxml2 2.9.4+dfsg1-7+deb10u2 fixed in 2.9.4+dfsg1-7+deb10u6 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-39615 | MEDIUM5.52 | libxml2 2.9.4+dfsg1-7+deb10u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-45322 | MEDIUM5.52 | libxml2 2.9.4+dfsg1-7+deb10u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-28484 | MEDIUM5.52 | libxml2-dev 2.9.4+dfsg1-7+deb10u2 fixed in 2.9.4+dfsg1-7+deb10u6 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-39615 | MEDIUM5.52 | libxml2-dev 2.9.4+dfsg1-7+deb10u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-45322 | MEDIUM5.52 | libxml2-dev 2.9.4+dfsg1-7+deb10u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-45815 | MEDIUM5.52 | @backstage/plugin-catalog-backend 0.13.1 fixed in 1.26.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-29184 | MEDIUM5.52 | @backstage/plugin-scaffolder-backend 0.14.2 fixed in 3.1.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-45816 | MEDIUM5.52 | @backstage/plugin-techdocs-backend 0.9.1 fixed in 1.10.13 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-45857 | MEDIUM5.52 | axios 0.21.1 fixed in 1.6.0, 0.28.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42041 | MEDIUM5.52 | axios 0.21.1 fixed in 1.15.1, 0.31.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-27904 | MEDIUM5.52 | minimatch 0.3.0 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27904 | MEDIUM5.52 | minimatch 3.0.4 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33671 | MEDIUM5.52 | picomatch 2.2.2 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33532 | MEDIUM5.52 | yaml 1.10.2 fixed in 2.8.3, 1.10.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-25665 | MEDIUM5.5 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25674 | MEDIUM5.5 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25676 | MEDIUM5.5 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27760 | MEDIUM5.5 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27762 | MEDIUM5.5 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27770 | MEDIUM5.5 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20241 | MEDIUM5.5 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20243 | MEDIUM5.5 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20244 | MEDIUM5.5 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20245 | MEDIUM5.5 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20246 | MEDIUM5.5 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25665 | MEDIUM5.5 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25674 | MEDIUM5.5 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25676 | MEDIUM5.5 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27760 | MEDIUM5.5 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27762 | MEDIUM5.5 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27770 | MEDIUM5.5 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20241 | MEDIUM5.5 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20243 | MEDIUM5.5 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20244 | MEDIUM5.5 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20245 | MEDIUM5.5 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20246 | MEDIUM5.5 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25665 | MEDIUM5.5 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25674 | MEDIUM5.5 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25676 | MEDIUM5.5 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27760 | MEDIUM5.5 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27762 | MEDIUM5.5 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27770 | MEDIUM5.5 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20241 | MEDIUM5.5 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20243 | MEDIUM5.5 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20244 | MEDIUM5.5 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20245 | MEDIUM5.5 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20246 | MEDIUM5.5 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo-gobject2 1.16.0-4+deb10u1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo-script-interpreter2 1.16.0-4+deb10u1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo2 1.16.0-4+deb10u1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-36411 | MEDIUM5.5 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15142 | MEDIUM5.5 | libdjvulibre-dev 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15143 | MEDIUM5.5 | libdjvulibre-dev 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15144 | MEDIUM5.5 | libdjvulibre-dev 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15145 | MEDIUM5.5 | libdjvulibre-dev 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3630 | MEDIUM5.5 | libdjvulibre-dev 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15142 | MEDIUM5.5 | libdjvulibre-text 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15143 | MEDIUM5.5 | libdjvulibre-text 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15144 | MEDIUM5.5 | libdjvulibre-text 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15145 | MEDIUM5.5 | libdjvulibre-text 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3630 | MEDIUM5.5 | libdjvulibre-text 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15142 | MEDIUM5.5 | libdjvulibre21 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15143 | MEDIUM5.5 | libdjvulibre21 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15144 | MEDIUM5.5 | libdjvulibre21 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15145 | MEDIUM5.5 | libdjvulibre21 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3630 | MEDIUM5.5 | libdjvulibre21 3.5.27.1-10 fixed in 3.5.27.1-10+deb10u1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-33068 | MEDIUM5.5 | libharfbuzz0b 2.3.1-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-21913 | MEDIUM5.5 | libicu-dev 63.1-6+deb10u1 fixed in 63.1-6+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-21913 | MEDIUM5.5 | libicu63 63.1-6+deb10u1 fixed in 63.1-6+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-46822 | MEDIUM5.5 | libjpeg-dev 1:1.5.2-2+deb10u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-46822 | MEDIUM5.5 | libjpeg62-turbo 1:1.5.2-2+deb10u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-46822 | MEDIUM5.5 | libjpeg62-turbo-dev 1:1.5.2-2+deb10u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25665 | MEDIUM5.5 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25674 | MEDIUM5.5 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25676 | MEDIUM5.5 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27760 | MEDIUM5.5 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27762 | MEDIUM5.5 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27770 | MEDIUM5.5 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20241 | MEDIUM5.5 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20243 | MEDIUM5.5 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20244 | MEDIUM5.5 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20245 | MEDIUM5.5 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20246 | MEDIUM5.5 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25665 | MEDIUM5.5 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25674 | MEDIUM5.5 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25676 | MEDIUM5.5 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27760 | MEDIUM5.5 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27762 | MEDIUM5.5 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27770 | MEDIUM5.5 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20241 | MEDIUM5.5 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20243 | MEDIUM5.5 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20244 | MEDIUM5.5 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20245 | MEDIUM5.5 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20246 | MEDIUM5.5 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25665 | MEDIUM5.5 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25674 | MEDIUM5.5 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25676 | MEDIUM5.5 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27760 | MEDIUM5.5 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27762 | MEDIUM5.5 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27770 | MEDIUM5.5 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20241 | MEDIUM5.5 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20243 | MEDIUM5.5 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20244 | MEDIUM5.5 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20245 | MEDIUM5.5 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20246 | MEDIUM5.5 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25665 | MEDIUM5.5 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25674 | MEDIUM5.5 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25676 | MEDIUM5.5 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27760 | MEDIUM5.5 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27762 | MEDIUM5.5 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27770 | MEDIUM5.5 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20241 | MEDIUM5.5 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20243 | MEDIUM5.5 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20244 | MEDIUM5.5 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20245 | MEDIUM5.5 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20246 | MEDIUM5.5 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25665 | MEDIUM5.5 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25674 | MEDIUM5.5 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25676 | MEDIUM5.5 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27760 | MEDIUM5.5 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27762 | MEDIUM5.5 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27770 | MEDIUM5.5 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20241 | MEDIUM5.5 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20243 | MEDIUM5.5 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20244 | MEDIUM5.5 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20245 | MEDIUM5.5 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20246 | MEDIUM5.5 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25665 | MEDIUM5.5 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25674 | MEDIUM5.5 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25676 | MEDIUM5.5 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27760 | MEDIUM5.5 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27762 | MEDIUM5.5 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27770 | MEDIUM5.5 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20241 | MEDIUM5.5 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20243 | MEDIUM5.5 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20244 | MEDIUM5.5 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20245 | MEDIUM5.5 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20246 | MEDIUM5.5 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35604 | MEDIUM5.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-16587 | MEDIUM5.5 | libopenexr-dev 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-16588 | MEDIUM5.5 | libopenexr-dev 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-16589 | MEDIUM5.5 | libopenexr-dev 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-23215 | MEDIUM5.5 | libopenexr-dev 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-26260 | MEDIUM5.5 | libopenexr-dev 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3605 | MEDIUM5.5 | libopenexr-dev 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-45942 | MEDIUM5.5 | libopenexr-dev 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2020-16587 | MEDIUM5.5 | libopenexr23 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-16588 | MEDIUM5.5 | libopenexr23 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-16589 | MEDIUM5.5 | libopenexr23 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-23215 | MEDIUM5.5 | libopenexr23 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-26260 | MEDIUM5.5 | libopenexr23 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3605 | MEDIUM5.5 | libopenexr23 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-45942 | MEDIUM5.5 | libopenexr23 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12973 | MEDIUM5.5 | libopenjp2-7 2.3.0-2+deb10u2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-29338 | MEDIUM5.5 | libopenjp2-7 2.3.0-2+deb10u2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1122 | MEDIUM5.5 | libopenjp2-7 2.3.0-2+deb10u2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12973 | MEDIUM5.5 | libopenjp2-7-dev 2.3.0-2+deb10u2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-29338 | MEDIUM5.5 | libopenjp2-7-dev 2.3.0-2+deb10u2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1122 | MEDIUM5.5 | libopenjp2-7-dev 2.3.0-2+deb10u2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libssl1.1 1.1.1d-0+deb10u6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3997 | MEDIUM5.5 | libsystemd0 241-7~deb10u8 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0561 | MEDIUM5.5 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0562 | MEDIUM5.5 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0907 | MEDIUM5.5 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0908 | MEDIUM5.5 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0909 | MEDIUM5.5 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0924 | MEDIUM5.5 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-22844 | MEDIUM5.5 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0561 | MEDIUM5.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0562 | MEDIUM5.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0907 | MEDIUM5.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0908 | MEDIUM5.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0909 | MEDIUM5.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0924 | MEDIUM5.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-22844 | MEDIUM5.5 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3997 | MEDIUM5.5 | libudev1 241-7~deb10u8 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9318 | MEDIUM5.5 | libxml2 2.9.4+dfsg1-7+deb10u2 No fix yet | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9318 | MEDIUM5.5 | libxml2-dev 2.9.4+dfsg1-7+deb10u2 No fix yet | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35604 | MEDIUM5.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-31130 | MEDIUM5.44 | libc-ares2 1.14.0-1 fixed in 1.14.0-1+deb10u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-41903 | MEDIUM5.41 | git 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u7 | 44.3% High Exploitation Risk | Post-ExploitContext importance: MEDIUM |
| CVE-2025-7783 | MEDIUM5.4 | form-data 2.3.2 fixed in 2.5.4, 3.0.4, 4.0.4 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-7783 | MEDIUM5.4 | form-data 2.3.3 fixed in 2.5.4, 3.0.4, 4.0.4 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-7783 | MEDIUM5.4 | form-data 2.5.1 fixed in 2.5.4, 3.0.4, 4.0.4 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-7783 | MEDIUM5.4 | form-data 3.0.0 fixed in 2.5.4, 3.0.4, 4.0.4 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-7783 | MEDIUM5.4 | form-data 4.0.0 fixed in 2.5.4, 3.0.4, 4.0.4 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-13627 | MEDIUM5.35 | libgcrypt20 1.8.4-5+deb10u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-24047 | MEDIUM5.35 | @backstage/cli-common 0.1.2 fixed in 0.1.17 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-23541 | MEDIUM5.35 | jsonwebtoken 8.5.1 fixed in 9.0.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-56326 | MEDIUM5.35 | Jinja2 3.0.1 fixed in 3.1.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc-bin 2.28-10 fixed in 2.28-10+deb10u4 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u4 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc6 2.28-10 fixed in 2.28-10+deb10u4 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u4 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44533 | MEDIUM5.3 | libnode64 10.24.0~dfsg-1~deb10u1 No fix yet | 9.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20296 | MEDIUM5.3 | libopenexr-dev 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3474 | MEDIUM5.3 | libopenexr-dev 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3475 | MEDIUM5.3 | libopenexr-dev 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3476 | MEDIUM5.3 | libopenexr-dev 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20296 | MEDIUM5.3 | libopenexr23 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3474 | MEDIUM5.3 | libopenexr23 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3475 | MEDIUM5.3 | libopenexr23 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3476 | MEDIUM5.3 | libopenexr23 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14155 | MEDIUM5.3 | libpcre16-3 2:8.39-12 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14155 | MEDIUM5.3 | libpcre3 2:8.39-12 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14155 | MEDIUM5.3 | libpcre3-dev 2:8.39-12 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14155 | MEDIUM5.3 | libpcre32-3 2:8.39-12 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14155 | MEDIUM5.3 | libpcrecpp0v5 2:8.39-12 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-4189 | MEDIUM5.3 | libpython2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-27043 | MEDIUM5.3 | libpython2.7-minimal 2.7.16-2+deb10u1 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-4189 | MEDIUM5.3 | libpython2.7-stdlib 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-27043 | MEDIUM5.3 | libpython2.7-stdlib 2.7.16-2+deb10u1 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-4189 | MEDIUM5.3 | libpython3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-27043 | MEDIUM5.3 | libpython3.7-minimal 3.7.3-2+deb10u3 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-4189 | MEDIUM5.3 | libpython3.7-stdlib 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-27043 | MEDIUM5.3 | libpython3.7-stdlib 3.7.3-2+deb10u3 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19924 | MEDIUM5.3 | libsqlite3-0 3.27.2-3+deb10u1 No fix yet | 7.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2097 | MEDIUM5.3 | libssl1.1 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u4 | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0465 | MEDIUM5.3 | libssl1.1 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u5 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0466 | MEDIUM5.3 | libssl1.1 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u5 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3446 | MEDIUM5.3 | libssl1.1 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u6 | 6.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3817 | MEDIUM5.3 | libssl1.1 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u6 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | libssl1.1 1.1.1d-0+deb10u6 No fix yet | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-44533 | MEDIUM5.3 | nodejs 10.24.0~dfsg-1~deb10u1 No fix yet | 9.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-28493 | MEDIUM5.3 | python3-jinja2 2.10-2 No fix yet | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-4189 | MEDIUM5.3 | python3.7 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-27043 | MEDIUM5.3 | python3.7 3.7.3-2+deb10u3 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-4189 | MEDIUM5.3 | python3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u5 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-27043 | MEDIUM5.3 | python3.7-minimal 3.7.3-2+deb10u3 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-106502 | MEDIUM5.3 | @backstage/plugin-scaffolder-backend 0.14.2 fixed in 4.1.0 | — | Directly Exposed |
| CVE-2021-29060 | MEDIUM5.3 | color-string 1.5.4 fixed in 1.5.5 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16137 | MEDIUM5.3 | debug 2.2.0 fixed in 2.6.9, 3.1.0, 3.2.7, 4.3.1 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16137 | MEDIUM5.3 | debug 3.2.6 fixed in 2.6.9, 3.1.0, 3.2.7, 4.3.1 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-33987 | MEDIUM5.3 | got 11.8.2 fixed in 12.1.0, 11.8.5 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-33987 | MEDIUM5.3 | got 6.7.1 fixed in 12.1.0, 11.8.5 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-36083 | MEDIUM5.3 | jose 1.28.1 fixed in 1.28.2, 2.0.6, 3.20.4, 4.9.2 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-36083 | MEDIUM5.3 | jose 2.0.5 fixed in 1.28.2, 2.0.6, 3.20.4, 4.9.2 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-28500 | MEDIUM5.3 | lodash 4.17.15 fixed in 4.17.21 | 7.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13465 | MEDIUM5.3 | lodash 4.17.15 fixed in 4.17.23 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13465 | MEDIUM5.3 | lodash 4.17.21 fixed in 4.17.23 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2020-28500 | MEDIUM5.3 | lodash-es 4.17.15 fixed in 4.17.21 | 7.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13465 | MEDIUM5.3 | lodash-es 4.17.15 fixed in 4.17.23 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4067 | MEDIUM5.3 | micromatch 4.0.2 fixed in 4.0.8 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-41580 | MEDIUM5.3 | passport-oauth2 1.2.0 fixed in 1.6.1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-41580 | MEDIUM5.3 | passport-oauth2 1.6.0 fixed in 1.6.1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0842 | MEDIUM5.3 | xml2js 0.4.19 fixed in 0.5.0 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0842 | MEDIUM5.3 | xml2js 0.4.23 fixed in 0.5.0 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-32796 | MEDIUM5.3 | xmldom 0.1.27 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-32796 | MEDIUM5.3 | xmldom 0.1.31 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-32796 | MEDIUM5.3 | xmldom 0.4.0 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-32796 | MEDIUM5.3 | xmldom 0.6.0 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-27533 | MEDIUM5.28 | curl 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u6 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27534 | MEDIUM5.28 | curl 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u9 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1387 | MEDIUM5.28 | git 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u9 | 4.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-39260 | MEDIUM5.28 | git 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u5 | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1271 | MEDIUM5.28 | gzip 1.9-3 fixed in 1.9-3+deb10u1 | 5.1% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27533 | MEDIUM5.28 | libcurl3-gnutls 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u6 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27534 | MEDIUM5.28 | libcurl3-gnutls 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u9 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27533 | MEDIUM5.28 | libcurl4 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u6 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27534 | MEDIUM5.28 | libcurl4 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u9 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27533 | MEDIUM5.28 | libcurl4-openssl-dev 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u6 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27534 | MEDIUM5.28 | libcurl4-openssl-dev 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u9 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1271 | MEDIUM5.28 | xz-utils 5.2.4-1 fixed in 5.2.4-1+deb10u1 | 5.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6345 | MEDIUM5.28 | setuptools 41.2.0 fixed in 70.0.0 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-47273 | MEDIUM5.28 | setuptools 41.2.0 fixed in 78.1.1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-0450 | MEDIUM5.27 | libpython2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-0450 | MEDIUM5.27 | libpython2.7-stdlib 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-0450 | MEDIUM5.27 | libpython3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-0450 | MEDIUM5.27 | libpython3.7-stdlib 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-0450 | MEDIUM5.27 | python3.7 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-0450 | MEDIUM5.27 | python3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-5569 | MEDIUM5.27 | zipp 3.5.0 fixed in 3.19.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2020-25664 | MEDIUM5.18 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2020-25664 | MEDIUM5.18 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2020-25664 | MEDIUM5.18 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2020-25664 | MEDIUM5.18 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2020-25664 | MEDIUM5.18 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2020-25664 | MEDIUM5.18 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2020-25664 | MEDIUM5.18 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2020-25664 | MEDIUM5.18 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2020-25664 | MEDIUM5.18 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-20303 | MEDIUM5.18 | libopenexr-dev 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-20303 | MEDIUM5.18 | libopenexr23 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-1355 | MEDIUM5.18 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-1355 | MEDIUM5.18 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2016-3709 | MEDIUM5.18 | libxml2 2.9.4+dfsg1-7+deb10u2 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2016-3709 | MEDIUM5.18 | libxml2-dev 2.9.4+dfsg1-7+deb10u2 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-22195 | MEDIUM5.18 | python3-jinja2 2.10-2 fixed in 2.10-2+deb10u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-43776 | MEDIUM5.18 | @backstage/plugin-auth-backend 0.3.19 fixed in 0.4.9 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42042 | MEDIUM5.18 | axios 0.21.1 fixed in 1.15.1, 0.31.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-29041 | MEDIUM5.18 | express 4.17.1 fixed in 4.19.2, 5.0.0-beta.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-26159 | MEDIUM5.18 | follow-redirects 1.13.0 fixed in 1.15.4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-0122 | MEDIUM5.18 | node-forge 0.10.0 fixed in 1.0.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-0122 | MEDIUM5.18 | node-forge 0.8.5 fixed in 1.0.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-2218 | MEDIUM5.18 | parse-url 5.0.1 fixed in 6.0.1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-3224 | MEDIUM5.18 | parse-url 5.0.1 fixed in 8.1.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-28155 | MEDIUM5.18 | request 2.88.0 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-28155 | MEDIUM5.18 | request 2.88.2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-22195 | MEDIUM5.18 | Jinja2 3.0.1 fixed in 3.1.3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-50181 | MEDIUM5.18 | urllib3 1.26.6 fixed in 2.5.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-2398 | MEDIUM5.17 | curl 7.64.0-4+deb10u2 No fix yet | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2024-2398 | MEDIUM5.17 | libcurl3-gnutls 7.64.0-4+deb10u2 No fix yet | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2024-2398 | MEDIUM5.17 | libcurl4 7.64.0-4+deb10u2 No fix yet | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2024-2398 | MEDIUM5.17 | libcurl4-openssl-dev 7.64.0-4+deb10u2 No fix yet | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2022-4450 | MEDIUM5.17 | openssl 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u4 | 20.4% High Exploitation Risk | Post-Exploit |
| CVE-2021-3737 | MEDIUM5.17 | python2.7 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 11.6% High Exploitation Risk | Post-Exploit |
| CVE-2023-24329 | MEDIUM5.17 | python2.7 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 20.5% High Exploitation Risk | Post-Exploit |
| CVE-2021-3737 | MEDIUM5.17 | python2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 11.6% High Exploitation Risk | Post-Exploit |
| CVE-2023-24329 | MEDIUM5.17 | python2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 20.5% High Exploitation Risk | Post-Exploit |
| CVE-2021-37713 | MEDIUM5.16 | tar 2.2.2 fixed in 4.4.18, 5.0.10, 6.1.9 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2021-37701 | MEDIUM5.16 | tar 4.4.13 fixed in 4.4.16, 5.0.8, 6.1.7 | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2021-37712 | MEDIUM5.16 | tar 4.4.13 fixed in 4.4.18, 5.0.10, 6.1.9 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-37713 | MEDIUM5.16 | tar 4.4.13 fixed in 4.4.18, 5.0.10, 6.1.9 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2021-37701 | MEDIUM5.16 | tar 4.4.15 fixed in 4.4.16, 5.0.8, 6.1.7 | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2021-37712 | MEDIUM5.16 | tar 4.4.15 fixed in 4.4.18, 5.0.10, 6.1.9 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-37713 | MEDIUM5.16 | tar 4.4.15 fixed in 4.4.18, 5.0.10, 6.1.9 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2021-37701 | MEDIUM5.16 | tar 6.1.2 fixed in 4.4.16, 5.0.8, 6.1.7 | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2021-37712 | MEDIUM5.16 | tar 6.1.2 fixed in 4.4.18, 5.0.10, 6.1.9 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-37713 | MEDIUM5.16 | tar 6.1.2 fixed in 4.4.18, 5.0.10, 6.1.9 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-2650 | MEDIUM5.07 | openssl 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u5 | 75.1% Actively Exploited | Post-Exploit |
| CVE-2020-22217 | MEDIUM5.02 | libc-ares2 1.14.0-1 fixed in 1.14.0-1+deb10u4 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-7008 | MEDIUM5.02 | libsystemd0 241-7~deb10u8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-7008 | MEDIUM5.02 | libudev1 241-7~deb10u8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-12590 | MEDIUM5.02 | body-parser 1.19.0 fixed in 1.20.6, 2.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27903 | MEDIUM5.02 | minimatch 0.3.0 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-27903 | MEDIUM5.02 | minimatch 3.0.4 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-27601 | MEDIUM5.02 | underscore 1.13.1 fixed in 1.13.8 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-32002 | MEDIUM4.97 | git 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u9 | 29.2% High Exploitation Risk | Post-ExploitContext importance: MEDIUM |
| CVE-2024-47762 | MEDIUM4.93 | @backstage/plugin-app-backend 0.3.15 fixed in 0.3.75 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-22084 | MEDIUM4.9 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.39-0+deb10u2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-22084 | MEDIUM4.9 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.39-0+deb10u2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-41151 | MEDIUM4.9 | @backstage/plugin-scaffolder-backend 0.14.2 fixed in 0.15.9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-106499 | MEDIUM4.9 | @backstage/plugin-scaffolder-backend 0.14.2 fixed in 4.1.0 | — | Directly Exposed |
| CVE-2018-12886 | MEDIUM4.86 | cpp-8 8.3.0-6 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-22576 | MEDIUM4.86 | curl 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2018-12886 | MEDIUM4.86 | g++-8 8.3.0-6 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2018-12886 | MEDIUM4.86 | gcc-8 8.3.0-6 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-22576 | MEDIUM4.86 | libcurl3-gnutls 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-22576 | MEDIUM4.86 | libcurl4 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-22576 | MEDIUM4.86 | libcurl4-openssl-dev 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-17498 | MEDIUM4.86 | libssh2-1 1.8.0-2.1 fixed in 1.8.0-2.1+deb10u1 | 3.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31484 | MEDIUM4.86 | perl 5.28.1-6+deb10u1 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31484 | MEDIUM4.86 | perl-base 5.28.1-6+deb10u1 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-32803 | MEDIUM4.86 | tar 4.4.13 fixed in 3.2.3, 4.4.15, 5.0.7, 6.1.2 | 7.8% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2511 | MEDIUM4.81 | libssl1.1 1.1.1d-0+deb10u6 No fix yet | 52.4% Actively Exploited | Directly Exposed |
| CVE-2026-40175 | MEDIUM4.8 | axios 0.21.1 fixed in 1.15.0, 0.31.0 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25896 | MEDIUM4.8 | passport 0.4.1 fixed in 0.6.0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-35195 | MEDIUM4.76 | requests 2.26.0 fixed in 2.32.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-106444 | MEDIUM4.7 | handlebars 4.7.7 fixed in 4.7.10 | — | Directly Exposed |
| CVE-2022-1304 | MEDIUM4.68 | e2fsprogs 1.44.5-1+deb10u3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-24765 | MEDIUM4.68 | git 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u5 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-29007 | MEDIUM4.68 | git 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u9 | 6.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-32004 | MEDIUM4.68 | git 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u9 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-32465 | MEDIUM4.68 | git 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u9 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2020-27750 | MEDIUM4.67 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2020-27756 | MEDIUM4.67 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-20176 | MEDIUM4.67 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-20224 | MEDIUM4.67 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-1289 | MEDIUM4.67 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-34151 | MEDIUM4.67 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-5341 | MEDIUM4.67 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-27750 | MEDIUM4.67 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2020-27756 | MEDIUM4.67 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-20176 | MEDIUM4.67 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-20224 | MEDIUM4.67 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-1289 | MEDIUM4.67 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-34151 | MEDIUM4.67 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-5341 | MEDIUM4.67 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-27750 | MEDIUM4.67 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2020-27756 | MEDIUM4.67 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-20176 | MEDIUM4.67 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-20224 | MEDIUM4.67 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-1289 | MEDIUM4.67 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-34151 | MEDIUM4.67 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-5341 | MEDIUM4.67 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-37600 | MEDIUM4.67 | libblkid-dev 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-37600 | MEDIUM4.67 | libblkid1 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-25629 | MEDIUM4.67 | libc-ares2 1.14.0-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-10029 | MEDIUM4.67 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2020-27618 | MEDIUM4.67 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-10029 | MEDIUM4.67 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2020-27618 | MEDIUM4.67 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-10029 | MEDIUM4.67 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2020-27618 | MEDIUM4.67 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-10029 | MEDIUM4.67 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2020-27618 | MEDIUM4.67 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-36408 | MEDIUM4.67 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-36410 | MEDIUM4.67 | libde265-0 1.0.3-1+b1 fixed in 1.0.3-1+deb10u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-24752 | MEDIUM4.67 | libde265-0 1.0.3-1+b1 fixed in 1.0.11-0+deb10u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-24754 | MEDIUM4.67 | libde265-0 1.0.3-1+b1 fixed in 1.0.11-0+deb10u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-24755 | MEDIUM4.67 | libde265-0 1.0.3-1+b1 fixed in 1.0.11-0+deb10u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-24756 | MEDIUM4.67 | libde265-0 1.0.3-1+b1 fixed in 1.0.11-0+deb10u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-24757 | MEDIUM4.67 | libde265-0 1.0.3-1+b1 fixed in 1.0.11-0+deb10u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-24758 | MEDIUM4.67 | libde265-0 1.0.3-1+b1 fixed in 1.0.11-0+deb10u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-21047 | MEDIUM4.67 | libelf1 0.176-1.1 fixed in 0.176-1.1+deb10u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-37600 | MEDIUM4.67 | libfdisk1 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-25309 | MEDIUM4.67 | libfribidi0 1.0.5-3.1+deb10u1 fixed in 1.0.5-3.1+deb10u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-25310 | MEDIUM4.67 | libfribidi0 1.0.5-3.1+deb10u1 fixed in 1.0.5-3.1+deb10u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-3800 | MEDIUM4.67 | libglib2.0-0 2.58.3-2+deb10u3 fixed in 2.58.3-2+deb10u4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-32611 | MEDIUM4.67 | libglib2.0-0 2.58.3-2+deb10u3 fixed in 2.58.3-2+deb10u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-32665 | MEDIUM4.67 | libglib2.0-0 2.58.3-2+deb10u3 fixed in 2.58.3-2+deb10u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-3800 | MEDIUM4.67 | libglib2.0-bin 2.58.3-2+deb10u3 fixed in 2.58.3-2+deb10u4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-32611 | MEDIUM4.67 | libglib2.0-bin 2.58.3-2+deb10u3 fixed in 2.58.3-2+deb10u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-32665 | MEDIUM4.67 | libglib2.0-bin 2.58.3-2+deb10u3 fixed in 2.58.3-2+deb10u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-3800 | MEDIUM4.67 | libglib2.0-data 2.58.3-2+deb10u3 fixed in 2.58.3-2+deb10u4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-32611 | MEDIUM4.67 | libglib2.0-data 2.58.3-2+deb10u3 fixed in 2.58.3-2+deb10u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-32665 | MEDIUM4.67 | libglib2.0-data 2.58.3-2+deb10u3 fixed in 2.58.3-2+deb10u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-3800 | MEDIUM4.67 | libglib2.0-dev-bin 2.58.3-2+deb10u3 fixed in 2.58.3-2+deb10u4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-32611 | MEDIUM4.67 | libglib2.0-dev-bin 2.58.3-2+deb10u3 fixed in 2.58.3-2+deb10u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-32665 | MEDIUM4.67 | libglib2.0-dev-bin 2.58.3-2+deb10u3 fixed in 2.58.3-2+deb10u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-35538 | MEDIUM4.67 | libjpeg-dev 1:1.5.2-2+deb10u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-35538 | MEDIUM4.67 | libjpeg62-turbo 1:1.5.2-2+deb10u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-35538 | MEDIUM4.67 | libjpeg62-turbo-dev 1:1.5.2-2+deb10u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-27750 | MEDIUM4.67 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2020-27756 | MEDIUM4.67 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-20176 | MEDIUM4.67 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-20224 | MEDIUM4.67 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-1289 | MEDIUM4.67 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-34151 | MEDIUM4.67 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-5341 | MEDIUM4.67 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-27750 | MEDIUM4.67 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2020-27756 | MEDIUM4.67 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-20176 | MEDIUM4.67 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-20224 | MEDIUM4.67 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-1289 | MEDIUM4.67 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-34151 | MEDIUM4.67 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-5341 | MEDIUM4.67 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-27750 | MEDIUM4.67 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2020-27756 | MEDIUM4.67 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-20176 | MEDIUM4.67 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-20224 | MEDIUM4.67 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-1289 | MEDIUM4.67 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-34151 | MEDIUM4.67 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-5341 | MEDIUM4.67 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-27750 | MEDIUM4.67 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2020-27756 | MEDIUM4.67 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-20176 | MEDIUM4.67 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-20224 | MEDIUM4.67 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-1289 | MEDIUM4.67 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-34151 | MEDIUM4.67 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-5341 | MEDIUM4.67 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-27750 | MEDIUM4.67 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2020-27756 | MEDIUM4.67 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-20176 | MEDIUM4.67 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-20224 | MEDIUM4.67 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-1289 | MEDIUM4.67 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-34151 | MEDIUM4.67 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-5341 | MEDIUM4.67 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-27750 | MEDIUM4.67 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2020-27756 | MEDIUM4.67 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-20176 | MEDIUM4.67 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-20224 | MEDIUM4.67 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-1289 | MEDIUM4.67 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-34151 | MEDIUM4.67 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-5341 | MEDIUM4.67 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-46657 | MEDIUM4.67 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.31-0+deb10u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-46658 | MEDIUM4.67 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.31-0+deb10u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-46659 | MEDIUM4.67 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-46661 | MEDIUM4.67 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-46662 | MEDIUM4.67 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-46663 | MEDIUM4.67 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-46664 | MEDIUM4.67 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-46665 | MEDIUM4.67 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-46666 | MEDIUM4.67 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.31-0+deb10u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-46667 | MEDIUM4.67 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-46668 | MEDIUM4.67 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-31621 | MEDIUM4.67 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-31622 | MEDIUM4.67 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-31623 | MEDIUM4.67 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-31624 | MEDIUM4.67 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-38791 | MEDIUM4.67 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-37600 | MEDIUM4.67 | libmount-dev 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-37600 | MEDIUM4.67 | libmount1 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-20300 | MEDIUM4.67 | libopenexr-dev 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-20302 | MEDIUM4.67 | libopenexr-dev 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-3477 | MEDIUM4.67 | libopenexr-dev 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-3478 | MEDIUM4.67 | libopenexr-dev 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-3479 | MEDIUM4.67 | libopenexr-dev 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-3598 | MEDIUM4.67 | libopenexr-dev 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-3933 | MEDIUM4.67 | libopenexr-dev 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-20300 | MEDIUM4.67 | libopenexr23 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-20302 | MEDIUM4.67 | libopenexr23 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-3477 | MEDIUM4.67 | libopenexr23 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-3478 | MEDIUM4.67 | libopenexr23 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-3479 | MEDIUM4.67 | libopenexr23 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-3598 | MEDIUM4.67 | libopenexr23 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-3933 | MEDIUM4.67 | libopenexr23 2.2.1-4.1+deb10u1 fixed in 2.2.1-4.1+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-37600 | MEDIUM4.67 | libsmartcols1 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2019-19645 | MEDIUM4.67 | libsqlite3-0 3.27.2-3+deb10u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2020-13631 | MEDIUM4.67 | libsqlite3-0 3.27.2-3+deb10u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-3821 | MEDIUM4.67 | libsystemd0 241-7~deb10u8 fixed in 241-7~deb10u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-4415 | MEDIUM4.67 | libsystemd0 241-7~deb10u8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-1354 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-2867 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-2868 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-2869 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3570 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-4645 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-48281 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0795 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0796 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0797 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0798 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0799 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0800 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0801 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0802 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0803 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0804 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-25433 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-25435 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-26965 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-26966 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-2908 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-30086 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-30774 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-3576 | MEDIUM4.67 | libtiff5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-1354 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-2867 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-2868 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-2869 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3570 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-4645 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-48281 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0795 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0796 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0797 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0798 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0799 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0800 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0801 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0802 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0803 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0804 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-25433 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-25435 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-26965 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-26966 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-2908 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-30086 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-30774 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-3576 | MEDIUM4.67 | libtiffxx5 4.1.0+git191117-2~deb10u2 fixed in 4.1.0+git191117-2~deb10u9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3821 | MEDIUM4.67 | libudev1 241-7~deb10u8 fixed in 241-7~deb10u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-4415 | MEDIUM4.67 | libudev1 241-7~deb10u8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2020-28935 | MEDIUM4.67 | libunbound8 1.9.0-2+deb10u2 fixed in 1.9.0-2+deb10u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-37600 | MEDIUM4.67 | libuuid1 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-43785 | MEDIUM4.67 | libx11-6 2:1.6.7-1+deb10u2 fixed in 2:1.6.7-1+deb10u4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-43786 | MEDIUM4.67 | libx11-6 2:1.6.7-1+deb10u2 fixed in 2:1.6.7-1+deb10u4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-43785 | MEDIUM4.67 | libx11-data 2:1.6.7-1+deb10u2 fixed in 2:1.6.7-1+deb10u4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-43786 | MEDIUM4.67 | libx11-data 2:1.6.7-1+deb10u2 fixed in 2:1.6.7-1+deb10u4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-43785 | MEDIUM4.67 | libx11-dev 2:1.6.7-1+deb10u2 fixed in 2:1.6.7-1+deb10u4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-43786 | MEDIUM4.67 | libx11-dev 2:1.6.7-1+deb10u2 fixed in 2:1.6.7-1+deb10u4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-46657 | MEDIUM4.67 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.31-0+deb10u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-46658 | MEDIUM4.67 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.31-0+deb10u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-46659 | MEDIUM4.67 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-46661 | MEDIUM4.67 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-46662 | MEDIUM4.67 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-46663 | MEDIUM4.67 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-46664 | MEDIUM4.67 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-46665 | MEDIUM4.67 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-46666 | MEDIUM4.67 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.31-0+deb10u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-46667 | MEDIUM4.67 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-46668 | MEDIUM4.67 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-31621 | MEDIUM4.67 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-31622 | MEDIUM4.67 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-31623 | MEDIUM4.67 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-31624 | MEDIUM4.67 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.34-0+deb10u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-38791 | MEDIUM4.67 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35255 | MEDIUM4.67 | @azure/identity 1.5.0 fixed in 4.2.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-40896 | MEDIUM4.67 | Pygments 2.7.4 fixed in 2.15.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25645 | MEDIUM4.67 | requests 2.26.0 fixed in 2.33.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38428 | MEDIUM4.64 | wget 1.20.1-1.1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48795 | MEDIUM4.6 | openssh-client 1:7.9p1-10+deb10u2 fixed in 1:7.9p1-10+deb10u4 | 93.5% Actively Exploited | Post-Exploit |
| CVE-2023-2455 | MEDIUM4.59 | libpq-dev 11.12-0+deb10u1 fixed in 11.20-0+deb10u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-2455 | MEDIUM4.59 | libpq5 11.12-0+deb10u1 fixed in 11.20-0+deb10u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-34064 | MEDIUM4.59 | python3-jinja2 2.10-2 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-25571 | MEDIUM4.59 | @backstage/catalog-model 0.9.0 fixed in 1.2.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-25571 | MEDIUM4.59 | @backstage/core-components 0.3.0 fixed in 0.12.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-25571 | MEDIUM4.59 | @backstage/plugin-catalog-backend 0.13.1 fixed in 1.7.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-46976 | MEDIUM4.59 | @backstage/plugin-techdocs-backend 0.9.1 fixed in 1.10.13 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-2142 | MEDIUM4.59 | nunjucks 3.2.3 fixed in 3.2.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-53382 | MEDIUM4.59 | prismjs 1.23.0 fixed in 1.30.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-34064 | MEDIUM4.59 | Jinja2 3.0.1 fixed in 3.1.4 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-29155 | MEDIUM4.58 | libldap-2.4-2 2.4.47+dfsg-3+deb10u6 fixed in 2.4.47+dfsg-3+deb10u7 | 64.5% Actively Exploited | Post-Exploit |
| CVE-2022-29155 | MEDIUM4.58 | libldap-common 2.4.47+dfsg-3+deb10u6 fixed in 2.4.47+dfsg-3+deb10u7 | 64.5% Actively Exploited | Post-Exploit |
| CVE-2021-3711 | MEDIUM4.58 | libssl1.1 1.1.1d-0+deb10u6 fixed in 1.1.1d-0+deb10u7 | 87.8% Actively Exploited | Post-Exploit |
| CVE-2023-38408 | MEDIUM4.58 | openssh-client 1:7.9p1-10+deb10u2 fixed in 1:7.9p1-10+deb10u3 | 79.7% Actively Exploited | Post-Exploit |
| CVE-2021-3711 | MEDIUM4.58 | openssl 1.1.1d-0+deb10u6 fixed in 1.1.1d-0+deb10u7 | 87.8% Actively Exploited | Post-Exploit |
| CVE-2015-20107 | MEDIUM4.56 | python2.7 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 7.1% Low-Moderate Risk | Post-Exploit |
| CVE-2015-20107 | MEDIUM4.56 | python2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 7.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-15847 | MEDIUM4.5 | cpp-8 8.3.0-6 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22946 | MEDIUM4.5 | curl 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27781 | MEDIUM4.5 | curl 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27782 | MEDIUM4.5 | curl 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2019-14855 | MEDIUM4.5 | dirmngr 2.2.12-1+deb10u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-15847 | MEDIUM4.5 | g++-8 8.3.0-6 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-15847 | MEDIUM4.5 | gcc-8 8.3.0-6 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2021-40330 | MEDIUM4.5 | git 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u4 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2023-23946 | MEDIUM4.5 | git 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u8 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-14855 | MEDIUM4.5 | gnupg 2.2.12-1+deb10u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-14855 | MEDIUM4.5 | gnupg-utils 2.2.12-1+deb10u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-14855 | MEDIUM4.5 | gpg 2.2.12-1+deb10u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-14855 | MEDIUM4.5 | gpg-agent 2.2.12-1+deb10u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-14855 | MEDIUM4.5 | gpg-wks-client 2.2.12-1+deb10u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-14855 | MEDIUM4.5 | gpg-wks-server 2.2.12-1+deb10u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-14855 | MEDIUM4.5 | gpgconf 2.2.12-1+deb10u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-14855 | MEDIUM4.5 | gpgsm 2.2.12-1+deb10u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-14855 | MEDIUM4.5 | gpgv 2.2.12-1+deb10u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22946 | MEDIUM4.5 | libcurl3-gnutls 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27781 | MEDIUM4.5 | libcurl3-gnutls 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27782 | MEDIUM4.5 | libcurl3-gnutls 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22946 | MEDIUM4.5 | libcurl4 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27781 | MEDIUM4.5 | libcurl4 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27782 | MEDIUM4.5 | libcurl4 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22946 | MEDIUM4.5 | libcurl4-openssl-dev 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27781 | MEDIUM4.5 | libcurl4-openssl-dev 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27782 | MEDIUM4.5 | libcurl4-openssl-dev 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2020-22218 | MEDIUM4.5 | libssh2-1 1.8.0-2.1 fixed in 1.8.0-2.1+deb10u1 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0215 | MEDIUM4.5 | openssl 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u4 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0464 | MEDIUM4.5 | openssl 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u5 | 3.7% Low-Moderate Risk | Post-Exploit |
| CVE-2019-20907 | MEDIUM4.5 | python2.7 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 6.3% Low-Moderate Risk | Post-Exploit |
| CVE-2020-10735 | MEDIUM4.5 | python2.7 2.7.16-2+deb10u1 No fix yet | 7.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-0391 | MEDIUM4.5 | python2.7 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 8.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-45061 | MEDIUM4.5 | python2.7 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48560 | MEDIUM4.5 | python2.7 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-20907 | MEDIUM4.5 | python2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 6.3% Low-Moderate Risk | Post-Exploit |
| CVE-2020-10735 | MEDIUM4.5 | python2.7-minimal 2.7.16-2+deb10u1 No fix yet | 7.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-0391 | MEDIUM4.5 | python2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 8.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-45061 | MEDIUM4.5 | python2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48560 | MEDIUM4.5 | python2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-24070 | MEDIUM4.5 | subversion 1.10.4-1+deb10u2 fixed in 1.10.4-1+deb10u3 | 9.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-40217 | MEDIUM4.5 | libpython2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-40217 | MEDIUM4.5 | libpython2.7-stdlib 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-40217 | MEDIUM4.5 | libpython3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-40217 | MEDIUM4.5 | libpython3.7-stdlib 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-40217 | MEDIUM4.5 | python3.7 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-40217 | MEDIUM4.5 | python3.7-minimal 3.7.3-2+deb10u3 fixed in 3.7.3-2+deb10u6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-37168 | MEDIUM4.5 | @grpc/grpc-js 1.3.2 fixed in 1.10.9, 1.9.15, 1.8.22 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-25288 | MEDIUM4.5 | @octokit/plugin-paginate-rest 2.7.0 fixed in 11.4.1, 9.2.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-25290 | MEDIUM4.5 | @octokit/request 5.6.0 fixed in 9.2.1, 8.4.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-25289 | MEDIUM4.5 | @octokit/request-error 2.1.0 fixed in 5.1.1, 6.1.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44288 | MEDIUM4.5 | @protobufjs/utf8 1.1.0 fixed in 1.1.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-27152 | MEDIUM4.5 | axios 0.21.1 fixed in 1.8.2, 0.30.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42034 | MEDIUM4.5 | axios 0.21.1 fixed in 1.15.1, 0.31.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42036 | MEDIUM4.5 | axios 0.21.1 fixed in 1.15.1, 0.31.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-102277 | MEDIUM4.5 | brace-expansion 1.1.11 fixed in 5.0.12, 3.0.9, 2.1.7, 1.1.21 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-32996 | MEDIUM4.5 | http-proxy-middleware 2.0.0 fixed in 2.0.8, 3.0.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-32997 | MEDIUM4.5 | http-proxy-middleware 2.0.0 fixed in 2.0.9, 3.0.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-64718 | MEDIUM4.5 | js-yaml 3.13.1 fixed in 4.1.1, 3.14.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53550 | MEDIUM4.5 | js-yaml 3.13.1 fixed in 4.2.0, 3.15.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-64718 | MEDIUM4.5 | js-yaml 3.14.1 fixed in 4.1.1, 3.14.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53550 | MEDIUM4.5 | js-yaml 3.14.1 fixed in 4.2.0, 3.15.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-64718 | MEDIUM4.5 | js-yaml 4.1.0 fixed in 4.1.1, 3.14.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53550 | MEDIUM4.5 | js-yaml 4.1.0 fixed in 4.2.0, 3.15.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2950 | MEDIUM4.5 | lodash 4.17.15 fixed in 4.18.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2950 | MEDIUM4.5 | lodash 4.17.21 fixed in 4.18.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2950 | MEDIUM4.5 | lodash-es 4.17.15 fixed in 4.18.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-15603 | MEDIUM4.5 | morgan 1.10.0 fixed in 1.12.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5078 | MEDIUM4.5 | morgan 1.10.0 fixed in 1.11.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-87859 | MEDIUM4.5 | morgan 1.10.0 fixed in 1.12.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-20162 | MEDIUM4.5 | ms 0.7.1 fixed in 2.0.0 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-24773 | MEDIUM4.5 | node-forge 0.10.0 fixed in 1.3.0 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-66030 | MEDIUM4.5 | node-forge 0.10.0 fixed in 1.3.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-24773 | MEDIUM4.5 | node-forge 0.8.5 fixed in 1.3.0 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-66030 | MEDIUM4.5 | node-forge 0.8.5 fixed in 1.3.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-45296 | MEDIUM4.5 | path-to-regexp 0.1.7 fixed in 1.9.0, 0.1.10, 8.0.0, 3.3.0, 6.3.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-52798 | MEDIUM4.5 | path-to-regexp 0.1.7 fixed in 0.1.12 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-4867 | MEDIUM4.5 | path-to-regexp 0.1.7 fixed in 0.1.13 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33672 | MEDIUM4.5 | picomatch 2.2.2 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44288 | MEDIUM4.5 | protobufjs 6.11.2 fixed in 7.5.6, 8.0.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44294 | MEDIUM4.5 | protobufjs 6.11.2 fixed in 7.5.6, 8.0.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54269 | MEDIUM4.5 | protobufjs 6.11.2 fixed in 7.6.3, 8.6.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-97058 | MEDIUM4.5 | sprintf-js 1.0.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-54798 | MEDIUM4.5 | tmp 0.0.33 fixed in 0.2.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-54798 | MEDIUM4.5 | tmp 0.2.1 fixed in 0.2.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-83610 | MEDIUM4.5 | xmldom 0.1.27 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83611 | MEDIUM4.5 | xmldom 0.1.27 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83610 | MEDIUM4.5 | xmldom 0.1.31 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83611 | MEDIUM4.5 | xmldom 0.1.31 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83610 | MEDIUM4.5 | xmldom 0.4.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83611 | MEDIUM4.5 | xmldom 0.4.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83610 | MEDIUM4.5 | xmldom 0.6.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83611 | MEDIUM4.5 | xmldom 0.6.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45409 | MEDIUM4.5 | idna 3.2 fixed in 3.15 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-61632 | MEDIUM4.5 | pymdown-extensions 7.1 fixed in 11.0.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-68142 | MEDIUM4.5 | pymdown-extensions 7.1 fixed in 10.16.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-47081 | MEDIUM4.5 | requests 2.26.0 fixed in 2.32.4 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-44431 | MEDIUM4.5 | urllib3 1.26.6 fixed in 2.7.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-32206 | MEDIUM4.48 | curl 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 33.1% High Exploitation Risk | Post-Exploit |
| CVE-2022-32206 | MEDIUM4.48 | libcurl3-gnutls 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 33.1% High Exploitation Risk | Post-Exploit |
| CVE-2022-32206 | MEDIUM4.48 | libcurl4 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 33.1% High Exploitation Risk | Post-Exploit |
| CVE-2022-32206 | MEDIUM4.48 | libcurl4-openssl-dev 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 33.1% High Exploitation Risk | Post-Exploit |
| CVE-2023-51385 | MEDIUM4.48 | openssh-client 1:7.9p1-10+deb10u2 fixed in 1:7.9p1-10+deb10u4 | 19.8% High Exploitation Risk | Post-Exploit |
| CVE-2024-28085 | MEDIUM4.4 | libblkid-dev 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libblkid1 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libfdisk1 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libmount-dev 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libmount1 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5870 | MEDIUM4.4 | libpq-dev 11.12-0+deb10u1 fixed in 11.22-0+deb10u1 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5870 | MEDIUM4.4 | libpq5 11.12-0+deb10u1 fixed in 11.22-0+deb10u1 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libsmartcols1 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libuuid1 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-26116 | MEDIUM4.32 | python2.7 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 6.4% Low-Moderate Risk | Post-Exploit |
| CVE-2020-26116 | MEDIUM4.32 | python2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 6.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5868 | MEDIUM4.3 | libpq-dev 11.12-0+deb10u1 fixed in 11.22-0+deb10u1 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5868 | MEDIUM4.3 | libpq5 11.12-0+deb10u1 fixed in 11.22-0+deb10u1 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-28544 | MEDIUM4.3 | libsvn1 1.10.4-1+deb10u2 fixed in 1.10.4-1+deb10u3 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-106498 | MEDIUM4.3 | @backstage/plugin-catalog-backend 0.13.1 fixed in 3.9.1 | — | Directly Exposed |
| CVE-2026-106561 | MEDIUM4.3 | @backstage/plugin-kubernetes-backend 0.3.13 fixed in 0.21.9 | — | Directly Exposed |
| CVE-2026-106461 | MEDIUM4.3 | @backstage/plugin-scaffolder-backend 0.14.2 fixed in 4.1.0 | — | Directly Exposed |
| CVE-2026-106562 | MEDIUM4.3 | @backstage/plugin-search-backend 0.2.3 fixed in 2.1.6 | — | Directly Exposed |
| CVE-2026-106562 | MEDIUM4.3 | @backstage/plugin-search-backend-module-elasticsearch 0.0.1 fixed in 1.8.7 | — | Directly Exposed |
| CVE-2021-21366 | MEDIUM4.3 | xmldom 0.1.27 fixed in 0.5.0 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-21366 | MEDIUM4.3 | xmldom 0.1.31 fixed in 0.5.0 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-21366 | MEDIUM4.3 | xmldom 0.4.0 fixed in 0.5.0 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-32021 | MEDIUM4.26 | git 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u9 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2021-41617 | MEDIUM4.2 | openssh-client 1:7.9p1-10+deb10u2 fixed in 1:7.9p1-10+deb10u4 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-24842 | MEDIUM4.18 | tar 2.2.2 fixed in 7.5.7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-24842 | MEDIUM4.18 | tar 4.4.13 fixed in 7.5.7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-24842 | MEDIUM4.18 | tar 4.4.15 fixed in 7.5.7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-24842 | MEDIUM4.18 | tar 6.1.2 fixed in 7.5.7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4863 | MEDIUM4.12 | libwebp-dev 0.6.1-2+deb10u1 fixed in 0.6.1-2+deb10u3 | 100.0% Actively Exploited | Post-Exploit |
| CVE-2023-4863 | MEDIUM4.12 | libwebp6 0.6.1-2+deb10u1 fixed in 0.6.1-2+deb10u3 | 100.0% Actively Exploited | Post-Exploit |
| CVE-2022-4304 | MEDIUM4.07 | openssl 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u4 | 16.2% High Exploitation Risk | Post-Exploit |
| CVE-2021-23336 | MEDIUM4.07 | python2.7 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 40.7% High Exploitation Risk | Post-Exploit |
| CVE-2021-23336 | MEDIUM4.07 | python2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 40.7% High Exploitation Risk | Post-Exploit |
| CVE-2019-8457 | MEDIUM4.06 | libdb5.3 5.3.28+dfsg1-0.5 No fix yet | 45.4% High Exploitation Risk | Post-Exploit |
| CVE-2019-8457 | MEDIUM4.06 | libdb5.3-dev 5.3.28+dfsg1-0.5 No fix yet | 45.4% High Exploitation Risk | Post-Exploit |
| CVE-2022-25236 | MEDIUM4.06 | libexpat1 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u3 | 35.9% High Exploitation Risk | Post-Exploit |
| CVE-2022-25236 | MEDIUM4.06 | libexpat1-dev 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u3 | 35.9% High Exploitation Risk | Post-Exploit |
| CVE-2021-3177 | MEDIUM4.06 | libpython2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 23.3% High Exploitation Risk | Post-Exploit |
| CVE-2021-3177 | MEDIUM4.06 | libpython2.7-stdlib 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 23.3% High Exploitation Risk | Post-Exploit |
| CVE-2021-3177 | MEDIUM4.06 | python2.7 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 23.3% High Exploitation Risk | Post-Exploit |
| CVE-2021-3177 | MEDIUM4.06 | python2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 23.3% High Exploitation Risk | Post-Exploit |
| CVE-2022-37434 | MEDIUM4.06 | zlib1g 1:1.2.11.dfsg-1 fixed in 1:1.2.11.dfsg-1+deb10u2 | 19.0% High Exploitation Risk | Post-Exploit |
| CVE-2026-32235 | MEDIUM4 | @backstage/plugin-auth-backend 0.3.19 fixed in 0.27.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-73563 | MEDIUM4 | @backstage/plugin-auth-backend 0.3.19 fixed in 0.29.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43796 | MEDIUM4 | express 4.17.1 fixed in 4.20.0, 5.0.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33916 | MEDIUM4 | handlebars 4.7.7 fixed in 4.7.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-43799 | MEDIUM4 | send 0.17.1 fixed in 0.19.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-43800 | MEDIUM4 | serve-static 1.14.1 fixed in 1.16.0, 2.1.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc-bin 2.28-10 fixed in 2.28-10+deb10u4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc6 2.28-10 fixed in 2.28-10+deb10u4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21427 | MEDIUM4 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21427 | MEDIUM4 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u1 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29187 | LOW3.98 | git 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2020-16156 | LOW3.98 | perl 5.28.1-6+deb10u1 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2020-16156 | LOW3.98 | perl-base 5.28.1-6+deb10u1 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2021-4435 | LOW3.98 | yarn 1.22.5 fixed in 1.22.13 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-27776 | LOW3.9 | curl 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 3.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-23916 | LOW3.9 | curl 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u5 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46218 | LOW3.9 | curl 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u8 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-34903 | LOW3.9 | dirmngr 2.2.12-1+deb10u1 fixed in 2.2.12-1+deb10u2 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-34903 | LOW3.9 | gnupg 2.2.12-1+deb10u1 fixed in 2.2.12-1+deb10u2 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-34903 | LOW3.9 | gnupg-utils 2.2.12-1+deb10u1 fixed in 2.2.12-1+deb10u2 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-34903 | LOW3.9 | gpg 2.2.12-1+deb10u1 fixed in 2.2.12-1+deb10u2 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-34903 | LOW3.9 | gpg-agent 2.2.12-1+deb10u1 fixed in 2.2.12-1+deb10u2 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-34903 | LOW3.9 | gpg-wks-client 2.2.12-1+deb10u1 fixed in 2.2.12-1+deb10u2 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-34903 | LOW3.9 | gpg-wks-server 2.2.12-1+deb10u1 fixed in 2.2.12-1+deb10u2 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-34903 | LOW3.9 | gpgconf 2.2.12-1+deb10u1 fixed in 2.2.12-1+deb10u2 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-34903 | LOW3.9 | gpgsm 2.2.12-1+deb10u1 fixed in 2.2.12-1+deb10u2 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-34903 | LOW3.9 | gpgv 2.2.12-1+deb10u1 fixed in 2.2.12-1+deb10u2 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27776 | LOW3.9 | libcurl3-gnutls 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 3.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-23916 | LOW3.9 | libcurl3-gnutls 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u5 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46218 | LOW3.9 | libcurl3-gnutls 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u8 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27776 | LOW3.9 | libcurl4 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 3.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-23916 | LOW3.9 | libcurl4 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u5 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46218 | LOW3.9 | libcurl4 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u8 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27776 | LOW3.9 | libcurl4-openssl-dev 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 3.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-23916 | LOW3.9 | libcurl4-openssl-dev 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u5 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46218 | LOW3.9 | libcurl4-openssl-dev 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u8 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2020-8492 | LOW3.9 | python2.7 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 6.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3733 | LOW3.9 | python2.7 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 4.7% Low-Moderate Risk | Post-Exploit |
| CVE-2020-8492 | LOW3.9 | python2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 6.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3733 | LOW3.9 | python2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 4.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-59873 | LOW3.82 | tar 2.2.2 fixed in 7.5.19 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-59874 | LOW3.82 | tar 2.2.2 fixed in 7.5.18 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-73566 | LOW3.82 | tar 2.2.2 fixed in 7.5.21 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-59871 | LOW3.82 | tar 2.2.2 fixed in 7.5.18 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-59873 | LOW3.82 | tar 4.4.13 fixed in 7.5.19 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-59874 | LOW3.82 | tar 4.4.13 fixed in 7.5.18 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-73566 | LOW3.82 | tar 4.4.13 fixed in 7.5.21 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-59871 | LOW3.82 | tar 4.4.13 fixed in 7.5.18 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-59873 | LOW3.82 | tar 4.4.15 fixed in 7.5.19 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-59874 | LOW3.82 | tar 4.4.15 fixed in 7.5.18 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-73566 | LOW3.82 | tar 4.4.15 fixed in 7.5.21 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-59871 | LOW3.82 | tar 4.4.15 fixed in 7.5.18 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-59873 | LOW3.82 | tar 6.1.2 fixed in 7.5.19 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-59874 | LOW3.82 | tar 6.1.2 fixed in 7.5.18 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-73566 | LOW3.82 | tar 6.1.2 fixed in 7.5.21 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-59871 | LOW3.82 | tar 6.1.2 fixed in 7.5.18 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-21538 | LOW3.74 | cross-spawn 5.1.0 fixed in 7.0.5, 6.0.6 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-21538 | LOW3.74 | cross-spawn 6.0.5 fixed in 7.0.5, 6.0.6 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-21538 | LOW3.74 | cross-spawn 7.0.3 fixed in 7.0.5, 6.0.6 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-33655 | LOW3.7 | libunbound8 1.9.0-2+deb10u2 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-31879 | LOW3.66 | wget 1.20.1-1.1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1552 | LOW3.64 | libpq-dev 11.12-0+deb10u1 fixed in 11.16-0+deb10u1 | 16.0% High Exploitation Risk | Post-Exploit |
| CVE-2022-1552 | LOW3.64 | libpq5 11.12-0+deb10u1 fixed in 11.16-0+deb10u1 | 16.0% High Exploitation Risk | Post-Exploit |
| CVE-2021-30560 | LOW3.64 | libxslt1-dev 1.1.32-2.2~deb10u1 fixed in 1.1.32-2.2~deb10u2 | 17.6% High Exploitation Risk | Post-Exploit |
| CVE-2021-30560 | LOW3.64 | libxslt1.1 1.1.32-2.2~deb10u1 fixed in 1.1.32-2.2~deb10u2 | 17.6% High Exploitation Risk | Post-Exploit |
| CVE-2026-26960 | LOW3.62 | tar 2.2.2 fixed in 7.5.8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-26960 | LOW3.62 | tar 4.4.13 fixed in 7.5.8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-26960 | LOW3.62 | tar 4.4.15 fixed in 7.5.8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-26960 | LOW3.62 | tar 6.1.2 fixed in 7.5.8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2020-26301 | LOW3.6 | ssh2 0.8.9 fixed in 1.4.0 | 3.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-23920 | LOW3.57 | libnode64 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-23920 | LOW3.57 | nodejs 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-45803 | LOW3.57 | urllib3 1.26.6 fixed in 2.0.7, 1.26.18 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-22947 | LOW3.54 | curl 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-32208 | LOW3.54 | curl 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 7.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-43552 | LOW3.54 | curl 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u4 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27535 | LOW3.54 | curl 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u6 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27536 | LOW3.54 | curl 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u6 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28321 | LOW3.54 | curl 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u7 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22947 | LOW3.54 | libcurl3-gnutls 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-32208 | LOW3.54 | libcurl3-gnutls 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 7.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-43552 | LOW3.54 | libcurl3-gnutls 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u4 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27535 | LOW3.54 | libcurl3-gnutls 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u6 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27536 | LOW3.54 | libcurl3-gnutls 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u6 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28321 | LOW3.54 | libcurl3-gnutls 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u7 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22947 | LOW3.54 | libcurl4 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-32208 | LOW3.54 | libcurl4 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 7.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-43552 | LOW3.54 | libcurl4 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u4 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27535 | LOW3.54 | libcurl4 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u6 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27536 | LOW3.54 | libcurl4 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u6 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28321 | LOW3.54 | libcurl4 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u7 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22947 | LOW3.54 | libcurl4-openssl-dev 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-32208 | LOW3.54 | libcurl4-openssl-dev 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 7.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-43552 | LOW3.54 | libcurl4-openssl-dev 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u4 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27535 | LOW3.54 | libcurl4-openssl-dev 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u6 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27536 | LOW3.54 | libcurl4-openssl-dev 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u6 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28321 | LOW3.54 | libcurl4-openssl-dev 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u7 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-4160 | LOW3.54 | openssl 1.1.1d-0+deb10u6 fixed in 1.1.1d-0+deb10u8 | 3.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48566 | LOW3.54 | python2.7 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48566 | LOW3.54 | python2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-40897 | LOW3.54 | setuptools 41.2.0 fixed in 65.5.1 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-32221 | LOW3.53 | curl 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u4 | 4.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1664 | LOW3.53 | dpkg 1.19.7 fixed in 1.19.8 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1664 | LOW3.53 | dpkg-dev 1.19.7 fixed in 1.19.8 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2021-2372 | LOW3.5 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.31-0+deb10u1 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-2372 | LOW3.5 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.31-0+deb10u1 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-106487 | LOW3.5 | @backstage/plugin-kubernetes-backend 0.3.13 fixed in 0.21.10 | — | Directly Exposed |
| CVE-2022-27774 | LOW3.42 | curl 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u4 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27774 | LOW3.42 | libcurl3-gnutls 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u4 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27774 | LOW3.42 | libcurl4 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u4 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27774 | LOW3.42 | libcurl4-openssl-dev 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u4 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3572 | LOW3.42 | pip 19.2.3 fixed in 21.1 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2024-33602 | LOW3.4 | libc-bin 2.28-10 fixed in 2.28-10+deb10u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | libc6 2.28-10 fixed in 2.28-10+deb10u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3449 | LOW3.4 | @tootallnate/once 1.1.2 fixed in 3.0.1, 2.0.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-4741 | LOW3.36 | openssl 1.1.1d-0+deb10u6 No fix yet | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2016-2781 | LOW3.31 | coreutils 8.30-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-28863 | LOW3.31 | tar 2.2.2 fixed in 6.2.1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-28863 | LOW3.31 | tar 4.4.13 fixed in 6.2.1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-28863 | LOW3.31 | tar 4.4.15 fixed in 6.2.1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-28863 | LOW3.31 | tar 6.1.2 fixed in 6.2.1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-13346 | LOW3.31 | pip 19.2.3 fixed in 26.2.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-27538 | LOW3.3 | curl 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u6 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-39253 | LOW3.3 | git 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u5 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27538 | LOW3.3 | libcurl3-gnutls 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u6 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27538 | LOW3.3 | libcurl4 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u6 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27538 | LOW3.3 | libcurl4-openssl-dev 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u6 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-0727 | LOW3.3 | openssl 1.1.1d-0+deb10u6 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-0529 | LOW3.3 | unzip 6.0-23+deb10u2 fixed in 6.0-23+deb10u3 | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-0530 | LOW3.3 | unzip 6.0-23+deb10u2 fixed in 6.0-23+deb10u3 | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2020-25666 | LOW3.3 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25675 | LOW3.3 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27560 | LOW3.3 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27751 | LOW3.3 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27754 | LOW3.3 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27757 | LOW3.3 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27758 | LOW3.3 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27759 | LOW3.3 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27761 | LOW3.3 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27764 | LOW3.3 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27765 | LOW3.3 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27767 | LOW3.3 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27768 | LOW3.3 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27769 | LOW3.3 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27771 | LOW3.3 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27772 | LOW3.3 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27774 | LOW3.3 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27775 | LOW3.3 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25666 | LOW3.3 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25675 | LOW3.3 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27560 | LOW3.3 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27751 | LOW3.3 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27754 | LOW3.3 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27757 | LOW3.3 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27758 | LOW3.3 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27759 | LOW3.3 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27761 | LOW3.3 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27764 | LOW3.3 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27765 | LOW3.3 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27767 | LOW3.3 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27768 | LOW3.3 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27769 | LOW3.3 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27771 | LOW3.3 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27772 | LOW3.3 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27774 | LOW3.3 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27775 | LOW3.3 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25666 | LOW3.3 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25675 | LOW3.3 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27560 | LOW3.3 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27751 | LOW3.3 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27754 | LOW3.3 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27757 | LOW3.3 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27758 | LOW3.3 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27759 | LOW3.3 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27761 | LOW3.3 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27764 | LOW3.3 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27765 | LOW3.3 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27767 | LOW3.3 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27768 | LOW3.3 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27769 | LOW3.3 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27771 | LOW3.3 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27772 | LOW3.3 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27774 | LOW3.3 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27775 | LOW3.3 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25666 | LOW3.3 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25675 | LOW3.3 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27560 | LOW3.3 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27751 | LOW3.3 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27754 | LOW3.3 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27757 | LOW3.3 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27758 | LOW3.3 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27759 | LOW3.3 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27761 | LOW3.3 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27764 | LOW3.3 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27765 | LOW3.3 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27767 | LOW3.3 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27768 | LOW3.3 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27769 | LOW3.3 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27771 | LOW3.3 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27772 | LOW3.3 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27774 | LOW3.3 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27775 | LOW3.3 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25666 | LOW3.3 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25675 | LOW3.3 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27560 | LOW3.3 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27751 | LOW3.3 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27754 | LOW3.3 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27757 | LOW3.3 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27758 | LOW3.3 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27759 | LOW3.3 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27761 | LOW3.3 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27764 | LOW3.3 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27765 | LOW3.3 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27767 | LOW3.3 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27768 | LOW3.3 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27769 | LOW3.3 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27771 | LOW3.3 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27772 | LOW3.3 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27774 | LOW3.3 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27775 | LOW3.3 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25666 | LOW3.3 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25675 | LOW3.3 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27560 | LOW3.3 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27751 | LOW3.3 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27754 | LOW3.3 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27757 | LOW3.3 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27758 | LOW3.3 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27759 | LOW3.3 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27761 | LOW3.3 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27764 | LOW3.3 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27765 | LOW3.3 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27767 | LOW3.3 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27768 | LOW3.3 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27769 | LOW3.3 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27771 | LOW3.3 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27772 | LOW3.3 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27774 | LOW3.3 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27775 | LOW3.3 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25666 | LOW3.3 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25675 | LOW3.3 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27560 | LOW3.3 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27751 | LOW3.3 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27754 | LOW3.3 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27757 | LOW3.3 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27758 | LOW3.3 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27759 | LOW3.3 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27761 | LOW3.3 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27764 | LOW3.3 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27765 | LOW3.3 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27767 | LOW3.3 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27768 | LOW3.3 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27769 | LOW3.3 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27771 | LOW3.3 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27772 | LOW3.3 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27774 | LOW3.3 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27775 | LOW3.3 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25666 | LOW3.3 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25675 | LOW3.3 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27560 | LOW3.3 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27751 | LOW3.3 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27754 | LOW3.3 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27757 | LOW3.3 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27758 | LOW3.3 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27759 | LOW3.3 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27761 | LOW3.3 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27764 | LOW3.3 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27765 | LOW3.3 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27767 | LOW3.3 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27768 | LOW3.3 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27769 | LOW3.3 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27771 | LOW3.3 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27772 | LOW3.3 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27774 | LOW3.3 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27775 | LOW3.3 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25666 | LOW3.3 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25675 | LOW3.3 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27560 | LOW3.3 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27751 | LOW3.3 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27754 | LOW3.3 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27757 | LOW3.3 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27758 | LOW3.3 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27759 | LOW3.3 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27761 | LOW3.3 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27764 | LOW3.3 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27765 | LOW3.3 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27767 | LOW3.3 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27768 | LOW3.3 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27769 | LOW3.3 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27771 | LOW3.3 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27772 | LOW3.3 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27774 | LOW3.3 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27775 | LOW3.3 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34397 | LOW3.23 | libglib2.0-0 2.58.3-2+deb10u3 fixed in 2.58.3-2+deb10u6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-34397 | LOW3.23 | libglib2.0-bin 2.58.3-2+deb10u3 fixed in 2.58.3-2+deb10u6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-34397 | LOW3.23 | libglib2.0-data 2.58.3-2+deb10u3 fixed in 2.58.3-2+deb10u6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-34397 | LOW3.23 | libglib2.0-dev-bin 2.58.3-2+deb10u3 fixed in 2.58.3-2+deb10u6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-29786 | LOW3.21 | tar 2.2.2 fixed in 7.5.10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-29786 | LOW3.21 | tar 4.4.13 fixed in 7.5.10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-29786 | LOW3.21 | tar 4.4.15 fixed in 7.5.10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-29786 | LOW3.21 | tar 6.1.2 fixed in 7.5.10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-2097 | LOW3.18 | openssl 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u4 | 4.9% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0465 | LOW3.18 | openssl 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u5 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0466 | LOW3.18 | openssl 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u5 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-3446 | LOW3.18 | openssl 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u6 | 6.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-3817 | LOW3.18 | openssl 1.1.1d-0+deb10u6 fixed in 1.1.1n-0+deb10u6 | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5678 | LOW3.18 | openssl 1.1.1d-0+deb10u6 No fix yet | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2018-7169 | LOW3.18 | passwd 1:4.5-1.1 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-4189 | LOW3.18 | python2.7 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27043 | LOW3.18 | python2.7 2.7.16-2+deb10u1 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-4189 | LOW3.18 | python2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u2 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27043 | LOW3.18 | python2.7-minimal 2.7.16-2+deb10u1 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-0450 | LOW3.16 | python2.7 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-0450 | LOW3.16 | python2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-67319 | LOW3.15 | axios 0.21.1 fixed in 0.33.0, 1.18.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42040 | LOW3.15 | axios 0.21.1 fixed in 1.15.1, 0.31.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47764 | LOW3.15 | cookie 0.4.0 fixed in 0.7.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-47764 | LOW3.15 | cookie 0.4.1 fixed in 0.7.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-23745 | LOW3.11 | tar 2.2.2 fixed in 7.5.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-23745 | LOW3.11 | tar 4.4.13 fixed in 7.5.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-23745 | LOW3.11 | tar 4.4.15 fixed in 7.5.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-23745 | LOW3.11 | tar 6.1.2 fixed in 7.5.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59890 | LOW3.11 | setuptools 41.2.0 fixed in 83.0.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-106496 | LOW3.1 | @backstage/plugin-catalog-backend 0.13.1 fixed in 3.9.1 | — | Directly Exposed |
| CVE-2021-39212 | LOW3.06 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-39212 | LOW3.06 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-39212 | LOW3.06 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-39212 | LOW3.06 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-39212 | LOW3.06 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-39212 | LOW3.06 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-39212 | LOW3.06 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-39212 | LOW3.06 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-39212 | LOW3.06 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23950 | LOW3.01 | tar 2.2.2 fixed in 7.5.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-23950 | LOW3.01 | tar 4.4.13 fixed in 7.5.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-23950 | LOW3.01 | tar 4.4.15 fixed in 7.5.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-23950 | LOW3.01 | tar 6.1.2 fixed in 7.5.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6357 | LOW2.96 | pip 19.2.3 fixed in 26.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-2511 | LOW2.89 | openssl 1.1.1d-0+deb10u6 No fix yet | 52.4% Actively Exploited | Post-Exploit |
| CVE-2025-7339 | LOW2.89 | on-headers 1.0.2 fixed in 1.1.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-37600 | LOW2.8 | bsdutils 1:2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-37600 | LOW2.8 | fdisk 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-22490 | LOW2.8 | git 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-37600 | LOW2.8 | mount 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-4641 | LOW2.8 | passwd 1:4.5-1.1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-37600 | LOW2.8 | util-linux 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-31802 | LOW2.8 | tar 2.2.2 fixed in 7.5.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53655 | LOW2.8 | tar 2.2.2 fixed in 7.5.16 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31802 | LOW2.8 | tar 4.4.13 fixed in 7.5.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53655 | LOW2.8 | tar 4.4.13 fixed in 7.5.16 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31802 | LOW2.8 | tar 4.4.15 fixed in 7.5.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53655 | LOW2.8 | tar 4.4.15 fixed in 7.5.16 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31802 | LOW2.8 | tar 6.1.2 fixed in 7.5.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53655 | LOW2.8 | tar 6.1.2 fixed in 7.5.16 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8643 | LOW2.8 | pip 19.2.3 fixed in 26.1.2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2020-27763 | LOW2.8 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-27773 | LOW2.8 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2020-27776 | LOW2.8 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-3574 | LOW2.8 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-27763 | LOW2.8 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-27773 | LOW2.8 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2020-27776 | LOW2.8 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-3574 | LOW2.8 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-27763 | LOW2.8 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-27773 | LOW2.8 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2020-27776 | LOW2.8 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-3574 | LOW2.8 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-19126 | LOW2.8 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-19126 | LOW2.8 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-19126 | LOW2.8 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-19126 | LOW2.8 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-27763 | LOW2.8 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-27773 | LOW2.8 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2020-27776 | LOW2.8 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-3574 | LOW2.8 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-27763 | LOW2.8 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-27773 | LOW2.8 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2020-27776 | LOW2.8 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-3574 | LOW2.8 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-27763 | LOW2.8 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-27773 | LOW2.8 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2020-27776 | LOW2.8 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-3574 | LOW2.8 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-27763 | LOW2.8 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-27773 | LOW2.8 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2020-27776 | LOW2.8 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-3574 | LOW2.8 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-27763 | LOW2.8 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-27773 | LOW2.8 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2020-27776 | LOW2.8 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-3574 | LOW2.8 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-27763 | LOW2.8 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-27773 | LOW2.8 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2020-27776 | LOW2.8 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-3574 | LOW2.8 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-4016 | LOW2.8 | libprocps7 2:3.3.15-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-36084 | LOW2.8 | libsepol1 2.8-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-36085 | LOW2.8 | libsepol1 2.8-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-36086 | LOW2.8 | libsepol1 2.8-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-36087 | LOW2.8 | libsepol1 2.8-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-36084 | LOW2.8 | libsepol1-dev 2.8-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-36085 | LOW2.8 | libsepol1-dev 2.8-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-36086 | LOW2.8 | libsepol1-dev 2.8-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-36087 | LOW2.8 | libsepol1-dev 2.8-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4539 | LOW2.8 | Pygments 2.7.4 fixed in 2.20.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-40217 | LOW2.7 | python2.7 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-40217 | LOW2.7 | python2.7-minimal 2.7.16-2+deb10u1 fixed in 2.7.16-2+deb10u3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-59875 | LOW2.7 | tar 2.2.2 fixed in 7.5.17 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-59875 | LOW2.7 | tar 4.4.13 fixed in 7.5.17 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-59875 | LOW2.7 | tar 4.4.15 fixed in 7.5.17 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-59875 | LOW2.7 | tar 6.1.2 fixed in 7.5.17 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8869 | LOW2.7 | pip 19.2.3 fixed in 25.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | bsdutils 1:2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | fdisk 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | mount 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | util-linux 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-5889 | LOW2.63 | brace-expansion 1.1.11 fixed in 2.0.2, 1.1.12, 3.0.1, 4.0.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83608 | LOW2.63 | xmldom 0.1.27 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83608 | LOW2.63 | xmldom 0.1.31 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83608 | LOW2.63 | xmldom 0.4.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83608 | LOW2.63 | xmldom 0.6.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-28544 | LOW2.58 | subversion 1.10.4-1+deb10u2 fixed in 1.10.4-1+deb10u3 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3219 | LOW2.55 | pip 19.2.3 fixed in 26.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-29185 | LOW2.29 | @backstage/integration 0.5.9 fixed in 1.20.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-20795 | LOW2.24 | iproute2 4.20.0-2+deb10u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-22924 | LOW2.22 | curl 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 6.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-35252 | LOW2.22 | curl 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u4 | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28322 | LOW2.22 | curl 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u8 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-38546 | LOW2.22 | curl 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u7 | 6.2% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22924 | LOW2.22 | libcurl3-gnutls 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 6.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-35252 | LOW2.22 | libcurl3-gnutls 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u4 | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28322 | LOW2.22 | libcurl3-gnutls 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u8 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-38546 | LOW2.22 | libcurl3-gnutls 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u7 | 6.2% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22924 | LOW2.22 | libcurl4 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 6.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-35252 | LOW2.22 | libcurl4 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u4 | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28322 | LOW2.22 | libcurl4 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u8 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-38546 | LOW2.22 | libcurl4 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u7 | 6.2% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22924 | LOW2.22 | libcurl4-openssl-dev 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 6.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-35252 | LOW2.22 | libcurl4-openssl-dev 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u4 | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28322 | LOW2.22 | libcurl4-openssl-dev 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u8 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-38546 | LOW2.22 | libcurl4-openssl-dev 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u7 | 6.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-55285 | LOW2.21 | @backstage/plugin-scaffolder-backend 0.14.2 fixed in 2.1.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-27645 | LOW2.12 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-27645 | LOW2.12 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-27645 | LOW2.12 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-27645 | LOW2.12 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-1703 | LOW1.99 | pip 19.2.3 fixed in 26.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-22898 | LOW1.86 | curl 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22898 | LOW1.86 | libcurl3-gnutls 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22898 | LOW1.86 | libcurl4 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22898 | LOW1.86 | libcurl4-openssl-dev 7.64.0-4+deb10u2 fixed in 7.64.0-4+deb10u3 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-29383 | LOW1.68 | passwd 1:4.5-1.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-4016 | LOW1.68 | procps 2:3.3.15-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-39804 | LOW1.68 | tar 1.30+dfsg-6 fixed in 1.30+dfsg-6+deb10u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-5752 | LOW1.68 | pip 19.2.3 fixed in 23.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-25815 | LOW1.12 | git 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u9 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-23521 | NONE0 | git-man 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u7 | 56.3% Actively Exploited | Not Applicable |
| CVE-2022-41903 | NONE0 | git-man 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u7 | 44.3% High Exploitation Risk | Not Applicable |
| CVE-2023-25775 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-22930 | NONE0 | nodejs-doc 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u2 | 36.5% High Exploitation Risk | Not Applicable |
| CVE-2024-32002 | NONE0 | git-man 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u9 | 29.2% High Exploitation Risk | Not Applicable |
| CVE-2019-1387 | NONE0 | git-man 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u9 | 4.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-39260 | NONE0 | git-man 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u5 | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-42898 | NONE0 | krb5-multidev 1.17-3+deb10u1 fixed in 1.17-3+deb10u5 | 6.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-39537 | NONE0 | libncurses-dev 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u5 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-39537 | NONE0 | libncurses6 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u5 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-39537 | NONE0 | libncursesw5-dev 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u5 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-39537 | NONE0 | libncursesw6 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u5 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-39537 | NONE0 | libtinfo6 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u5 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-3653 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-3656 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2022-0435 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 68.0% Actively Exploited | Not Applicable |
| CVE-2022-27223 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-3640 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-42896 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-39537 | NONE0 | ncurses-base 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u5 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-39537 | NONE0 | ncurses-bin 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u5 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-1012 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 4.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-21824 | NONE0 | nodejs-doc 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u2 | 21.5% High Exploitation Risk | Not Applicable |
| CVE-2022-32212 | NONE0 | nodejs-doc 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u2 | 6.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-43548 | NONE0 | nodejs-doc 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u3 | 14.6% High Exploitation Risk | Not Applicable |
| CVE-2022-1304 | NONE0 | comerr-dev 2.1-1.44.5-1+deb10u3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-48622 | NONE0 | gir1.2-gdkpixbuf-2.0 2.38.1+dfsg-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-24765 | NONE0 | git-man 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u5 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-29187 | NONE0 | git-man 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-29007 | NONE0 | git-man 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u9 | 6.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-32004 | NONE0 | git-man 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u9 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-32465 | NONE0 | git-man 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u9 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-29491 | NONE0 | libncurses-dev 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u5 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-29491 | NONE0 | libncurses6 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u5 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-29491 | NONE0 | libncursesw5-dev 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u5 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-29491 | NONE0 | libncursesw6 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u5 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-29491 | NONE0 | libtinfo6 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u5 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-19449 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-25162 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-12362 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-16119 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-22543 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-33631 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-3444 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-35039 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3600 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3612 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-37576 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-3760 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-38160 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-38300 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-39685 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-39698 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-41864 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-4197 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-42008 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2021-42252 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-4439 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-45469 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-46936 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47082 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47103 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2021-47194 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47222 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47235 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47239 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47254 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47261 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47293 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47301 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47310 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47311 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47321 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47328 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2021-47334 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47336 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47355 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47357 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47358 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47361 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47372 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47388 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47404 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47458 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47474 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47475 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47477 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-47483 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47485 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47497 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47500 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47505 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47506 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2021-47520 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47521 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47541 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47549 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47565 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47566 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47571 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47576 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47589 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47598 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47600 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47609 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-0330 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-0492 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 5.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-1011 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-1419 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-1652 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-1679 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-20368 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-20421 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2022-20566 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-22942 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-24958 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.235-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-2586 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 10.2% High Exploitation Risk | Not Applicable |
| CVE-2022-2588 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 5.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-2639 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-26490 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-27666 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 5.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-28390 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-29581 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-2964 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2977 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-2978 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-30594 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-32250 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-3239 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3424 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3545 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-3565 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-4095 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-4378 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-45934 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-4744 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-48626 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48672 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48695 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48702 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48717 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48732 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48742 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48771 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0386 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 7.9% Low-Moderate Risk | Not Applicable |
| CVE-2023-0461 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-1078 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1118 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-1281 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-1670 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-1829 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-2007 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.289-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-20938 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-23559 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-3090 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.289-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-3111 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.289-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31436 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-32233 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.289-1 | 13.0% High Exploitation Risk | Not Applicable |
| CVE-2023-3390 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-34319 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-35001 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-35788 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.289-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-3609 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-3611 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-3776 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-3812 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-40283 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-4206 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4207 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-4208 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-42753 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-4623 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-4921 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-51042 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52436 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52439 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52444 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52445 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52451 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52464 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52469 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52475 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52510 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52594 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52599 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52600 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52603 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52604 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52612 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52679 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52691 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52764 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52796 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52799 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52804 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52805 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52818 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52835 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52836 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52840 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52864 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52867 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52868 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-5717 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-6040 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-1086 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 28.1% High Exploitation Risk | Not Applicable |
| CVE-2024-26625 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26704 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26754 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26793 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26883 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26884 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26898 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26934 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26955 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26956 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26957 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26965 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26981 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27000 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27008 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27024 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27043 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27075 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27395 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27396 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27398 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-35789 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-35847 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35886 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36015 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36886 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-36904 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36934 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36940 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36971 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2024-38552 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38578 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38583 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38627 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-32981 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-29491 | NONE0 | ncurses-base 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u5 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-29491 | NONE0 | ncurses-bin 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u5 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2021-21300 | NONE0 | git-man 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u4 | 88.5% Actively Exploited | Not Applicable |
| CVE-2021-40330 | NONE0 | git-man 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u4 | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2023-23946 | NONE0 | git-man 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u8 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-25652 | NONE0 | git-man 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u9 | 51.9% Actively Exploited | Not Applicable |
| CVE-2019-14855 | NONE0 | gnupg-l10n 2.2.12-1+deb10u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-36222 | NONE0 | krb5-multidev 1.17-3+deb10u1 fixed in 1.17-3+deb10u2 | 10.3% High Exploitation Risk | Not Applicable |
| CVE-2021-38207 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 3.4% Low-Moderate Risk | Not Applicable |
| CVE-2021-45485 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 3.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-1199 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-1678 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-36946 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 7.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-0045 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-45871 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-46838 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-52340 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2021-22940 | NONE0 | nodejs-doc 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u2 | 13.9% High Exploitation Risk | Not Applicable |
| CVE-2023-30590 | NONE0 | nodejs-doc 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u4 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2021-20322 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 6.9% Low-Moderate Risk | Not Applicable |
| CVE-2021-44531 | NONE0 | nodejs-doc 10.24.0~dfsg-1~deb10u1 No fix yet | 8.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-32021 | NONE0 | git-man 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u9 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-29458 | NONE0 | libncurses-dev 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u3 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-29458 | NONE0 | libncurses6 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u3 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-29458 | NONE0 | libncursesw5-dev 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u3 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-29458 | NONE0 | libncursesw6 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u3 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-29458 | NONE0 | libtinfo6 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u3 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-3743 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-3752 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-47240 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47243 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47245 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2021-47277 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47288 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47309 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47346 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47383 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47393 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-0850 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-1353 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-26365 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3202 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-33740 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-33741 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-33742 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3564 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-41858 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48701 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48738 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48757 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48760 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1380 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.289-1 | 16.5% High Exploitation Risk | Not Applicable |
| CVE-2023-1838 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-3141 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.289-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-3268 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.289-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-3567 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-4387 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52504 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52507 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52525 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52598 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52628 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-6606 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-0775 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.289-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26597 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26664 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26763 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26791 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27401 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35849 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36883 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36960 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38381 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-38560 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38599 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38621 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38659 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52502 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-29458 | NONE0 | ncurses-base 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u3 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-29458 | NONE0 | ncurses-bin 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u3 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-22600 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 6.5% Low-Moderate Risk | Not Applicable |
| CVE-2021-3640 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-39686 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-39713 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-40490 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-4083 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-4202 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-44733 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-47280 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-1048 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-1729 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-1734 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-20141 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-20422 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-23036 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.235-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-23037 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.235-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-23038 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.235-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-23039 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.235-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-23040 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.235-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-23041 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.235-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-23042 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.235-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3028 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3635 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-3649 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-48759 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0266 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-1077 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-1989 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-28466 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-35823 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.289-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-35824 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.289-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-35828 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.289-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-4244 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-4622 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-51043 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-51780 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-51781 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-51782 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52578 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52847 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-6270 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6931 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-6932 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-26654 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26974 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27020 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26852 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45886 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.289-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45919 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.289-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-33656 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-4203 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-1079 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-2002 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.289-1 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-24857 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-38204 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-33655 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-42739 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-43975 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-47356 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-20369 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-20572 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-21499 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-2503 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-43750 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-2194 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-2513 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-28772 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-3159 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-32269 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2991 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-3628 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-1073 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-0607 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-20446 | NONE0 | gir1.2-rsvg-2.0 2.44.10-2.1 fixed in 2.44.10-2.1+deb10u1 | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-34903 | NONE0 | gnupg-l10n 2.2.12-1+deb10u1 fixed in 2.2.12-1+deb10u2 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2021-37750 | NONE0 | krb5-multidev 1.17-3+deb10u1 fixed in 1.17-3+deb10u3 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-36054 | NONE0 | krb5-multidev 1.17-3+deb10u1 fixed in 1.17-3+deb10u6 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2020-19189 | NONE0 | libncurses-dev 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u4 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | libncurses-dev 6.1+20181013-2+deb10u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2020-19189 | NONE0 | libncurses6 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u4 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | libncurses6 6.1+20181013-2+deb10u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2020-19189 | NONE0 | libncursesw5-dev 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u4 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | libncursesw5-dev 6.1+20181013-2+deb10u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2020-19189 | NONE0 | libncursesw6 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u4 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | libncursesw6 6.1+20181013-2+deb10u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2020-19189 | NONE0 | libtinfo6 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u4 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | libtinfo6 6.1+20181013-2+deb10u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2020-3702 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-28711 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-28712 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-28713 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-28714 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-28715 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3772 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.235-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-38199 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-0001 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-0002 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-29900 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 3.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-29901 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 5.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-3621 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-3643 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-40982 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.289-2 | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-42895 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-30456 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-3338 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.289-1 | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2020-19189 | NONE0 | ncurses-base 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u4 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.1+20181013-2+deb10u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2020-19189 | NONE0 | ncurses-bin 6.1+20181013-2+deb10u2 fixed in 6.1+20181013-2+deb10u4 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-bin 6.1+20181013-2+deb10u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-22025 | NONE0 | nodejs-doc 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u4 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-0920 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2021-37159 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-47274 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2022-20154 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-30772 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-33203 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45863 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36016 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-1462 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-1855 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52644 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-24861 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47478 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-47547 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-39842 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-52810 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47308 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-47548 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-39189 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-39192 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-39193 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-26894 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-36516 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-46809 | NONE0 | nodejs-doc 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u4 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-35910 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48651 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-1206 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-26401 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47375 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-23960 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-1998 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-48754 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-39253 | NONE0 | git-man 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u5 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-22490 | NONE0 | git-man 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u8 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2020-21913 | NONE0 | icu-devtools 63.1-6+deb10u1 fixed in 63.1-6+deb10u2 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-modules 1.3.1-5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-modules-bin 1.3.1-5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-runtime 1.3.1-5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam0g 1.3.1-5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-12363 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-12364 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-36322 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-20320 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-28950 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-33630 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-34556 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-35477 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-3679 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2021-3732 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-3744 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-3764 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-38198 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-39633 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-4135 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-4149 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.235-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-4155 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-43389 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-44879 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-45095 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-45480 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-45868 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-46906 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46924 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46929 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-46932 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46933 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46935 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47086 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47100 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47104 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47181 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47184 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47189 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-47203 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47206 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47207 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47210 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47216 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47217 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47223 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47229 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47236 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47237 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47249 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47250 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47252 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47256 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47258 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47260 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47269 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47270 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47276 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47294 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47296 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47305 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47314 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47315 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47319 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47320 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47323 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-47330 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47337 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47340 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47343 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47344 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47345 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47347 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2021-47353 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47373 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47387 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47395 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47397 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2021-47401 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47405 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47409 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47416 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47418 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47423 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47424 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47425 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47434 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47436 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47442 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47445 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47460 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47468 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47480 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47495 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47499 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47509 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47511 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47515 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-47516 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47518 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47527 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47538 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47542 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47579 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47583 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47587 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-47588 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47602 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47606 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47611 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47612 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47617 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.235-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47619 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47620 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-0322 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-0480 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-0487 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-0617 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-0854 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-1016 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-1195 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-1198 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-1204 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-1516 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-1975 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-21123 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 6.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-21125 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 6.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-21166 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-2153 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-2318 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-2380 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-24959 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-25375 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-26373 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-26966 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-28356 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-28388 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-28389 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2873 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3107 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3111 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3524 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-3586 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-36280 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-36879 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3707 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-40768 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-41218 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-42328 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-42329 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-42703 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-4662 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-47929 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-48619 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48629 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-48630 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48636 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48641 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48659 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48671 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48687 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48688 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48693 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48704 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48708 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48710 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48711 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-48715 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48722 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48724 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48743 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-48756 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48758 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0394 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-0459 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-0615 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1074 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1095 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1637 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-20593 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.289-1 | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-2162 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-23454 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-23455 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-28328 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-2985 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3006 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31084 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.289-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-3161 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3220 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3358 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-34256 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.289-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-42754 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-42755 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-4385 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-4459 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45862 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-46343 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52429 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52443 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52449 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52470 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52477 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52486 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52527 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52528 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52566 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52567 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52574 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52577 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52583 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52587 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52601 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52606 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52607 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52615 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52619 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52622 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52623 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52646 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52650 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52670 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52675 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52683 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52686 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52693 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52698 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52699 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-52703 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52705 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52730 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52742 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52747 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52753 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52774 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52789 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52806 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52809 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52813 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52817 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52832 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-52843 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52845 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52853 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52865 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52875 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52880 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52881 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-7042 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-0340 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-0639 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-22099 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-23848 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-23849 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-23851 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-25739 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26600 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26602 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26606 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26615 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26635 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26636 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26642 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26645 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26651 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26663 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26675 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26679 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26696 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26697 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26722 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26735 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26744 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26751 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26752 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26766 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26772 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26773 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26777 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26778 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26779 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26801 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-26805 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26816 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26817 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26820 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26825 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26839 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26840 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26845 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-26851 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-26863 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26880 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-26889 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26901 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26903 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26917 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26922 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26931 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-26966 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26969 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26973 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26976 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26984 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26993 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26994 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26997 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26999 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27001 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27013 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27028 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-27046 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27059 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27074 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27077 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27078 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27388 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-27399 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27405 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-27410 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27412 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27413 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27416 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-27436 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-31076 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-33621 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35806 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35807 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35811 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-35815 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35819 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35821 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35822 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35823 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-35825 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35828 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35830 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35835 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35877 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35893 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35898 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35902 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35915 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35922 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35925 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35930 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35933 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35936 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35944 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35955 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-35960 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-35969 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-35978 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35982 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35984 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35997 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36004 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36014 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36017 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36020 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36286 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36288 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-36902 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36905 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36919 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36933 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36941 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36946 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36954 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36959 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36964 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-37356 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38549 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38558 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-38565 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-38567 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38579 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38582 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-38587 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-38589 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38598 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38607 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38612 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-38618 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-38633 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38634 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38637 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38661 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38780 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39292 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39301 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-47257 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47259 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-47267 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-47284 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47297 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47403 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47443 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47456 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47482 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2022-48697 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-52819 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26633 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26685 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35888 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35947 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35973 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-39276 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-4641 | NONE0 | login 1:4.5-1.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-37600 | NONE0 | uuid-dev 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-47238 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-2663 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-3594 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-24858 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-7169 | NONE0 | login 1:4.5-1.1 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2021-22939 | NONE0 | nodejs-doc 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u2 | 14.7% High Exploitation Risk | Not Applicable |
| CVE-2021-44532 | NONE0 | nodejs-doc 10.24.0~dfsg-1~deb10u1 No fix yet | 10.4% High Exploitation Risk | Not Applicable |
| CVE-2021-44533 | NONE0 | nodejs-doc 10.24.0~dfsg-1~deb10u1 No fix yet | 9.4% Low-Moderate Risk | Not Applicable |
| CVE-2021-47231 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-34324 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2019-20794 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-20321 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-33624 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2021-3753 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-47248 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47435 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-1205 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-33744 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-39188 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-40307 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-41850 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0458 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-0590 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1382 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1859 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1990 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-20569 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 7.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-26545 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52478 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52602 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52609 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-22386 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26671 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26859 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26874 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26878 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26923 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27419 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35809 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38596 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38601 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38613 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-45887 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.289-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-43976 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2022-20008 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-20132 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-20423 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-25258 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-20317 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-4002 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-4159 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47324 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-47603 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0494 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-48627 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-2269 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.289-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-2860 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-3212 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-3772 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-39194 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-7192 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36950 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47161 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47185 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47440 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47476 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52838 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52855 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26857 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-26875 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38559 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-28085 | NONE0 | uuid-dev 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-0812 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-3646 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-47233 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-41849 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-23920 | NONE0 | nodejs-doc 10.24.0~dfsg-1~deb10u1 fixed in 10.24.0~dfsg-1~deb10u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-16089 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-1974 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-52597 | NONE0 | linux-libc-dev 4.19.194-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-29374 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-45486 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-3655 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-38205 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-46934 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-24448 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-32296 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-33981 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.249-2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-3629 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-1513 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26764 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35935 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-29383 | NONE0 | login 1:4.5-1.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-3521 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.269-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52620 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3923 | NONE0 | linux-libc-dev 4.19.194-3 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-25815 | NONE0 | git-man 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u9 | 1.0% Theoretical Threat | Not Applicable |
| DLA-3112-1 | NONE0 | bzip2 1.0.6-9.2~deb10u1 fixed in 1.0.6-9.2~deb10u2 | — | Not Applicable |
| DLA-3482-1 | NONE0 | debian-archive-keyring 2019.1+deb10u1 fixed in 2019.1+deb10u2 | — | Not Applicable |
| DLA-3239-2 | NONE0 | git 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u6 | — | Not Applicable |
| DLA-3239-2 | NONE0 | git-man 1:2.20.1-2+deb10u3 fixed in 1:2.20.1-2+deb10u6 | — | Not Applicable |
| DLA-3357-2 | NONE0 | imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u4 | — | Not Applicable |
| DLA-3357-2 | NONE0 | imagemagick-6-common 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u4 | — | Not Applicable |
| DLA-3357-2 | NONE0 | imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u4 | — | Not Applicable |
| DLA-3112-1 | NONE0 | libbz2-1.0 1.0.6-9.2~deb10u1 fixed in 1.0.6-9.2~deb10u2 | — | Not Applicable |
| CVE-2023-51792 | NONE0 | libde265-0 1.0.3-1+b1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| DSA-5085-2 | NONE0 | libexpat1 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u4 | — | Not Applicable |
| DSA-5085-2 | NONE0 | libexpat1-dev 2.2.6-2+deb10u1 fixed in 2.2.6-2+deb10u4 | — | Not Applicable |
| DLA-3357-2 | NONE0 | libmagickcore-6-arch-config 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u4 | — | Not Applicable |
| DLA-3357-2 | NONE0 | libmagickcore-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u4 | — | Not Applicable |
| DLA-3357-2 | NONE0 | libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u4 | — | Not Applicable |
| DLA-3357-2 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u4 | — | Not Applicable |
| DLA-3357-2 | NONE0 | libmagickwand-6-headers 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u4 | — | Not Applicable |
| DLA-3357-2 | NONE0 | libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1+deb10u1 fixed in 8:6.9.10.23+dfsg-2.1+deb10u4 | — | Not Applicable |
| DLA-3114-2 | NONE0 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u2 | — | Not Applicable |
| DLA-3337-1 | NONE0 | libmariadb3 1:10.3.29-0+deb10u1 fixed in 1:10.3.38-0+deb10u1 | — | Not Applicable |
| CVE-2024-31047 | NONE0 | libopenexr-dev 2.2.1-4.1+deb10u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-31047 | NONE0 | libopenexr23 2.2.1-4.1+deb10u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| DLA-3189-1 | NONE0 | libpq-dev 11.12-0+deb10u1 fixed in 11.18-0+deb10u1 | — | Not Applicable |
| DLA-3316-1 | NONE0 | libpq-dev 11.12-0+deb10u1 fixed in 11.19-0+deb10u1 | — | Not Applicable |
| DLA-3189-1 | NONE0 | libpq5 11.12-0+deb10u1 fixed in 11.18-0+deb10u1 | — | Not Applicable |
| DLA-3316-1 | NONE0 | libpq5 11.12-0+deb10u1 fixed in 11.19-0+deb10u1 | — | Not Applicable |
| DLA-3114-2 | NONE0 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.36-0+deb10u2 | — | Not Applicable |
| DLA-3337-1 | NONE0 | mariadb-common 1:10.3.29-0+deb10u1 fixed in 1:10.3.38-0+deb10u1 | — | Not Applicable |
| DLA-3134-1 | NONE0 | tzdata 2021a-0+deb10u1 fixed in 2021a-0+deb10u7 | — | Not Applicable |
| DLA-3161-1 | NONE0 | tzdata 2021a-0+deb10u1 fixed in 2021a-0+deb10u8 | — | Not Applicable |
| DLA-3366-1 | NONE0 | tzdata 2021a-0+deb10u1 fixed in 2021a-0+deb10u10 | — | Not Applicable |
| DLA-3412-1 | NONE0 | tzdata 2021a-0+deb10u1 fixed in 2021a-0+deb10u11 | — | Not Applicable |
| DLA-3684-1 | NONE0 | tzdata 2021a-0+deb10u1 fixed in 2021a-0+deb10u12 | — | Not Applicable |
| DLA-3788-1 | NONE0 | tzdata 2021a-0+deb10u1 fixed in 2024a-0+deb10u1 | — | Not Applicable |
| CVE-2025-27789 | NONE0 | @babel/runtime 7.14.6 fixed in 7.26.10, 8.0.0-alpha.17 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-27789 | NONE0 | @babel/runtime-corejs3 7.14.0 fixed in 7.26.10, 8.0.0-alpha.17 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-106563 | NONE0 | @backstage/plugin-kubernetes-backend 0.3.13 fixed in 0.21.8 | — | Not Applicable |
| CVE-2026-106491 | NONE0 | @backstage/plugin-proxy-backend 0.2.11 fixed in 0.6.17 | — | Not Applicable |
| GHSA-2g8g-63j4-9w3r | NONE0 | @backstage/plugin-scaffolder-backend 0.14.2 fixed in 0.15.14 | — | Not Applicable |
| CVE-2026-106506 | NONE0 | @backstage/plugin-scaffolder-backend 0.14.2 fixed in 4.1.0 | — | Not Applicable |
| CVE-2026-106490 | NONE0 | @backstage/plugin-techdocs-backend 0.9.1 fixed in 2.2.4 | — | Not Applicable |
| GHSA-4jqc-jvh2-pxg9 | NONE0 | @backstage/techdocs-common 0.8.0 fixed in 0.11.16 | — | Not Applicable |
| CVE-2026-101915 | NONE0 | @grpc/grpc-js 1.3.2 fixed in 1.13.6, 1.14.5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23897 | NONE0 | apollo-server 2.21.0 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| GHSA-qm7x-rc44-rrqw | NONE0 | apollo-server 2.21.0 fixed in 2.25.3, 3.4.1 | — | Not Applicable |
| GHSA-2p3c-p3qw-69r4 | NONE0 | apollo-server 2.21.0 fixed in 2.25.4 | — | Not Applicable |
| GHSA-9q82-xgwf-vj6h | NONE0 | apollo-server-core 2.25.2 No fix yet | — | Not Applicable |
| GHSA-j5g3-5c8r-7qfx | NONE0 | apollo-server-core 2.25.2 fixed in 3.12.1, 2.26.1 | — | Not Applicable |
| GHSA-j965-2qgj-vjmq | NONE0 | aws-sdk 2.922.0 No fix yet | — | Not Applicable |
| GHSA-j965-2qgj-vjmq | NONE0 | aws-sdk 2.948.0 No fix yet | — | Not Applicable |
| GHSA-36jr-mh4h-2g58 | NONE0 | d3-color 2.0.0 fixed in 3.1.0 | — | Not Applicable |
| GHSA-h6ch-v84p-w6p9 | NONE0 | diff 1.4.0 fixed in 3.5.0 | — | Not Applicable |
| GHSA-r4q5-vmmm-2653 | NONE0 | follow-redirects 1.13.0 fixed in 1.16.0 | — | Not Applicable |
| CVE-2026-106445 | NONE0 | handlebars 4.7.7 fixed in 4.7.10 | — | Not Applicable |
| CVE-2026-106446 | NONE0 | handlebars 4.7.7 fixed in 4.7.10 | — | Not Applicable |
| GHSA-7rx3-28cr-v5wh | NONE0 | handlebars 4.7.7 fixed in 4.7.9 | — | Not Applicable |
| GHSA-442j-39wm-28r2 | NONE0 | handlebars 4.7.7 fixed in 4.7.9 | — | Not Applicable |
| GHSA-5p4m-2wfm-xmqj | NONE0 | js-yaml 3.13.1 fixed in 4.3.1, 3.15.1 | — | Not Applicable |
| GHSA-5p4m-2wfm-xmqj | NONE0 | js-yaml 3.14.1 fixed in 4.3.1, 3.15.1 | — | Not Applicable |
| GHSA-5p4m-2wfm-xmqj | NONE0 | js-yaml 4.1.0 fixed in 4.3.1, 3.15.1 | — | Not Applicable |
| NSWG-ECO-516 | NONE0 | lodash 4.17.15 fixed in >=4.17.19 | — | Not Applicable |
| NSWG-ECO-118 | NONE0 | minimatch 0.3.0 fixed in >=3.0.2 | — | Not Applicable |
| GHSA-5rrq-pxf6-6jx5 | NONE0 | node-forge 0.10.0 fixed in 1.0.0 | — | Not Applicable |
| GHSA-gf8q-jrpm-jvxq | NONE0 | node-forge 0.10.0 fixed in 1.0.0 | — | Not Applicable |
| GHSA-5rrq-pxf6-6jx5 | NONE0 | node-forge 0.8.5 fixed in 1.0.0 | — | Not Applicable |
| GHSA-gf8q-jrpm-jvxq | NONE0 | node-forge 0.8.5 fixed in 1.0.0 | — | Not Applicable |
| GHSA-wxgw-qj99-44c2 | NONE0 | node-forge 0.8.5 fixed in 0.10.0 | — | Not Applicable |
| GHSA-64g7-mvw6-v9qj | NONE0 | shelljs 0.8.4 fixed in 0.8.5 | — | Not Applicable |
| CVE-2025-12758 | NONE0 | validator 8.2.0 fixed in 13.15.22 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-56200 | NONE0 | validator 8.2.0 fixed in 13.15.20 | 0.3% Theoretical Threat | 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.