Last scanned:
This base/runtime image carries significant vulnerabilities that any image built on it would inherit; remediate them in the final image before production. The most severe inherited risk is CVE-2026-25971, a flaw that could let an app processing untrusted MSL files crash or stall due to stack exhaustion, disrupting service availability. Note: CVE-2026-25971 only applies if the application invokes ImageMagick on untrusted MSL scripts. Removing the ImageMagick packages from the final image would fully eliminate CVE-2026-25971. The wider exposed-surface count is large, but the stated severities and the absence of known exploitation keep this at a caution level rather than a blocker. Note: this is a general-purpose base/runtime image — many findings live in components that an application built on top may never load, so actual exploitability depends on the final image. For an accurate risk picture, re-scan the final application image with context.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-25971 | HIGH7.84 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-25971 | HIGH7.84 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-25971 | HIGH7.84 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-25971 | HIGH7.84 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-25971 | HIGH7.84 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-25971 | HIGH7.84 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-25971 | HIGH7.84 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-25971 | HIGH7.84 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-25971 | HIGH7.84 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-25971 | HIGH7.84 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-25971 | HIGH7.84 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-25971 | HIGH7.84 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-25971 | HIGH7.84 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6653 | HIGH7.84 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6653 | HIGH7.84 | libxml2-dev 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86805 | HIGH7 | libc-bin 2.36-9+deb12u14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | HIGH7 | libc-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | HIGH7 | libc-dev-bin 2.36-9+deb12u14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | HIGH7 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | HIGH7 | libc6 2.36-9+deb12u14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | HIGH7 | libc6 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | HIGH7 | libc6-dev 2.36-9+deb12u14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | HIGH7 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-74860 | MEDIUM6.8 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-74860 | MEDIUM6.8 | libxml2-dev 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-19499 | MEDIUM6.8 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM6.8 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM6.8 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM6.8 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-106580 | MEDIUM6.56 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106580 | MEDIUM6.56 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106580 | MEDIUM6.56 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106580 | MEDIUM6.56 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106580 | MEDIUM6.56 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106580 | MEDIUM6.56 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106580 | MEDIUM6.56 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106580 | MEDIUM6.56 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106580 | MEDIUM6.56 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106580 | MEDIUM6.56 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106580 | MEDIUM6.56 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106580 | MEDIUM6.56 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106580 | MEDIUM6.56 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107778 | MEDIUM6.5 | krb5-multidev 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM6.5 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM6.5 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM6.5 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM6.5 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM6.5 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM6.5 | libgssrpc4 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM6.5 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM6.5 | libkadm5clnt-mit12 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM6.5 | libkadm5srv-mit12 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM6.5 | libkdb5-10 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM6.5 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM6.5 | libkrb5-dev 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM6.5 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM6.5 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM6.5 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-85231 | MEDIUM6.5 | libtirpc-common 1.3.3+ds-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85231 | MEDIUM6.5 | libtirpc-dev 1.3.3+ds-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85231 | MEDIUM6.5 | libtirpc3 1.3.3+ds-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM6.3 | libattr1 1:2.5.1-4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-12345 | MEDIUM6.3 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-12345 | MEDIUM6.3 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-116149 | MEDIUM6.24 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116149 | MEDIUM6.24 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116149 | MEDIUM6.24 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116149 | MEDIUM6.24 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116149 | MEDIUM6.24 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116149 | MEDIUM6.24 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116149 | MEDIUM6.24 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116149 | MEDIUM6.24 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116149 | MEDIUM6.24 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116149 | MEDIUM6.24 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116149 | MEDIUM6.24 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116149 | MEDIUM6.24 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116149 | MEDIUM6.24 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-11822 | MEDIUM6.24 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-11824 | MEDIUM6.24 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-11822 | MEDIUM6.24 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-11824 | MEDIUM6.24 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86138 | MEDIUM6.24 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86140 | MEDIUM6.24 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86142 | MEDIUM6.24 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86144 | MEDIUM6.24 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86138 | MEDIUM6.24 | libxml2-dev 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86140 | MEDIUM6.24 | libxml2-dev 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86142 | MEDIUM6.24 | libxml2-dev 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86144 | MEDIUM6.24 | libxml2-dev 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-13757 | MEDIUM6.2 | libp11-kit0 0.24.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18938 | MEDIUM6.2 | libp11-kit0 0.24.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7458 | MEDIUM6.18 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-7458 | MEDIUM6.18 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-18090 | MEDIUM6.1 | gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18090 | MEDIUM6.1 | libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18090 | MEDIUM6.1 | libgdk-pixbuf-2.0-dev 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18090 | MEDIUM6.1 | libgdk-pixbuf2.0-bin 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18090 | MEDIUM6.1 | libgdk-pixbuf2.0-common 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-106565 | MEDIUM6 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106567 | MEDIUM6 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106573 | MEDIUM6 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106578 | MEDIUM6 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106579 | MEDIUM6 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107209 | MEDIUM6 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86420 | MEDIUM6 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86421 | MEDIUM6 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93589 | MEDIUM6 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106565 | MEDIUM6 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106567 | MEDIUM6 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106573 | MEDIUM6 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106578 | MEDIUM6 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106579 | MEDIUM6 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107209 | MEDIUM6 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86420 | MEDIUM6 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86421 | MEDIUM6 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93589 | MEDIUM6 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106565 | MEDIUM6 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106567 | MEDIUM6 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106573 | MEDIUM6 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106578 | MEDIUM6 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106579 | MEDIUM6 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107209 | MEDIUM6 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86420 | MEDIUM6 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86421 | MEDIUM6 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93589 | MEDIUM6 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106565 | MEDIUM6 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106567 | MEDIUM6 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106573 | MEDIUM6 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106578 | MEDIUM6 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106579 | MEDIUM6 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107209 | MEDIUM6 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86420 | MEDIUM6 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86421 | MEDIUM6 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93589 | MEDIUM6 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106565 | MEDIUM6 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106567 | MEDIUM6 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106573 | MEDIUM6 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106578 | MEDIUM6 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106579 | MEDIUM6 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107209 | MEDIUM6 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86420 | MEDIUM6 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86421 | MEDIUM6 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93589 | MEDIUM6 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106565 | MEDIUM6 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106567 | MEDIUM6 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106573 | MEDIUM6 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106578 | MEDIUM6 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106579 | MEDIUM6 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107209 | MEDIUM6 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86420 | MEDIUM6 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86421 | MEDIUM6 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93589 | MEDIUM6 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106565 | MEDIUM6 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106567 | MEDIUM6 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106573 | MEDIUM6 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106578 | MEDIUM6 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106579 | MEDIUM6 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107209 | MEDIUM6 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86420 | MEDIUM6 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86421 | MEDIUM6 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93589 | MEDIUM6 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106565 | MEDIUM6 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106567 | MEDIUM6 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106573 | MEDIUM6 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106578 | MEDIUM6 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106579 | MEDIUM6 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107209 | MEDIUM6 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86420 | MEDIUM6 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86421 | MEDIUM6 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93589 | MEDIUM6 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106565 | MEDIUM6 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106567 | MEDIUM6 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106573 | MEDIUM6 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106578 | MEDIUM6 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106579 | MEDIUM6 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107209 | MEDIUM6 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86420 | MEDIUM6 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86421 | MEDIUM6 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93589 | MEDIUM6 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106565 | MEDIUM6 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106567 | MEDIUM6 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106573 | MEDIUM6 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106578 | MEDIUM6 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106579 | MEDIUM6 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107209 | MEDIUM6 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86420 | MEDIUM6 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86421 | MEDIUM6 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93589 | MEDIUM6 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106565 | MEDIUM6 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106567 | MEDIUM6 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106573 | MEDIUM6 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106578 | MEDIUM6 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106579 | MEDIUM6 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107209 | MEDIUM6 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86420 | MEDIUM6 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86421 | MEDIUM6 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93589 | MEDIUM6 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106565 | MEDIUM6 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106567 | MEDIUM6 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106573 | MEDIUM6 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106578 | MEDIUM6 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106579 | MEDIUM6 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107209 | MEDIUM6 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86420 | MEDIUM6 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86421 | MEDIUM6 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93589 | MEDIUM6 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106565 | MEDIUM6 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106567 | MEDIUM6 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106573 | MEDIUM6 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106578 | MEDIUM6 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106579 | MEDIUM6 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107209 | MEDIUM6 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86420 | MEDIUM6 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86421 | MEDIUM6 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93589 | MEDIUM6 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-7210 | MEDIUM6 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-7210 | MEDIUM6 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-7210 | MEDIUM6 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-7210 | MEDIUM6 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102276 | MEDIUM6 | brace-expansion 5.0.9 fixed in 5.0.10, 3.0.7, 2.1.5, 1.1.19 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102278 | MEDIUM6 | brace-expansion 5.0.9 fixed in 5.0.11, 3.0.8, 2.1.6, 1.1.20 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109869 | MEDIUM6 | undici 6.28.0 fixed in 6.29.1, 7.30.1, 8.12.2 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-19534 | MEDIUM6 | undici 6.28.0 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-5435 | MEDIUM5.9 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.9 | libssl-dev 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.9 | libssl-dev 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.9 | libssl-dev 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.9 | libssl3 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.9 | libssl3 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.9 | libssl3 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.19.0-2+deb12u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-104844 | MEDIUM5.9 | postcss-selector-parser 7.1.4 fixed in 7.1.6, 6.1.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86143 | MEDIUM5.84 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86143 | MEDIUM5.84 | libxml2-dev 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109964 | MEDIUM5.6 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109964 | MEDIUM5.6 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109964 | MEDIUM5.6 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109964 | MEDIUM5.6 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109964 | MEDIUM5.6 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109964 | MEDIUM5.6 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109964 | MEDIUM5.6 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109964 | MEDIUM5.6 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109964 | MEDIUM5.6 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109964 | MEDIUM5.6 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109964 | MEDIUM5.6 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109964 | MEDIUM5.6 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109964 | MEDIUM5.6 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2023-39329 | MEDIUM5.52 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-39329 | MEDIUM5.52 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc6 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95512 | MEDIUM5.5 | libfreetype-dev 2.12.1+dfsg-5+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95512 | MEDIUM5.5 | libfreetype6 2.12.1+dfsg-5+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95512 | MEDIUM5.5 | libfreetype6-dev 2.12.1+dfsg-5+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM5.5 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM5.5 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libudev1 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58055 | MEDIUM5.4 | libnghttp2-14 1.52.0-1+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-16768 | MEDIUM5.3 | gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-16768 | MEDIUM5.3 | libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-16768 | MEDIUM5.3 | libgdk-pixbuf-2.0-dev 2.42.10+dfsg-1+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-16768 | MEDIUM5.3 | libgdk-pixbuf2.0-bin 2.42.10+dfsg-1+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-16768 | MEDIUM5.3 | libgdk-pixbuf2.0-common 2.42.10+dfsg-1+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM5.3 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM5.3 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM5.3 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM5.3 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM5.3 | libssl-dev 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-75806 | MEDIUM5.3 | libssl3 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-85977 | MEDIUM5.3 | libtirpc-common 1.3.3+ds-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-85977 | MEDIUM5.3 | libtirpc-dev 1.3.3+ds-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-85977 | MEDIUM5.3 | libtirpc3 1.3.3+ds-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-101910 | MEDIUM5.3 | ip-address 10.5.0 fixed in 10.5.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-101911 | MEDIUM5.3 | ip-address 10.5.0 fixed in 10.7.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-101912 | MEDIUM5.3 | ip-address 10.5.0 fixed in 10.7.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-101913 | MEDIUM5.3 | ip-address 10.5.0 fixed in 10.5.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-111997 | MEDIUM5.3 | ip-address 10.5.0 fixed in 10.7.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-106570 | MEDIUM5.2 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106577 | MEDIUM5.2 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106570 | MEDIUM5.2 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106577 | MEDIUM5.2 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106570 | MEDIUM5.2 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106577 | MEDIUM5.2 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106570 | MEDIUM5.2 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106577 | MEDIUM5.2 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106570 | MEDIUM5.2 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106577 | MEDIUM5.2 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106570 | MEDIUM5.2 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106577 | MEDIUM5.2 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106570 | MEDIUM5.2 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106577 | MEDIUM5.2 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106570 | MEDIUM5.2 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106577 | MEDIUM5.2 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106570 | MEDIUM5.2 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106577 | MEDIUM5.2 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106570 | MEDIUM5.2 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106577 | MEDIUM5.2 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106570 | MEDIUM5.2 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106577 | MEDIUM5.2 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106570 | MEDIUM5.2 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106577 | MEDIUM5.2 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106570 | MEDIUM5.2 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106577 | MEDIUM5.2 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2011-3389 | MEDIUM5.07 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2023-32570 | MEDIUM5.02 | libdav1d6 1.0.0-2+deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM5 | libbz2-1.0 1.0.8-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM5 | libbz2-dev 1.0.8-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libc-bin 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libc6 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-88373 | MEDIUM5 | libde265-0 1.0.11-1+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.9 | krb5-multidev 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc6 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.9 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.9 | libgssrpc4 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.9 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.9 | libkadm5clnt-mit12 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.9 | libkadm5srv-mit12 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.9 | libkdb5-10 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.9 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.9 | libkrb5-dev 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.9 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-85024 | MEDIUM4.72 | undici 6.28.0 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-81893 | MEDIUM4.7 | gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-81893 | MEDIUM4.7 | libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-81893 | MEDIUM4.7 | libgdk-pixbuf-2.0-dev 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-81893 | MEDIUM4.7 | libgdk-pixbuf2.0-bin 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-81893 | MEDIUM4.7 | libgdk-pixbuf2.0-common 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-39328 | MEDIUM4.67 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-39328 | MEDIUM4.67 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-10911 | MEDIUM4.67 | libxslt1-dev 1.1.35-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-10911 | MEDIUM4.67 | libxslt1.1 1.1.35-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM4.5 | libsasl2-2 2.1.28+dfsg-10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM4.5 | libsasl2-modules-db 2.1.28+dfsg-10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-88806 | MEDIUM4.5 | libx11-6 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88806 | MEDIUM4.5 | libx11-data 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88806 | MEDIUM4.5 | libx11-dev 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-109924 | MEDIUM4.5 | undici 6.28.0 fixed in 6.29.1, 7.30.1, 8.12.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2009-3546 | MEDIUM4.48 | libwmf-0.2-7 0.2.12-5.1 No fix yet | 10.2% High Exploitation Risk | Directly Exposed |
| CVE-2009-3546 | MEDIUM4.48 | libwmf-dev 0.2.12-5.1 No fix yet | 10.2% High Exploitation Risk | Directly Exposed |
| CVE-2009-3546 | MEDIUM4.48 | libwmflite-0.2-7 0.2.12-5.1 No fix yet | 10.2% High Exploitation Risk | Directly Exposed |
| CVE-2026-106571 | MEDIUM4.4 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86423 | MEDIUM4.4 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86425 | MEDIUM4.4 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106571 | MEDIUM4.4 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86423 | MEDIUM4.4 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86425 | MEDIUM4.4 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106571 | MEDIUM4.4 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86423 | MEDIUM4.4 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86425 | MEDIUM4.4 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106571 | MEDIUM4.4 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86423 | MEDIUM4.4 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86425 | MEDIUM4.4 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106571 | MEDIUM4.4 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86423 | MEDIUM4.4 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86425 | MEDIUM4.4 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106571 | MEDIUM4.4 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86423 | MEDIUM4.4 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86425 | MEDIUM4.4 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106571 | MEDIUM4.4 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86423 | MEDIUM4.4 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86425 | MEDIUM4.4 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106571 | MEDIUM4.4 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86423 | MEDIUM4.4 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86425 | MEDIUM4.4 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106571 | MEDIUM4.4 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86423 | MEDIUM4.4 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86425 | MEDIUM4.4 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106571 | MEDIUM4.4 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86423 | MEDIUM4.4 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86425 | MEDIUM4.4 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106571 | MEDIUM4.4 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86423 | MEDIUM4.4 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86425 | MEDIUM4.4 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106571 | MEDIUM4.4 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86423 | MEDIUM4.4 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86425 | MEDIUM4.4 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106571 | MEDIUM4.4 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86423 | MEDIUM4.4 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86425 | MEDIUM4.4 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-50812 | MEDIUM4.4 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-50813 | MEDIUM4.4 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-50812 | MEDIUM4.4 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-50813 | MEDIUM4.4 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-76781 | MEDIUM4.4 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-76781 | MEDIUM4.4 | libxml2-dev 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-11940 | MEDIUM4.38 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | MEDIUM4.38 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | MEDIUM4.26 | libacl1 2.3.1-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM4.26 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM4.26 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM4.26 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM4.26 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102635 | MEDIUM4.24 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106568 | MEDIUM4.24 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106572 | MEDIUM4.24 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107208 | MEDIUM4.24 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107210 | MEDIUM4.24 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109259 | MEDIUM4.24 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109262 | MEDIUM4.24 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109265 | MEDIUM4.24 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109269 | MEDIUM4.24 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109276 | MEDIUM4.24 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116141 | MEDIUM4.24 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116152 | MEDIUM4.24 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116154 | MEDIUM4.24 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116155 | MEDIUM4.24 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-64685 | MEDIUM4.24 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102635 | MEDIUM4.24 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106568 | MEDIUM4.24 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106572 | MEDIUM4.24 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107208 | MEDIUM4.24 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107210 | MEDIUM4.24 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109259 | MEDIUM4.24 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109262 | MEDIUM4.24 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109265 | MEDIUM4.24 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109269 | MEDIUM4.24 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109276 | MEDIUM4.24 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116141 | MEDIUM4.24 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116152 | MEDIUM4.24 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116154 | MEDIUM4.24 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116155 | MEDIUM4.24 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-64685 | MEDIUM4.24 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102635 | MEDIUM4.24 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106568 | MEDIUM4.24 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106572 | MEDIUM4.24 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107208 | MEDIUM4.24 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107210 | MEDIUM4.24 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109259 | MEDIUM4.24 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109262 | MEDIUM4.24 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109265 | MEDIUM4.24 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109269 | MEDIUM4.24 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109276 | MEDIUM4.24 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116141 | MEDIUM4.24 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116152 | MEDIUM4.24 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116154 | MEDIUM4.24 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116155 | MEDIUM4.24 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-64685 | MEDIUM4.24 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102635 | MEDIUM4.24 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106568 | MEDIUM4.24 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106572 | MEDIUM4.24 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107208 | MEDIUM4.24 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107210 | MEDIUM4.24 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109259 | MEDIUM4.24 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109262 | MEDIUM4.24 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109265 | MEDIUM4.24 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109269 | MEDIUM4.24 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109276 | MEDIUM4.24 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116141 | MEDIUM4.24 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116152 | MEDIUM4.24 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116154 | MEDIUM4.24 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116155 | MEDIUM4.24 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-64685 | MEDIUM4.24 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102635 | MEDIUM4.24 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106568 | MEDIUM4.24 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106572 | MEDIUM4.24 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107208 | MEDIUM4.24 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107210 | MEDIUM4.24 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109259 | MEDIUM4.24 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109262 | MEDIUM4.24 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109265 | MEDIUM4.24 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109269 | MEDIUM4.24 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109276 | MEDIUM4.24 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116141 | MEDIUM4.24 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116152 | MEDIUM4.24 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116154 | MEDIUM4.24 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116155 | MEDIUM4.24 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-64685 | MEDIUM4.24 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102635 | MEDIUM4.24 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106568 | MEDIUM4.24 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106572 | MEDIUM4.24 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107208 | MEDIUM4.24 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107210 | MEDIUM4.24 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109259 | MEDIUM4.24 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109262 | MEDIUM4.24 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109265 | MEDIUM4.24 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109269 | MEDIUM4.24 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109276 | MEDIUM4.24 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116141 | MEDIUM4.24 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116152 | MEDIUM4.24 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116154 | MEDIUM4.24 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116155 | MEDIUM4.24 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-64685 | MEDIUM4.24 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102635 | MEDIUM4.24 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106568 | MEDIUM4.24 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106572 | MEDIUM4.24 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107208 | MEDIUM4.24 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107210 | MEDIUM4.24 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109259 | MEDIUM4.24 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109262 | MEDIUM4.24 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109265 | MEDIUM4.24 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109269 | MEDIUM4.24 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109276 | MEDIUM4.24 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116141 | MEDIUM4.24 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116152 | MEDIUM4.24 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116154 | MEDIUM4.24 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116155 | MEDIUM4.24 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-64685 | MEDIUM4.24 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102635 | MEDIUM4.24 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106568 | MEDIUM4.24 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106572 | MEDIUM4.24 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107208 | MEDIUM4.24 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107210 | MEDIUM4.24 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109259 | MEDIUM4.24 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109262 | MEDIUM4.24 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109265 | MEDIUM4.24 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109269 | MEDIUM4.24 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109276 | MEDIUM4.24 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116141 | MEDIUM4.24 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116152 | MEDIUM4.24 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116154 | MEDIUM4.24 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116155 | MEDIUM4.24 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-64685 | MEDIUM4.24 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102635 | MEDIUM4.24 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106568 | MEDIUM4.24 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106572 | MEDIUM4.24 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107208 | MEDIUM4.24 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107210 | MEDIUM4.24 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109259 | MEDIUM4.24 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109262 | MEDIUM4.24 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109265 | MEDIUM4.24 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109269 | MEDIUM4.24 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109276 | MEDIUM4.24 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116141 | MEDIUM4.24 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116152 | MEDIUM4.24 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116154 | MEDIUM4.24 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116155 | MEDIUM4.24 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-64685 | MEDIUM4.24 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102635 | MEDIUM4.24 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106568 | MEDIUM4.24 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106572 | MEDIUM4.24 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107208 | MEDIUM4.24 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107210 | MEDIUM4.24 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109259 | MEDIUM4.24 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109262 | MEDIUM4.24 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109265 | MEDIUM4.24 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109269 | MEDIUM4.24 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109276 | MEDIUM4.24 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116141 | MEDIUM4.24 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116152 | MEDIUM4.24 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116154 | MEDIUM4.24 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116155 | MEDIUM4.24 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-64685 | MEDIUM4.24 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102635 | MEDIUM4.24 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106568 | MEDIUM4.24 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106572 | MEDIUM4.24 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107208 | MEDIUM4.24 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107210 | MEDIUM4.24 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109259 | MEDIUM4.24 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109262 | MEDIUM4.24 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109265 | MEDIUM4.24 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109269 | MEDIUM4.24 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109276 | MEDIUM4.24 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116141 | MEDIUM4.24 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116152 | MEDIUM4.24 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116154 | MEDIUM4.24 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116155 | MEDIUM4.24 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-64685 | MEDIUM4.24 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102635 | MEDIUM4.24 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106568 | MEDIUM4.24 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106572 | MEDIUM4.24 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107208 | MEDIUM4.24 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107210 | MEDIUM4.24 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109259 | MEDIUM4.24 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109262 | MEDIUM4.24 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109265 | MEDIUM4.24 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109269 | MEDIUM4.24 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109276 | MEDIUM4.24 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116141 | MEDIUM4.24 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116152 | MEDIUM4.24 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116154 | MEDIUM4.24 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116155 | MEDIUM4.24 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-64685 | MEDIUM4.24 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102635 | MEDIUM4.24 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106568 | MEDIUM4.24 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106572 | MEDIUM4.24 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107208 | MEDIUM4.24 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107210 | MEDIUM4.24 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109259 | MEDIUM4.24 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109262 | MEDIUM4.24 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109265 | MEDIUM4.24 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109269 | MEDIUM4.24 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109276 | MEDIUM4.24 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116141 | MEDIUM4.24 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116152 | MEDIUM4.24 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116154 | MEDIUM4.24 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116155 | MEDIUM4.24 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-64685 | MEDIUM4.24 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102277 | MEDIUM4.24 | brace-expansion 5.0.9 fixed in 5.0.12, 3.0.9, 2.1.7, 1.1.21 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-19542 | MEDIUM4.2 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107080 | MEDIUM4 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | — | Directly Exposed |
| CVE-2026-107080 | MEDIUM4 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | — | Directly Exposed |
| CVE-2026-114583 | MEDIUM4 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-114583 | MEDIUM4 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94283 | LOW3.9 | libx11-6 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94283 | LOW3.9 | libx11-data 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94283 | LOW3.9 | libx11-dev 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | LOW3.9 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.9 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW3.9 | binutils-common 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | LOW3.9 | binutils-common 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | LOW3.9 | binutils-common 2.40-2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | LOW3.9 | binutils-common 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | LOW3.9 | binutils-common 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-66864 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19548 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90801 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90802 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90803 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90804 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90829 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90830 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90831 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91779 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91780 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91782 | LOW3.9 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW3.9 | krb5-multidev 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW3.9 | krb5-multidev 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW3.9 | krb5-multidev 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | LOW3.9 | libbinutils 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | LOW3.9 | libbinutils 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | LOW3.9 | libbinutils 2.40-2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | LOW3.9 | libbinutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | LOW3.9 | libbinutils 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-66864 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19548 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90801 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90802 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90803 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90804 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90829 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90830 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90831 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91779 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91780 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91782 | LOW3.9 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc6-dev 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc6-dev 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc6-dev 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc6-dev 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc6-dev 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc6-dev 2.36-9+deb12u14 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc6-dev 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | LOW3.9 | libcairo-gobject2 1.16.0-7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | LOW3.9 | libcairo-gobject2 1.16.0-7 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6461 | LOW3.9 | libcairo-gobject2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6462 | LOW3.9 | libcairo-gobject2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | LOW3.9 | libcairo-script-interpreter2 1.16.0-7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | LOW3.9 | libcairo-script-interpreter2 1.16.0-7 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6461 | LOW3.9 | libcairo-script-interpreter2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6462 | LOW3.9 | libcairo-script-interpreter2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | LOW3.9 | libcairo2 1.16.0-7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | LOW3.9 | libcairo2 1.16.0-7 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6461 | LOW3.9 | libcairo2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6462 | LOW3.9 | libcairo2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | LOW3.9 | libcairo2-dev 1.16.0-7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | LOW3.9 | libcairo2-dev 1.16.0-7 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6461 | LOW3.9 | libcairo2-dev 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6462 | LOW3.9 | libcairo2-dev 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-66864 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19548 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90801 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90802 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90803 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90804 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90829 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90830 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90831 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91779 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91780 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91782 | LOW3.9 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | LOW3.9 | libctf0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | LOW3.9 | libctf0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | LOW3.9 | libctf0 2.40-2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | LOW3.9 | libctf0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | LOW3.9 | libctf0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-66864 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19548 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90801 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90802 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90803 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90804 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90829 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90830 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90831 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91779 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91780 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91782 | LOW3.9 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-61147 | LOW3.9 | libde265-0 1.0.11-1+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-6829 | LOW3.9 | libgcrypt20 1.10.1-3+deb12u1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | LOW3.9 | libgcrypt20 1.10.1-3+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-67693 | LOW3.9 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88647 | LOW3.9 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88648 | LOW3.9 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95184 | LOW3.9 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-66864 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19548 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90801 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90802 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90803 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90804 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90829 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90830 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90831 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91779 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91780 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91782 | LOW3.9 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW3.9 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW3.9 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW3.9 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW3.9 | libgssrpc4 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW3.9 | libgssrpc4 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW3.9 | libgssrpc4 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-9937 | LOW3.9 | libjbig-dev 2.1-6.1 No fix yet | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2017-9937 | LOW3.9 | libjbig0 2.1-6.1 No fix yet | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | LOW3.9 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW3.9 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW3.9 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW3.9 | libkadm5clnt-mit12 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW3.9 | libkadm5clnt-mit12 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW3.9 | libkadm5clnt-mit12 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW3.9 | libkadm5srv-mit12 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW3.9 | libkadm5srv-mit12 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW3.9 | libkadm5srv-mit12 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW3.9 | libkdb5-10 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW3.9 | libkdb5-10 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW3.9 | libkdb5-10 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW3.9 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW3.9 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW3.9 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW3.9 | libkrb5-dev 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW3.9 | libkrb5-dev 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW3.9 | libkrb5-dev 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW3.9 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW3.9 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW3.9 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2016-10505 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9113 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9114 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9115 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9116 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9117 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9580 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9581 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2018-16376 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6988 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2016-10505 | LOW3.9 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9113 | LOW3.9 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9114 | LOW3.9 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9115 | LOW3.9 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9116 | LOW3.9 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9117 | LOW3.9 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9580 | LOW3.9 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9581 | LOW3.9 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2018-16376 | LOW3.9 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6988 | LOW3.9 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2025-28162 | LOW3.9 | libpng-dev 1.6.39-2+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-28164 | LOW3.9 | libpng-dev 1.6.39-2+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | LOW3.9 | libpng-dev 1.6.39-2+deb12u6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-28162 | LOW3.9 | libpng16-16 1.6.39-2+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-28164 | LOW3.9 | libpng16-16 1.6.39-2+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | LOW3.9 | libpng16-16 1.6.39-2+deb12u6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-12003 | LOW3.9 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-12003 | LOW3.9 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2007-3476 | LOW3.9 | libwmf-0.2-7 0.2.12-5.1 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3477 | LOW3.9 | libwmf-0.2-7 0.2.12-5.1 No fix yet | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3996 | LOW3.9 | libwmf-0.2-7 0.2.12-5.1 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3476 | LOW3.9 | libwmf-dev 0.2.12-5.1 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3477 | LOW3.9 | libwmf-dev 0.2.12-5.1 No fix yet | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3996 | LOW3.9 | libwmf-dev 0.2.12-5.1 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3476 | LOW3.9 | libwmflite-0.2-7 0.2.12-5.1 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3477 | LOW3.9 | libwmflite-0.2-7 0.2.12-5.1 No fix yet | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3996 | LOW3.9 | libwmflite-0.2-7 0.2.12-5.1 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2015-9019 | LOW3.9 | libxslt1-dev 1.1.35-1+deb12u4 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2015-9019 | LOW3.9 | libxslt1.1 1.1.35-1+deb12u4 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-109275 | LOW3.84 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109275 | LOW3.84 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109275 | LOW3.84 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109275 | LOW3.84 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109275 | LOW3.84 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109275 | LOW3.84 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109275 | LOW3.84 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109275 | LOW3.84 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109275 | LOW3.84 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109275 | LOW3.84 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109275 | LOW3.84 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109275 | LOW3.84 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109275 | LOW3.84 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54370 | LOW3.78 | libacl1 2.3.1-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-12345 | LOW3.78 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12345 | LOW3.78 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-62343 | LOW3.76 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62946 | LOW3.76 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62343 | LOW3.76 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62946 | LOW3.76 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62343 | LOW3.76 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62946 | LOW3.76 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62343 | LOW3.76 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62946 | LOW3.76 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62343 | LOW3.76 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62946 | LOW3.76 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62343 | LOW3.76 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62946 | LOW3.76 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62343 | LOW3.76 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62946 | LOW3.76 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62343 | LOW3.76 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62946 | LOW3.76 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62343 | LOW3.76 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62946 | LOW3.76 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62343 | LOW3.76 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62946 | LOW3.76 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62343 | LOW3.76 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62946 | LOW3.76 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62343 | LOW3.76 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62946 | LOW3.76 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62343 | LOW3.76 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-62946 | LOW3.76 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2011-3374 | LOW3.7 | libapt-pkg6.0 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.7 | libssl-dev 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.7 | libssl3 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-39327 | LOW3.65 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-39327 | LOW3.65 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | LOW3.54 | openssl 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-75805 | LOW3.54 | openssl 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-77696 | LOW3.54 | openssl 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-6879 | LOW3.53 | libaom3 3.6.0-1+deb12u3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42217 | LOW3.53 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42217 | LOW3.53 | libopenexr-dev 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-45853 | LOW3.53 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 3.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-45853 | LOW3.53 | zlib1g-dev 1:1.2.13.dfsg-1 No fix yet | 3.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-106566 | LOW3.52 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109281 | LOW3.52 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106566 | LOW3.52 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109281 | LOW3.52 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106566 | LOW3.52 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109281 | LOW3.52 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106566 | LOW3.52 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109281 | LOW3.52 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106566 | LOW3.52 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109281 | LOW3.52 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106566 | LOW3.52 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109281 | LOW3.52 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106566 | LOW3.52 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109281 | LOW3.52 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106566 | LOW3.52 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109281 | LOW3.52 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106566 | LOW3.52 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109281 | LOW3.52 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106566 | LOW3.52 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109281 | LOW3.52 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106566 | LOW3.52 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109281 | LOW3.52 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106566 | LOW3.52 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109281 | LOW3.52 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-106566 | LOW3.52 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109281 | LOW3.52 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93588 | LOW3.44 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93588 | LOW3.44 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93588 | LOW3.44 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93588 | LOW3.44 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93588 | LOW3.44 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93588 | LOW3.44 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93588 | LOW3.44 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93588 | LOW3.44 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93588 | LOW3.44 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93588 | LOW3.44 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93588 | LOW3.44 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93588 | LOW3.44 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93588 | LOW3.44 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-7709 | LOW3.4 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-7709 | LOW3.4 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-60002 | LOW3.38 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-105083 | LOW3.36 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-105083 | LOW3.36 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-105083 | LOW3.36 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-105083 | LOW3.36 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-105083 | LOW3.36 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-105083 | LOW3.36 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-105083 | LOW3.36 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-105083 | LOW3.36 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-105083 | LOW3.36 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-105083 | LOW3.36 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-105083 | LOW3.36 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-105083 | LOW3.36 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-105083 | LOW3.36 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-111497 | LOW3.35 | libbrotli-dev 1.0.9-2+b6 fixed in 1.0.9-2+deb12u1 | 36.0% High Exploitation Risk | Post-Exploit |
| CVE-2026-111497 | LOW3.35 | libbrotli1 1.0.9-2+b6 fixed in 1.0.9-2+deb12u1 | 36.0% High Exploitation Risk | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW3.31 | krb5-multidev 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | LOW3.31 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | LOW3.31 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | LOW3.31 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.31 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | LOW3.31 | libelf1 0.188-2.1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1365 | LOW3.31 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | LOW3.31 | libelf1 0.188-2.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1372 | LOW3.31 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | LOW3.31 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | LOW3.31 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | LOW3.31 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW3.31 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW3.31 | libgssrpc4 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW3.31 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW3.31 | libkadm5clnt-mit12 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW3.31 | libkadm5srv-mit12 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW3.31 | libkdb5-10 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW3.31 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW3.31 | libkrb5-dev 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW3.31 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-37769 | LOW3.31 | libpixman-1-0 0.42.2-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-37769 | LOW3.31 | libpixman-1-dev 0.42.2-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | LOW3.31 | libpng-dev 1.6.39-2+deb12u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | LOW3.31 | libpng16-16 1.6.39-2+deb12u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-94284 | LOW3.3 | libx11-6 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94284 | LOW3.3 | libx11-data 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94284 | LOW3.3 | libx11-dev 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-115207 | LOW3.3 | patch 2.7.6-7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW3.3 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW3.3 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW3.3 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW3.3 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW3.3 | binutils-common 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW3.3 | binutils-common 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW3.3 | binutils-common 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW3.3 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW3.3 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW3.3 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91781 | LOW3.3 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW3.3 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW3.3 | libbinutils 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW3.3 | libbinutils 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW3.3 | libbinutils 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW3.3 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW3.3 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW3.3 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91781 | LOW3.3 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW3.3 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW3.3 | libctf-nobfd0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW3.3 | libctf-nobfd0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW3.3 | libctf-nobfd0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW3.3 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW3.3 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW3.3 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91781 | LOW3.3 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW3.3 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW3.3 | libctf0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW3.3 | libctf0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW3.3 | libctf0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW3.3 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW3.3 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW3.3 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91781 | LOW3.3 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW3.3 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW3.3 | libgprofng0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW3.3 | libgprofng0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW3.3 | libgprofng0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW3.3 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW3.3 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW3.3 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91781 | LOW3.3 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW3.3 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW3.3 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libudev1 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | LOW3.28 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58016 | LOW3.28 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58016 | LOW3.28 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58016 | LOW3.28 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58016 | LOW3.28 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-5841 | LOW3.28 | libopenexr-3-1-30 3.1.5-5 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42216 | LOW3.28 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-5841 | LOW3.28 | libopenexr-dev 3.1.5-5 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42216 | LOW3.28 | libopenexr-dev 3.1.5-5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-109266 | LOW3.2 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116142 | LOW3.2 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116145 | LOW3.2 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109266 | LOW3.2 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116142 | LOW3.2 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116145 | LOW3.2 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109266 | LOW3.2 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116142 | LOW3.2 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116145 | LOW3.2 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109266 | LOW3.2 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116142 | LOW3.2 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116145 | LOW3.2 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109266 | LOW3.2 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116142 | LOW3.2 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116145 | LOW3.2 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109266 | LOW3.2 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116142 | LOW3.2 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116145 | LOW3.2 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109266 | LOW3.2 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116142 | LOW3.2 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116145 | LOW3.2 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109266 | LOW3.2 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116142 | LOW3.2 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116145 | LOW3.2 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109266 | LOW3.2 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116142 | LOW3.2 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116145 | LOW3.2 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109266 | LOW3.2 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116142 | LOW3.2 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116145 | LOW3.2 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109266 | LOW3.2 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116142 | LOW3.2 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116145 | LOW3.2 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109266 | LOW3.2 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116142 | LOW3.2 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116145 | LOW3.2 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109266 | LOW3.2 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116142 | LOW3.2 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116145 | LOW3.2 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-75806 | LOW3.18 | openssl 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-12781 | LOW3.18 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW3.18 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW3.18 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW3.18 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-32740 | LOW3.17 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-85746 | LOW3.17 | libmariadb-dev 1:10.11.19-0+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-92262 | LOW3.17 | libmariadb-dev 1:10.11.19-0+deb12u1 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-97380 | LOW3.17 | libmariadb-dev 1:10.11.19-0+deb12u1 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-85746 | LOW3.17 | libmariadb-dev-compat 1:10.11.19-0+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-92262 | LOW3.17 | libmariadb-dev-compat 1:10.11.19-0+deb12u1 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-97380 | LOW3.17 | libmariadb-dev-compat 1:10.11.19-0+deb12u1 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-85746 | LOW3.17 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-92262 | LOW3.17 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-97380 | LOW3.17 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-41142 | LOW3.17 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41142 | LOW3.17 | libopenexr-dev 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-16742 | LOW3.17 | libsystemd0 252.39-1~deb12u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-16742 | LOW3.17 | libudev1 252.39-1~deb12u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-85746 | LOW3.17 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-92262 | LOW3.17 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-97380 | LOW3.17 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW3.15 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2008-3134 | LOW3.12 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2016-8678 | LOW3.12 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11754 | LOW3.12 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11755 | LOW3.12 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-7275 | LOW3.12 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2018-15607 | LOW3.12 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | LOW3.12 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2008-3134 | LOW3.12 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2016-8678 | LOW3.12 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11754 | LOW3.12 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11755 | LOW3.12 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-7275 | LOW3.12 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2018-15607 | LOW3.12 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | LOW3.12 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2008-3134 | LOW3.12 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2016-8678 | LOW3.12 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11754 | LOW3.12 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11755 | LOW3.12 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-7275 | LOW3.12 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2018-15607 | LOW3.12 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | LOW3.12 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2008-3134 | LOW3.12 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2016-8678 | LOW3.12 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11754 | LOW3.12 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11755 | LOW3.12 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-7275 | LOW3.12 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2018-15607 | LOW3.12 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | LOW3.12 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2008-3134 | LOW3.12 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2016-8678 | LOW3.12 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11754 | LOW3.12 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11755 | LOW3.12 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-7275 | LOW3.12 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2018-15607 | LOW3.12 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | LOW3.12 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2008-3134 | LOW3.12 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2016-8678 | LOW3.12 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11754 | LOW3.12 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11755 | LOW3.12 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-7275 | LOW3.12 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2018-15607 | LOW3.12 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | LOW3.12 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2008-3134 | LOW3.12 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2016-8678 | LOW3.12 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11754 | LOW3.12 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11755 | LOW3.12 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-7275 | LOW3.12 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2018-15607 | LOW3.12 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | LOW3.12 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2008-3134 | LOW3.12 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2016-8678 | LOW3.12 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11754 | LOW3.12 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11755 | LOW3.12 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-7275 | LOW3.12 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2018-15607 | LOW3.12 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | LOW3.12 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2008-3134 | LOW3.12 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2016-8678 | LOW3.12 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11754 | LOW3.12 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11755 | LOW3.12 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-7275 | LOW3.12 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2018-15607 | LOW3.12 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | LOW3.12 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2008-3134 | LOW3.12 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2016-8678 | LOW3.12 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11754 | LOW3.12 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11755 | LOW3.12 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-7275 | LOW3.12 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2018-15607 | LOW3.12 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | LOW3.12 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2008-3134 | LOW3.12 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2016-8678 | LOW3.12 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11754 | LOW3.12 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11755 | LOW3.12 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-7275 | LOW3.12 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2018-15607 | LOW3.12 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | LOW3.12 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2008-3134 | LOW3.12 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2016-8678 | LOW3.12 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11754 | LOW3.12 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11755 | LOW3.12 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-7275 | LOW3.12 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2018-15607 | LOW3.12 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | LOW3.12 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2008-3134 | LOW3.12 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2016-8678 | LOW3.12 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11754 | LOW3.12 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-11755 | LOW3.12 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-7275 | LOW3.12 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2018-15607 | LOW3.12 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | LOW3.12 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2021-45346 | LOW3.12 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 1.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2021-45346 | LOW3.12 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 1.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-11979 | LOW3.12 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-11979 | LOW3.12 | libxml2-dev 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-58014 | LOW3.1 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-58014 | LOW3.1 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-58014 | LOW3.1 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-58014 | LOW3.1 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-58014 | LOW3.1 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-94285 | LOW3.06 | libx11-6 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94285 | LOW3.06 | libx11-data 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94285 | LOW3.06 | libx11-dev 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107818 | LOW3.02 | libmariadb-dev 1:10.11.19-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-107818 | LOW3.02 | libmariadb-dev-compat 1:10.11.19-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-107818 | LOW3.02 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-107818 | LOW3.02 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | LOW3 | bzip2 1.0.8-5+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-88807 | LOW2.99 | libxrender-dev 1:0.9.10-1.1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-88807 | LOW2.99 | libxrender1 1:0.9.10-1.1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-109260 | LOW2.96 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109261 | LOW2.96 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109263 | LOW2.96 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109264 | LOW2.96 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109268 | LOW2.96 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109271 | LOW2.96 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116146 | LOW2.96 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116151 | LOW2.96 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109260 | LOW2.96 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109261 | LOW2.96 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109263 | LOW2.96 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109264 | LOW2.96 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109268 | LOW2.96 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109271 | LOW2.96 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116146 | LOW2.96 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116151 | LOW2.96 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109260 | LOW2.96 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109261 | LOW2.96 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109263 | LOW2.96 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109264 | LOW2.96 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109268 | LOW2.96 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109271 | LOW2.96 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116146 | LOW2.96 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116151 | LOW2.96 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109260 | LOW2.96 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109261 | LOW2.96 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109263 | LOW2.96 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109264 | LOW2.96 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109268 | LOW2.96 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109271 | LOW2.96 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116146 | LOW2.96 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116151 | LOW2.96 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109260 | LOW2.96 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109261 | LOW2.96 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109263 | LOW2.96 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109264 | LOW2.96 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109268 | LOW2.96 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109271 | LOW2.96 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116146 | LOW2.96 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116151 | LOW2.96 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109260 | LOW2.96 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109261 | LOW2.96 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109263 | LOW2.96 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109264 | LOW2.96 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109268 | LOW2.96 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109271 | LOW2.96 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116146 | LOW2.96 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116151 | LOW2.96 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109260 | LOW2.96 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109261 | LOW2.96 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109263 | LOW2.96 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109264 | LOW2.96 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109268 | LOW2.96 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109271 | LOW2.96 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116146 | LOW2.96 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116151 | LOW2.96 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109260 | LOW2.96 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109261 | LOW2.96 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109263 | LOW2.96 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109264 | LOW2.96 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109268 | LOW2.96 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109271 | LOW2.96 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116146 | LOW2.96 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116151 | LOW2.96 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109260 | LOW2.96 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109261 | LOW2.96 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109263 | LOW2.96 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109264 | LOW2.96 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109268 | LOW2.96 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109271 | LOW2.96 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116146 | LOW2.96 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116151 | LOW2.96 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109260 | LOW2.96 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109261 | LOW2.96 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109263 | LOW2.96 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109264 | LOW2.96 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109268 | LOW2.96 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109271 | LOW2.96 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116146 | LOW2.96 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116151 | LOW2.96 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109260 | LOW2.96 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109261 | LOW2.96 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109263 | LOW2.96 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109264 | LOW2.96 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109268 | LOW2.96 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109271 | LOW2.96 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116146 | LOW2.96 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116151 | LOW2.96 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109260 | LOW2.96 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109261 | LOW2.96 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109263 | LOW2.96 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109264 | LOW2.96 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109268 | LOW2.96 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109271 | LOW2.96 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116146 | LOW2.96 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116151 | LOW2.96 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109260 | LOW2.96 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109261 | LOW2.96 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109263 | LOW2.96 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109264 | LOW2.96 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109268 | LOW2.96 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109271 | LOW2.96 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116146 | LOW2.96 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116151 | LOW2.96 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-18540 | LOW2.96 | undici 6.28.0 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-77214 | LOW2.95 | libexpat1 2.5.0-1+deb12u4 fixed in 2.5.0-1+deb12u5 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-77214 | LOW2.95 | libexpat1-dev 2.5.0-1+deb12u4 fixed in 2.5.0-1+deb12u5 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58010 | LOW2.95 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58012 | LOW2.95 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58013 | LOW2.95 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58010 | LOW2.95 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58012 | LOW2.95 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58013 | LOW2.95 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58010 | LOW2.95 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58012 | LOW2.95 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58013 | LOW2.95 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58010 | LOW2.95 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58012 | LOW2.95 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58013 | LOW2.95 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58010 | LOW2.95 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58012 | LOW2.95 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58013 | LOW2.95 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | LOW2.92 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.92 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | LOW2.92 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.92 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | LOW2.92 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.92 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | LOW2.92 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.92 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41071 | LOW2.92 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-modules 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-modules-bin 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-runtime 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam0g 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-105081 | LOW2.88 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116148 | LOW2.88 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-105081 | LOW2.88 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116148 | LOW2.88 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-105081 | LOW2.88 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116148 | LOW2.88 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-105081 | LOW2.88 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116148 | LOW2.88 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-105081 | LOW2.88 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116148 | LOW2.88 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-105081 | LOW2.88 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116148 | LOW2.88 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-105081 | LOW2.88 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116148 | LOW2.88 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-105081 | LOW2.88 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116148 | LOW2.88 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-105081 | LOW2.88 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116148 | LOW2.88 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-105081 | LOW2.88 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116148 | LOW2.88 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-105081 | LOW2.88 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116148 | LOW2.88 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-105081 | LOW2.88 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116148 | LOW2.88 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-105081 | LOW2.88 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116148 | LOW2.88 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78408 | LOW2.84 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.82 | dirmngr 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.82 | gnupg 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.82 | gnupg-utils 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.82 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.82 | gpg-agent 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.82 | gpg-wks-client 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.82 | gpg-wks-server 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.82 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.82 | gpgsm 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.82 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-96889 | LOW2.81 | gir1.2-rsvg-2.0 2.54.7+dfsg-1~deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-47178 | LOW2.81 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libncurses-dev 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libncurses5-dev 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libncurses6 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libncursesw5-dev 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libncursesw6 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-12495 | LOW2.81 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-12839 | LOW2.81 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-12840 | LOW2.81 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27622 | LOW2.81 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34588 | LOW2.81 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-12495 | LOW2.81 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-12839 | LOW2.81 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-12840 | LOW2.81 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27622 | LOW2.81 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34588 | LOW2.81 | libopenexr-dev 3.1.5-5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-96889 | LOW2.81 | librsvg2-2 2.54.7+dfsg-1~deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-96889 | LOW2.81 | librsvg2-common 2.54.7+dfsg-1~deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-96889 | LOW2.81 | librsvg2-dev 2.54.7+dfsg-1~deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libtinfo6 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | ncurses-base 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | ncurses-bin 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-106583 | LOW2.81 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo-gobject2 1.16.0-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo-script-interpreter2 1.16.0-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo2 1.16.0-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo2-dev 1.16.0-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-4016 | LOW2.8 | libproc2-0 2:4.0.2-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | LOW2.77 | cpp-12 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | g++-12 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | gcc-12 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | libasan8 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | libatomic1 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | libcc1-0 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | libgcc-12-dev 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | libgomp1 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | libitm1 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | liblsan0 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-86047 | LOW2.77 | libmariadb-dev 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-86047 | LOW2.77 | libmariadb-dev-compat 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-86047 | LOW2.77 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | libquadmath0 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | libstdc++-12-dev 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | libtsan2 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | libubsan1 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-86047 | LOW2.77 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW2.7 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW2.7 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW2.7 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW2.7 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW2.7 | gzip 1.12-1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW2.7 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW2.7 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW2.7 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW2.7 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW2.7 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW2.7 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW2.7 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW2.7 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW2.7 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW2.7 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW2.7 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW2.7 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58011 | LOW2.7 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58015 | LOW2.7 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-58011 | LOW2.7 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58015 | LOW2.7 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-58011 | LOW2.7 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58015 | LOW2.7 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-58011 | LOW2.7 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58015 | LOW2.7 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-58011 | LOW2.7 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58015 | LOW2.7 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-25193 | LOW2.7 | libharfbuzz0b 6.0.0+dfsg-3 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-84450 | LOW2.7 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-84451 | LOW2.7 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-47247 | LOW2.7 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-2953 | LOW2.7 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-107815 | LOW2.7 | libmariadb-dev 1:10.11.19-0+deb12u1 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-107815 | LOW2.7 | libmariadb-dev-compat 1:10.11.19-0+deb12u1 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-107815 | LOW2.7 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-64181 | LOW2.7 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34543 | LOW2.7 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-64181 | LOW2.7 | libopenexr-dev 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34543 | LOW2.7 | libopenexr-dev 3.1.5-5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW2.7 | libperl5.36 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-52355 | LOW2.7 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-36849 | LOW2.7 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | — | Post-Exploit |
| CVE-2023-52355 | LOW2.7 | libtiff6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-36849 | LOW2.7 | libtiff6 4.5.0-6+deb12u4 No fix yet | — | Post-Exploit |
| CVE-2023-52355 | LOW2.7 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-36849 | LOW2.7 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | — | Post-Exploit |
| CVE-2026-107815 | LOW2.7 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-106553 | LOW2.7 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-106555 | LOW2.7 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59999 | LOW2.7 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-60000 | LOW2.7 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW2.7 | perl 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW2.7 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW2.7 | perl-modules-5.36 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-93748 | LOW2.7 | http-cache-semantics 4.2.0 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-84782 | LOW2.66 | libssl-dev 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-84782 | LOW2.66 | libssl3 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-84782 | LOW2.66 | openssl 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2005-0406 | LOW2.65 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-55160 | LOW2.65 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2005-0406 | LOW2.65 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-55160 | LOW2.65 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2005-0406 | LOW2.65 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-55160 | LOW2.65 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2005-0406 | LOW2.65 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-55160 | LOW2.65 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2005-0406 | LOW2.65 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-55160 | LOW2.65 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2005-0406 | LOW2.65 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-55160 | LOW2.65 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2005-0406 | LOW2.65 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-55160 | LOW2.65 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2005-0406 | LOW2.65 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-55160 | LOW2.65 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2005-0406 | LOW2.65 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-55160 | LOW2.65 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2005-0406 | LOW2.65 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-55160 | LOW2.65 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2005-0406 | LOW2.65 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-55160 | LOW2.65 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2005-0406 | LOW2.65 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-55160 | LOW2.65 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2005-0406 | LOW2.65 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-55160 | LOW2.65 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-29088 | LOW2.65 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-29088 | LOW2.65 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-18477 | LOW2.64 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.64 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-109267 | LOW2.64 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109270 | LOW2.64 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109273 | LOW2.64 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109277 | LOW2.64 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116140 | LOW2.64 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116143 | LOW2.64 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116144 | LOW2.64 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116156 | LOW2.64 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116157 | LOW2.64 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116159 | LOW2.64 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116160 | LOW2.64 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-66011 | LOW2.64 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93586 | LOW2.64 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93587 | LOW2.64 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109267 | LOW2.64 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109270 | LOW2.64 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109273 | LOW2.64 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109277 | LOW2.64 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116140 | LOW2.64 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116143 | LOW2.64 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116144 | LOW2.64 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116156 | LOW2.64 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116157 | LOW2.64 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116159 | LOW2.64 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116160 | LOW2.64 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-66011 | LOW2.64 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93586 | LOW2.64 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93587 | LOW2.64 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109267 | LOW2.64 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109270 | LOW2.64 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109273 | LOW2.64 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109277 | LOW2.64 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116140 | LOW2.64 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116143 | LOW2.64 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116144 | LOW2.64 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116156 | LOW2.64 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116157 | LOW2.64 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116159 | LOW2.64 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116160 | LOW2.64 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-66011 | LOW2.64 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93586 | LOW2.64 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93587 | LOW2.64 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109267 | LOW2.64 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109270 | LOW2.64 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109273 | LOW2.64 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109277 | LOW2.64 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116140 | LOW2.64 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116143 | LOW2.64 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116144 | LOW2.64 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116156 | LOW2.64 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116157 | LOW2.64 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116159 | LOW2.64 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116160 | LOW2.64 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-66011 | LOW2.64 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93586 | LOW2.64 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93587 | LOW2.64 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109267 | LOW2.64 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109270 | LOW2.64 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109273 | LOW2.64 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109277 | LOW2.64 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116140 | LOW2.64 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116143 | LOW2.64 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116144 | LOW2.64 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116156 | LOW2.64 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116157 | LOW2.64 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116159 | LOW2.64 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116160 | LOW2.64 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-66011 | LOW2.64 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93586 | LOW2.64 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93587 | LOW2.64 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109267 | LOW2.64 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109270 | LOW2.64 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109273 | LOW2.64 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109277 | LOW2.64 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116140 | LOW2.64 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116143 | LOW2.64 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116144 | LOW2.64 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116156 | LOW2.64 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116157 | LOW2.64 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116159 | LOW2.64 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116160 | LOW2.64 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-66011 | LOW2.64 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93586 | LOW2.64 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93587 | LOW2.64 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109267 | LOW2.64 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109270 | LOW2.64 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109273 | LOW2.64 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109277 | LOW2.64 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116140 | LOW2.64 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116143 | LOW2.64 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116144 | LOW2.64 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116156 | LOW2.64 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116157 | LOW2.64 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116159 | LOW2.64 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116160 | LOW2.64 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-66011 | LOW2.64 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93586 | LOW2.64 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93587 | LOW2.64 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109267 | LOW2.64 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109270 | LOW2.64 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109273 | LOW2.64 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109277 | LOW2.64 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116140 | LOW2.64 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116143 | LOW2.64 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116144 | LOW2.64 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116156 | LOW2.64 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116157 | LOW2.64 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116159 | LOW2.64 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116160 | LOW2.64 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-66011 | LOW2.64 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93586 | LOW2.64 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93587 | LOW2.64 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109267 | LOW2.64 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109270 | LOW2.64 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109273 | LOW2.64 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109277 | LOW2.64 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116140 | LOW2.64 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116143 | LOW2.64 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116144 | LOW2.64 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116156 | LOW2.64 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116157 | LOW2.64 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116159 | LOW2.64 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116160 | LOW2.64 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-66011 | LOW2.64 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93586 | LOW2.64 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93587 | LOW2.64 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109267 | LOW2.64 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109270 | LOW2.64 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109273 | LOW2.64 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109277 | LOW2.64 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116140 | LOW2.64 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116143 | LOW2.64 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116144 | LOW2.64 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116156 | LOW2.64 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116157 | LOW2.64 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116159 | LOW2.64 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116160 | LOW2.64 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-66011 | LOW2.64 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93586 | LOW2.64 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93587 | LOW2.64 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109267 | LOW2.64 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109270 | LOW2.64 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109273 | LOW2.64 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109277 | LOW2.64 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116140 | LOW2.64 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116143 | LOW2.64 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116144 | LOW2.64 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116156 | LOW2.64 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116157 | LOW2.64 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116159 | LOW2.64 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116160 | LOW2.64 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-66011 | LOW2.64 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93586 | LOW2.64 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93587 | LOW2.64 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109267 | LOW2.64 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109270 | LOW2.64 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109273 | LOW2.64 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109277 | LOW2.64 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116140 | LOW2.64 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116143 | LOW2.64 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116144 | LOW2.64 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116156 | LOW2.64 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116157 | LOW2.64 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116159 | LOW2.64 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116160 | LOW2.64 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-66011 | LOW2.64 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93586 | LOW2.64 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93587 | LOW2.64 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109267 | LOW2.64 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109270 | LOW2.64 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109273 | LOW2.64 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109277 | LOW2.64 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116140 | LOW2.64 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116143 | LOW2.64 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116144 | LOW2.64 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116156 | LOW2.64 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116157 | LOW2.64 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116159 | LOW2.64 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116160 | LOW2.64 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-66011 | LOW2.64 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93586 | LOW2.64 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93587 | LOW2.64 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-70873 | LOW2.64 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-70873 | LOW2.64 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-34544 | LOW2.63 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34545 | LOW2.63 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-34544 | LOW2.63 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34545 | LOW2.63 | libopenexr-dev 3.1.5-5 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-12912 | LOW2.63 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-52490 | LOW2.63 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-12912 | LOW2.63 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-52490 | LOW2.63 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-12912 | LOW2.63 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-52490 | LOW2.63 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-11940 | LOW2.63 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-11940 | LOW2.63 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW2.63 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11731 | LOW2.63 | libxslt1-dev 1.1.35-1+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11731 | LOW2.63 | libxslt1.1 1.1.35-1+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107823 | LOW2.59 | libmariadb-dev 1:10.11.19-0+deb12u1 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-107823 | LOW2.59 | libmariadb-dev-compat 1:10.11.19-0+deb12u1 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-107823 | LOW2.59 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-107823 | LOW2.59 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-16118 | LOW2.56 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-16118 | LOW2.56 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-16118 | LOW2.56 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-16118 | LOW2.56 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-16118 | LOW2.56 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68431 | LOW2.56 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-32741 | LOW2.56 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-32882 | LOW2.56 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-48029 | LOW2.56 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34379 | LOW2.56 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-40244 | LOW2.56 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-40250 | LOW2.56 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59184 | LOW2.56 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59186 | LOW2.56 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59187 | LOW2.56 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59189 | LOW2.56 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59981 | LOW2.56 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59982 | LOW2.56 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-68515 | LOW2.56 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34379 | LOW2.56 | libopenexr-dev 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-40244 | LOW2.56 | libopenexr-dev 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-40250 | LOW2.56 | libopenexr-dev 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59184 | LOW2.56 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59186 | LOW2.56 | libopenexr-dev 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59187 | LOW2.56 | libopenexr-dev 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59189 | LOW2.56 | libopenexr-dev 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59981 | LOW2.56 | libopenexr-dev 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59982 | LOW2.56 | libopenexr-dev 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-68515 | LOW2.56 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW2.56 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW2.56 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW2.56 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW2.56 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58471 | LOW2.56 | wget 1.21.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58472 | LOW2.56 | wget 1.21.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW2.52 | cpp-12 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW2.52 | g++-12 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW2.52 | gcc-12 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW2.52 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW2.52 | libasan8 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW2.52 | libatomic1 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW2.52 | libcc1-0 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW2.52 | libgcc-12-dev 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW2.52 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW2.52 | libgomp1 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW2.52 | libitm1 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW2.52 | liblsan0 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW2.52 | libquadmath0 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW2.52 | libstdc++-12-dev 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW2.52 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW2.52 | libtsan2 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW2.52 | libubsan1 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-95209 | LOW2.5 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95210 | LOW2.5 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-115557 | LOW2.5 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-115557 | LOW2.5 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| TEMP-0601525-BEBB65 | LOW2.5 | libwmf-0.2-7 0.2.12-5.1 No fix yet | — | Directly Exposed |
| TEMP-0601525-BEBB65 | LOW2.5 | libwmf-dev 0.2.12-5.1 No fix yet | — | Directly Exposed |
| TEMP-0601525-BEBB65 | LOW2.5 | libwmflite-0.2-7 0.2.12-5.1 No fix yet | — | Directly Exposed |
| CVE-2026-56132 | LOW2.48 | libexpat1 2.5.0-1+deb12u4 fixed in 2.5.0-1+deb12u5 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56132 | LOW2.48 | libexpat1-dev 2.5.0-1+deb12u4 fixed in 2.5.0-1+deb12u5 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-116150 | LOW2.48 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116150 | LOW2.48 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116150 | LOW2.48 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116150 | LOW2.48 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116150 | LOW2.48 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116150 | LOW2.48 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116150 | LOW2.48 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116150 | LOW2.48 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116150 | LOW2.48 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116150 | LOW2.48 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116150 | LOW2.48 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116150 | LOW2.48 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116150 | LOW2.48 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-1965 | LOW2.45 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-86410 | LOW2.45 | curl 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW2.45 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-86410 | LOW2.45 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW2.45 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-86410 | LOW2.45 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW2.45 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-86410 | LOW2.45 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-107821 | LOW2.41 | libmariadb-dev 1:10.11.19-0+deb12u1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-107821 | LOW2.41 | libmariadb-dev-compat 1:10.11.19-0+deb12u1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-107821 | LOW2.41 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-107821 | LOW2.41 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | dirmngr 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg-utils 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-agent 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-wks-client 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-wks-server 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgsm 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam-modules 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam-modules-bin 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam-runtime 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam0g 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-114583 | LOW2.4 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-114583 | LOW2.4 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW2.34 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW2.34 | curl 7.88.1-10+deb12u15 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5545 | LOW2.34 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW2.34 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW2.34 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-92388 | LOW2.34 | curl 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86414 | LOW2.34 | curl 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92390 | LOW2.34 | curl 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW2.34 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW2.34 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5545 | LOW2.34 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW2.34 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW2.34 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-92388 | LOW2.34 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86414 | LOW2.34 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92390 | LOW2.34 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW2.34 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW2.34 | libcurl4 7.88.1-10+deb12u15 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5545 | LOW2.34 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW2.34 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW2.34 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-92388 | LOW2.34 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86414 | LOW2.34 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92390 | LOW2.34 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW2.34 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW2.34 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5545 | LOW2.34 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW2.34 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW2.34 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-92388 | LOW2.34 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86414 | LOW2.34 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92390 | LOW2.34 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-32738 | LOW2.34 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-32739 | LOW2.34 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-32814 | LOW2.34 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41069 | LOW2.34 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-49271 | LOW2.34 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-50495 | LOW2.34 | libncurses-dev 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-50495 | LOW2.34 | libncurses5-dev 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-50495 | LOW2.34 | libncurses6 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-50495 | LOW2.34 | libncursesw5-dev 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-50495 | LOW2.34 | libncursesw6 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-53532 | LOW2.34 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-54920 | LOW2.34 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-68516 | LOW2.34 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53532 | LOW2.34 | libopenexr-dev 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-54920 | LOW2.34 | libopenexr-dev 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-68516 | LOW2.34 | libopenexr-dev 3.1.5-5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-6277 | LOW2.34 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6277 | LOW2.34 | libtiff6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6277 | LOW2.34 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-50495 | LOW2.34 | libtinfo6 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-50495 | LOW2.34 | ncurses-base 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-50495 | LOW2.34 | ncurses-bin 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-106552 | LOW2.34 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-106585 | LOW2.34 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59998 | LOW2.34 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-60001 | LOW2.34 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-10524 | LOW2.34 | wget 1.21.3-1+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-58469 | LOW2.34 | wget 1.21.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW2.34 | binutils 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW2.34 | binutils 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW2.34 | binutils 2.40-2 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW2.34 | binutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW2.34 | binutils 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-66864 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW2.34 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW2.34 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW2.34 | binutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.34 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18220 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-19548 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW2.34 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.34 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.34 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90801 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90802 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90803 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90804 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90828 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90829 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90830 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90831 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91779 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91780 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91782 | LOW2.34 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-66864 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18220 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-19548 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90801 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90802 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90803 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90804 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90828 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90829 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90830 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90831 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91779 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91780 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91782 | LOW2.34 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56391 | LOW2.34 | coreutils 9.1-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.34 | coreutils 9.1-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-102473 | LOW2.34 | dash 0.5.12-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-102474 | LOW2.34 | dash 0.5.12-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53910 | LOW2.34 | diffutils 1:3.8-4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2018-1000021 | LOW2.34 | git 1:2.39.5-0+deb12u3 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-24975 | LOW2.34 | git 1:2.39.5-0+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1687 | LOW2.34 | m4 1.4.19-3 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1688 | LOW2.34 | m4 1.4.19-3 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2010-4651 | LOW2.34 | patch 2.7.6-7 No fix yet | 4.9% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6951 | LOW2.34 | patch 2.7.6-7 No fix yet | 8.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | LOW2.34 | patch 2.7.6-7 No fix yet | 8.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-56288 | LOW2.34 | patch 2.7.6-7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56289 | LOW2.34 | patch 2.7.6-7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-12003 | LOW2.34 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-12003 | LOW2.34 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW2.34 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-109278 | LOW2.32 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109278 | LOW2.32 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109278 | LOW2.32 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109278 | LOW2.32 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109278 | LOW2.32 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109278 | LOW2.32 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109278 | LOW2.32 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109278 | LOW2.32 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109278 | LOW2.32 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109278 | LOW2.32 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109278 | LOW2.32 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109278 | LOW2.32 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109278 | LOW2.32 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107822 | LOW2.3 | libmariadb-dev 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-107822 | LOW2.3 | libmariadb-dev-compat 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-107822 | LOW2.3 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-107822 | LOW2.3 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-39616 | LOW2.29 | libaom3 3.6.0-1+deb12u3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-55373 | LOW2.23 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55373 | LOW2.23 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-35189 | LOW2.22 | openssl 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-47254 | LOW2.2 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-47714 | LOW2.2 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18495 | LOW2.2 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18495 | LOW2.2 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18495 | LOW2.2 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-31879 | LOW2.2 | wget 1.21.3-1+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-6879 | LOW2.2 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6879 | LOW2.2 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | dirmngr 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW2.16 | gnupg 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW2.16 | gnupg-utils 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW2.16 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW2.16 | gpg-agent 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW2.16 | gpg-wks-client 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW2.16 | gpg-wks-server 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW2.16 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW2.16 | gpgsm 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW2.16 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-102633 | LOW2.12 | libexpat1 2.5.0-1+deb12u4 fixed in 2.5.0-1+deb12u5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-113351 | LOW2.12 | libexpat1 2.5.0-1+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-102633 | LOW2.12 | libexpat1-dev 2.5.0-1+deb12u4 fixed in 2.5.0-1+deb12u5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-113351 | LOW2.12 | libexpat1-dev 2.5.0-1+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-15146 | LOW2.12 | wget 1.21.3-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-29070 | LOW2.12 | liblcms2-2 2.14-2+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-29070 | LOW2.12 | liblcms2-dev 2.14-2+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-27587 | LOW2.12 | libssl-dev 3.0.22-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-27587 | LOW2.12 | libssl3 3.0.22-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | LOW2.05 | libperl5.36 5.36.0-7+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl 5.36.0-7+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-modules-5.36 5.36.0-7+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-73282 | LOW2.02 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-109258 | LOW2 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109272 | LOW2 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109274 | LOW2 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109279 | LOW2 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109280 | LOW2 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109282 | LOW2 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116147 | LOW2 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116153 | LOW2 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116158 | LOW2 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86424 | LOW2 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109258 | LOW2 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109272 | LOW2 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109274 | LOW2 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109279 | LOW2 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109280 | LOW2 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109282 | LOW2 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116147 | LOW2 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116153 | LOW2 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116158 | LOW2 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86424 | LOW2 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109258 | LOW2 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109272 | LOW2 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109274 | LOW2 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109279 | LOW2 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109280 | LOW2 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109282 | LOW2 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116147 | LOW2 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116153 | LOW2 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116158 | LOW2 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86424 | LOW2 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109258 | LOW2 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109272 | LOW2 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109274 | LOW2 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109279 | LOW2 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109280 | LOW2 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109282 | LOW2 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116147 | LOW2 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116153 | LOW2 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116158 | LOW2 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86424 | LOW2 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109258 | LOW2 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109272 | LOW2 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109274 | LOW2 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109279 | LOW2 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109280 | LOW2 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109282 | LOW2 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116147 | LOW2 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116153 | LOW2 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116158 | LOW2 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86424 | LOW2 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109258 | LOW2 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109272 | LOW2 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109274 | LOW2 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109279 | LOW2 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109280 | LOW2 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109282 | LOW2 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116147 | LOW2 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116153 | LOW2 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116158 | LOW2 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86424 | LOW2 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109258 | LOW2 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109272 | LOW2 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109274 | LOW2 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109279 | LOW2 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109280 | LOW2 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109282 | LOW2 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116147 | LOW2 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116153 | LOW2 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116158 | LOW2 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86424 | LOW2 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109258 | LOW2 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109272 | LOW2 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109274 | LOW2 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109279 | LOW2 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109280 | LOW2 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109282 | LOW2 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116147 | LOW2 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116153 | LOW2 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116158 | LOW2 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86424 | LOW2 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109258 | LOW2 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109272 | LOW2 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109274 | LOW2 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109279 | LOW2 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109280 | LOW2 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109282 | LOW2 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116147 | LOW2 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116153 | LOW2 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116158 | LOW2 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86424 | LOW2 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109258 | LOW2 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109272 | LOW2 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109274 | LOW2 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109279 | LOW2 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109280 | LOW2 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109282 | LOW2 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116147 | LOW2 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116153 | LOW2 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116158 | LOW2 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86424 | LOW2 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109258 | LOW2 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109272 | LOW2 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109274 | LOW2 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109279 | LOW2 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109280 | LOW2 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109282 | LOW2 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116147 | LOW2 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116153 | LOW2 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116158 | LOW2 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86424 | LOW2 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109258 | LOW2 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109272 | LOW2 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109274 | LOW2 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109279 | LOW2 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109280 | LOW2 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109282 | LOW2 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116147 | LOW2 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116153 | LOW2 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116158 | LOW2 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86424 | LOW2 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109258 | LOW2 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109272 | LOW2 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109274 | LOW2 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109279 | LOW2 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109280 | LOW2 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109282 | LOW2 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116147 | LOW2 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116153 | LOW2 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-116158 | LOW2 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86424 | LOW2 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 fixed in 8:6.9.11.60+dfsg-1.6+deb12u14 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2021-32256 | LOW1.99 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW1.99 | binutils 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW1.99 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW1.99 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW1.99 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW1.99 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW1.99 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW1.99 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW1.99 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW1.99 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW1.99 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW1.99 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW1.99 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW1.99 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW1.99 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW1.99 | binutils 2.40-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW1.99 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW1.99 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW1.99 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW1.99 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW1.99 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW1.99 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW1.99 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW1.99 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW1.99 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW1.99 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW1.99 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW1.99 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2016-2781 | LOW1.99 | coreutils 9.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW1.99 | coreutils 9.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW1.99 | coreutils 9.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-52005 | LOW1.99 | git 1:2.39.5-0+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW1.99 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW1.99 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW1.99 | patch 2.7.6-7 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-66382 | LOW1.98 | libexpat1 2.5.0-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66382 | LOW1.98 | libexpat1-dev 2.5.0-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-47709 | LOW1.98 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55059 | LOW1.98 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55371 | LOW1.98 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59183 | LOW1.98 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59983 | LOW1.98 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59984 | LOW1.98 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59985 | LOW1.98 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-61555 | LOW1.98 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-88384 | LOW1.98 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55059 | LOW1.98 | libopenexr-dev 3.1.5-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55371 | LOW1.98 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59183 | LOW1.98 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59983 | LOW1.98 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59984 | LOW1.98 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59985 | LOW1.98 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-61555 | LOW1.98 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-88384 | LOW1.98 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27171 | LOW1.98 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27171 | LOW1.98 | zlib1g-dev 1:1.2.13.dfsg-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.98 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.98 | binutils 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.98 | binutils 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.98 | binutils 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91781 | LOW1.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91781 | LOW1.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.98 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.98 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-107816 | LOW1.94 | libmariadb-dev 1:10.11.19-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-85985 | LOW1.94 | libmariadb-dev 1:10.11.19-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-107816 | LOW1.94 | libmariadb-dev-compat 1:10.11.19-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-85985 | LOW1.94 | libmariadb-dev-compat 1:10.11.19-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-107816 | LOW1.94 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-85985 | LOW1.94 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-107816 | LOW1.94 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-85985 | LOW1.94 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59995 | LOW1.94 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59996 | LOW1.94 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59997 | LOW1.94 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-73283 | LOW1.94 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW1.91 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW1.91 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-86409 | LOW1.91 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW1.91 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW1.91 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-86409 | LOW1.91 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW1.91 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW1.91 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-86409 | LOW1.91 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW1.91 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW1.91 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-86409 | LOW1.91 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-59375 | LOW1.91 | libexpat1 2.5.0-1+deb12u4 fixed in 2.5.0-1+deb12u5 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-59375 | LOW1.91 | libexpat1-dev 2.5.0-1+deb12u4 fixed in 2.5.0-1+deb12u5 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-15588 | LOW1.91 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-86469 | LOW1.91 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-15588 | LOW1.91 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-86469 | LOW1.91 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-15588 | LOW1.91 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-86469 | LOW1.91 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-15588 | LOW1.91 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-86469 | LOW1.91 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-15588 | LOW1.91 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-86469 | LOW1.91 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22693 | LOW1.91 | libharfbuzz0b 6.0.0+dfsg-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34380 | LOW1.91 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34380 | LOW1.91 | libopenexr-dev 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | mount 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58470 | LOW1.91 | wget 1.21.3-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-50142 | LOW1.8 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-62289 | LOW1.8 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-62292 | LOW1.8 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-84384 | LOW1.8 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-84446 | LOW1.8 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-84447 | LOW1.8 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-84448 | LOW1.8 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-84449 | LOW1.8 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34589 | LOW1.8 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34589 | LOW1.8 | libopenexr-dev 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-85091 | LOW1.8 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-85091 | LOW1.8 | zlib1g-dev 1:1.2.13.dfsg-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.74 | dirmngr 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.74 | gnupg 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.74 | gnupg-utils 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.74 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.74 | gpg-agent 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.74 | gpg-wks-client 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.74 | gpg-wks-server 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.74 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.74 | gpgsm 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.74 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-107928 | LOW1.73 | curl 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-107928 | LOW1.73 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-107928 | LOW1.73 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-107928 | LOW1.73 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW1.69 | curl 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW1.69 | gzip 1.12-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW1.69 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW1.69 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW1.69 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-48074 | LOW1.68 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-48074 | LOW1.68 | libopenexr-dev 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | dirmngr 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg-utils 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-agent 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-wks-client 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-wks-server 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgsm 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-4016 | LOW1.68 | procps 2:4.0.2-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-4217 | LOW1.68 | unzip 6.0-28+deb12u1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.68 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2019-6110 | LOW1.61 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 24.9% High Exploitation Risk | Post-Exploit |
| CVE-2020-15778 | LOW1.61 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 13.7% High Exploitation Risk | Post-Exploit |
| CVE-2026-107817 | LOW1.58 | libmariadb-dev 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-107817 | LOW1.58 | libmariadb-dev-compat 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-107817 | LOW1.58 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-107817 | LOW1.58 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-44169 | LOW1.55 | libmariadb-dev 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-85745 | LOW1.55 | libmariadb-dev 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-44169 | LOW1.55 | libmariadb-dev-compat 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-85745 | LOW1.55 | libmariadb-dev-compat 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-44169 | LOW1.55 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-85745 | LOW1.55 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-44169 | LOW1.55 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-85745 | LOW1.55 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-106586 | LOW1.55 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| TEMP-0841856-B18BAF | LOW1.5 | bash 5.2.15-2+b13 No fix yet | — | Post-Exploit |
| TEMP-0628843-DBAD28 | LOW1.5 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | — | Post-Exploit |
| TEMP-0628843-DBAD28 | LOW1.5 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | — | Post-Exploit |
| CVE-2026-115557 | LOW1.5 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-115557 | LOW1.5 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| TEMP-0517018-A83CE6 | LOW1.5 | sysvinit-utils 3.06-4 No fix yet | — | Post-Exploit |
| TEMP-0290435-0B57B5 | LOW1.5 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-115506 | LOW1.44 | libexpat1 2.5.0-1+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-115506 | LOW1.44 | libexpat1-dev 2.5.0-1+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-84444 | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| TEMP-0000000-0F03E5 | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Post-Exploit |
| TEMP-0000000-153207 | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Post-Exploit |
| TEMP-0000000-18A2CE | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Post-Exploit |
| TEMP-0000000-1B5D39 | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Post-Exploit |
| TEMP-0000000-21F713 | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Post-Exploit |
| TEMP-0000000-301DE5 | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Post-Exploit |
| TEMP-0000000-415AE1 | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Post-Exploit |
| TEMP-0000000-4EF776 | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Post-Exploit |
| TEMP-0000000-5124DE | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Post-Exploit |
| TEMP-0000000-57F868 | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Post-Exploit |
| TEMP-0000000-6C5194 | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Post-Exploit |
| TEMP-0000000-78AC20 | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Post-Exploit |
| TEMP-0000000-809756 | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Post-Exploit |
| TEMP-0000000-8A4B18 | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Post-Exploit |
| TEMP-0000000-9253BB | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Post-Exploit |
| TEMP-0000000-956D99 | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Post-Exploit |
| TEMP-0000000-BBE297 | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Post-Exploit |
| TEMP-0000000-D1A721 | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Post-Exploit |
| TEMP-0000000-D2EEB5 | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Post-Exploit |
| TEMP-0000000-DB3DE2 | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Post-Exploit |
| TEMP-0000000-F2B97A | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Post-Exploit |
| TEMP-0000000-FDE8B2 | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Post-Exploit |
| TEMP-1148137-089975 | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Post-Exploit |
| TEMP-1148137-126A7B | LOW1.44 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-82560 | LOW1.44 | libperl5.36 5.36.0-7+deb12u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-82560 | LOW1.44 | perl 5.36.0-7+deb12u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-82560 | LOW1.44 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-82560 | LOW1.44 | perl-modules-5.36 5.36.0-7+deb12u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-2379 | LOW1.4 | curl 7.88.1-10+deb12u15 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0725 | LOW1.4 | curl 7.88.1-10+deb12u15 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2025-10966 | LOW1.4 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW1.4 | curl 7.88.1-10+deb12u15 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | LOW1.4 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW1.4 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW1.4 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-2379 | LOW1.4 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0725 | LOW1.4 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2025-10966 | LOW1.4 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW1.4 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | LOW1.4 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW1.4 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW1.4 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-2379 | LOW1.4 | libcurl4 7.88.1-10+deb12u15 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0725 | LOW1.4 | libcurl4 7.88.1-10+deb12u15 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2025-10966 | LOW1.4 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW1.4 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | LOW1.4 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW1.4 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW1.4 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-2379 | LOW1.4 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0725 | LOW1.4 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2025-10966 | LOW1.4 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW1.4 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | LOW1.4 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW1.4 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW1.4 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2012-0039 | LOW1.4 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2012-0039 | LOW1.4 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2012-0039 | LOW1.4 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2012-0039 | LOW1.4 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2012-0039 | LOW1.4 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2015-3276 | LOW1.4 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 5.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-17740 | LOW1.4 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 7.0% Low-Moderate Risk | Post-Exploit |
| CVE-2020-15719 | LOW1.4 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-22185 | LOW1.4 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-31486 | LOW1.4 | libperl5.36 5.36.0-7+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2017-16232 | LOW1.4 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 5.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-10126 | LOW1.4 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1210 | LOW1.4 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2025-61143 | LOW1.4 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-61144 | LOW1.4 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-61145 | LOW1.4 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52491 | LOW1.4 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52492 | LOW1.4 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2017-16232 | LOW1.4 | libtiff6 4.5.0-6+deb12u4 No fix yet | 5.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-10126 | LOW1.4 | libtiff6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1210 | LOW1.4 | libtiff6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2025-61143 | LOW1.4 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-61144 | LOW1.4 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-61145 | LOW1.4 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52491 | LOW1.4 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52492 | LOW1.4 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2017-16232 | LOW1.4 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 5.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-10126 | LOW1.4 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1210 | LOW1.4 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2025-61143 | LOW1.4 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-61144 | LOW1.4 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-61145 | LOW1.4 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52491 | LOW1.4 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52492 | LOW1.4 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2007-2243 | LOW1.4 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2007-2768 | LOW1.4 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 8.6% Low-Moderate Risk | Post-Exploit |
| CVE-2008-3234 | LOW1.4 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2016-20012 | LOW1.4 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 5.3% Low-Moderate Risk | Post-Exploit |
| CVE-2018-15919 | LOW1.4 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 3.6% Low-Moderate Risk | Post-Exploit |
| CVE-2020-14145 | LOW1.4 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | LOW1.4 | perl 5.36.0-7+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | LOW1.4 | perl-base 5.36.0-7+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | LOW1.4 | perl-modules-5.36 5.36.0-7+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-16599 | LOW1.4 | wget 1.21.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13608 | LOW1.33 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.33 | curl 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.33 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-87864 | LOW1.33 | curl 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-87865 | LOW1.33 | curl 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-87866 | LOW1.33 | curl 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92389 | LOW1.33 | curl 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92391 | LOW1.33 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-13608 | LOW1.33 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.33 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.33 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-87864 | LOW1.33 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-87865 | LOW1.33 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-87866 | LOW1.33 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92389 | LOW1.33 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92391 | LOW1.33 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-13608 | LOW1.33 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.33 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.33 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-87864 | LOW1.33 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-87865 | LOW1.33 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-87866 | LOW1.33 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92389 | LOW1.33 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92391 | LOW1.33 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-13608 | LOW1.33 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.33 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.33 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-87864 | LOW1.33 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-87865 | LOW1.33 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-87866 | LOW1.33 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92389 | LOW1.33 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92391 | LOW1.33 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41080 | LOW1.33 | libexpat1 2.5.0-1+deb12u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41080 | LOW1.33 | libexpat1-dev 2.5.0-1+deb12u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-106582 | LOW1.33 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6879 | LOW1.32 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6879 | LOW1.32 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-27587 | LOW1.27 | openssl 3.0.22-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-73281 | LOW1.26 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW1.19 | cpp-12 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW1.19 | g++-12 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW1.19 | gcc-12 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW1.19 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW1.19 | libasan8 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW1.19 | libatomic1 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW1.19 | libcc1-0 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2023-52426 | LOW1.19 | libexpat1 2.5.0-1+deb12u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-52426 | LOW1.19 | libexpat1-dev 2.5.0-1+deb12u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW1.19 | libgcc-12-dev 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW1.19 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW1.19 | libgomp1 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2023-49463 | LOW1.19 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW1.19 | libitm1 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2017-14159 | LOW1.19 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW1.19 | liblsan0 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW1.19 | libquadmath0 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW1.19 | libstdc++-12-dev 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW1.19 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2023-1916 | LOW1.19 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-3164 | LOW1.19 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-6228 | LOW1.19 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-8176 | LOW1.19 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-8177 | LOW1.19 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-8851 | LOW1.19 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-1916 | LOW1.19 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-3164 | LOW1.19 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-6228 | LOW1.19 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-8176 | LOW1.19 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-8177 | LOW1.19 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-8851 | LOW1.19 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-1916 | LOW1.19 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-3164 | LOW1.19 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-6228 | LOW1.19 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-8176 | LOW1.19 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-8177 | LOW1.19 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-8851 | LOW1.19 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW1.19 | libtsan2 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW1.19 | libubsan1 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-94266 | LOW1.19 | curl 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-94266 | LOW1.19 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-94266 | LOW1.19 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-94266 | LOW1.19 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3949 | LOW1.19 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-106584 | LOW1.19 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-106587 | LOW1.19 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.12 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.12 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.12 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.12 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.01 | libncurses-dev 6.4-4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.01 | libncurses5-dev 6.4-4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.01 | libncurses6 6.4-4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.01 | libncursesw5-dev 6.4-4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.01 | libncursesw6 6.4-4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-31047 | LOW1.01 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-31047 | LOW1.01 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.01 | libperl5.36 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8961 | LOW1.01 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-9165 | LOW1.01 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8961 | LOW1.01 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-9165 | LOW1.01 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8961 | LOW1.01 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-9165 | LOW1.01 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.01 | libtinfo6 6.4-4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.01 | ncurses-base 6.4-4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.01 | ncurses-bin 6.4-4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.01 | perl 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.01 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.01 | perl-modules-5.36 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-25269 | LOW0.76 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-13978 | LOW0.76 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8534 | LOW0.76 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-13978 | LOW0.76 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8534 | LOW0.76 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-13978 | LOW0.76 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8534 | LOW0.76 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68809 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90037 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93221 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98959 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72130 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74752 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89676 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90036 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98716 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98769 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98466 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89526 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89631 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89633 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-19449 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-3847 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-52452 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52624 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52751 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53218 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-21803 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-26836 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26913 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26914 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26944 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38570 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-38630 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41045 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42118 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44941 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44942 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44951 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46729 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46811 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46813 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47691 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50217 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50226 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50282 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53068 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53168 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53179 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-53218 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56538 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56775 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57900 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21927 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-21967 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21969 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23133 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37750 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-37777 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37861 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37952 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37957 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38069 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38182 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38248 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38369 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38582 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38585 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38595 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38722 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38734 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-39797 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39810 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39952 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71068 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71073 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71152 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100072 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23171 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23226 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23361 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31527 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31729 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43049 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43250 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46068 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46219 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46241 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53115 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53117 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53118 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53120 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53129 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53143 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53156 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53262 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53272 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64001 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64305 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64341 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64348 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64424 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64556 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72042 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72098 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89465 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89638 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89761 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89972 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-93817 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98715 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98741 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46274 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68470 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40137 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40333 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-64138 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64389 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64392 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74345 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89788 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89803 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90048 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-93792 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98490 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98725 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98853 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98857 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98895 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98944 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98945 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98964 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98968 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98980 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99006 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99012 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99032 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99053 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99054 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99056 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99059 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-99081 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74695 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89702 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98805 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40170 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68426 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-53781 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39981 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43248 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63974 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97505 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89610 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-26669 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41935 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53147 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57982 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21985 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38081 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38204 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38636 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39744 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23327 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45893 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45943 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45957 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46130 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46293 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53179 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68409 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-14040 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-25743 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68183 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68324 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43126 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43414 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64078 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89671 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97422 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97425 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97493 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97494 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-52586 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42162 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37776 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43125 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46054 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52991 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53000 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53091 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63962 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64017 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64026 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74269 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80837 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80841 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89530 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89545 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89564 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89652 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89659 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89675 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89708 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89713 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89811 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90111 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90206 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90227 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90315 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98222 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98364 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-53216 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57984 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40158 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-23050 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31663 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45859 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-45894 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45942 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52956 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53009 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53053 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53132 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53185 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53224 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53230 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53246 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63826 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63940 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64025 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64109 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64160 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64319 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64320 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64481 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68086 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68118 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68273 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68293 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68323 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68329 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68401 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68404 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68448 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68453 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72288 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72320 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72338 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72398 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72405 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72469 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74391 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74405 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74506 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74537 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74611 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74684 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80668 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80710 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80864 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80989 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89528 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89537 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89550 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89580 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89625 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89637 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89654 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89672 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89680 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89685 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89693 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90093 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90099 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90104 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90161 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90230 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90237 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90343 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90347 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90392 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90398 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93105 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93154 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97496 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97555 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97561 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97563 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97594 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97933 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97990 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98033 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98034 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98041 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98173 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98175 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98254 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98266 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98295 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98330 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98341 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98365 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98373 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98375 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98403 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98657 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98733 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98754 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98176 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98687 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-36694 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-21264 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-53095 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-57795 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21714 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98589 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98808 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93125 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53267 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-6240 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-36968 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43239 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72382 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89707 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98439 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98449 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98452 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98454 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98704 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98705 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98794 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98803 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98829 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23383 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31502 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31516 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68399 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90333 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3397 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89648 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89848 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98634 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98763 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98828 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98836 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40071 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68342 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31505 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98760 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98810 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98839 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68320 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89709 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98271 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98570 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98792 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98852 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54107 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23239 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23240 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89448 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-49569 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-80836 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89995 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98714 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98863 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0597 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-23005 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-37454 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-4133 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52590 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52591 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52625 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52648 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52671 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52761 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52770 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52797 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52888 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52920 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53149 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53261 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53367 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53394 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53460 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53523 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53529 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53846 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54013 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54280 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-6039 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-2193 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-25740 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26670 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26677 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26691 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26740 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26756 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26799 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26841 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26866 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26876 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26902 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26947 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26948 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26953 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-26962 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27010 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27011 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27041 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27057 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27062 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27079 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35784 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35794 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35799 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35808 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35860 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35904 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35924 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35931 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35942 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35945 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35946 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35951 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35961 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36911 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36951 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38557 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38564 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38594 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38608 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38622 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38625 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40965 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40969 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40975 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40998 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40999 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-41008 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41023 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-41031 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41082 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42128 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42139 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42239 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42241 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42243 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42279 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42317 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43819 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43824 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43850 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43872 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43899 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43901 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43913 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44963 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45015 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46678 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46681 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46698 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46727 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46728 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46730 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46760 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46765 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46775 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46776 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46806 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46808 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46834 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-46860 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47141 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47658 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-47661 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47662 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47664 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47703 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47752 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47794 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49893 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49901 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49906 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49908 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49910 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49914 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49916 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49918 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49919 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49920 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49921 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49922 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49923 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49926 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49940 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49945 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49970 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-49988 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-50009 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50028 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50111 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50166 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50285 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-50289 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52559 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52560 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53051 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53056 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53079 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53085 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53089 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53090 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-53091 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53094 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-53114 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53134 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53187 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53195 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53219 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53224 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53687 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-54683 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56544 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56565 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56566 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56583 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56588 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56591 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56592 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56611 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56641 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-56692 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56712 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56742 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57804 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57809 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57872 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57888 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57975 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57976 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57999 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-58006 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-58012 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-58053 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-58089 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58096 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-58098 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58100 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58237 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58241 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21634 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21635 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21656 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21658 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21673 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21693 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21696 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21723 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21729 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21768 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21801 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21831 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21836 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21870 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21872 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21885 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-21888 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21894 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21907 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21949 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21955 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21961 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-21972 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21976 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22028 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22037 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 69.5% Actively Exploited | Not Applicable |
| CVE-2025-22043 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-22048 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22053 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22057 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22070 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22113 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22125 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22127 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23130 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37747 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37800 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37802 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37806 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37807 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37834 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37842 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37853 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37856 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37860 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37893 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37956 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37977 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38006 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38014 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38038 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38039 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38045 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38059 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38080 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38096 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38127 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38132 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38195 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38244 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38246 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38264 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38272 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38283 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38311 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38333 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38426 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38429 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-38438 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38449 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38507 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38531 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38544 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38590 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38597 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38615 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38692 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38705 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38709 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38716 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39705 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39707 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39720 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39732 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39746 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39747 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39767 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39779 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39829 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39850 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39851 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-39886 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39910 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39932 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39940 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39947 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39989 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40075 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40160 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40325 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40328 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40339 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68188 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68209 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68304 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68379 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71109 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71129 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71138 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71160 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71184 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71188 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71272 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71273 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71289 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100076 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-100077 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22996 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23000 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23088 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23137 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23138 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23213 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23214 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23247 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23276 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23330 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23346 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23374 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23419 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23465 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31410 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31458 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31462 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31487 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31531 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31557 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31560 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31606 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31648 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31655 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31675 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31677 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31722 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31723 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31724 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31725 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31767 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43010 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43016 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43036 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43073 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43083 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43091 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43107 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43119 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43129 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43137 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43153 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43161 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43167 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43170 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43173 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43215 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43244 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43271 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43317 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43318 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43338 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43344 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43362 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43409 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43413 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43419 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43443 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43456 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45855 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45858 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45877 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45892 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45899 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45901 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45917 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45944 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45981 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45985 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45988 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45993 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46000 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46012 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46071 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46156 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46157 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46200 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46225 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46226 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46229 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46254 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46282 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46312 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52936 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52937 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52961 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52990 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53015 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53017 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53018 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53027 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53070 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53076 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53083 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53102 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53106 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53122 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53220 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53226 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53232 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53237 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53258 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53265 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53285 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53292 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53297 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53313 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53317 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53345 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53353 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53358 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53376 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53377 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63845 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63846 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63847 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63848 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63853 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63854 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63856 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63858 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63963 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63983 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63999 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64006 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64036 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64060 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64076 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64077 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64079 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64112 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64144 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64146 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64163 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64190 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64212 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64213 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64241 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64345 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64463 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68085 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68098 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68112 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68152 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68205 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68233 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68242 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68247 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68258 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68312 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68396 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68435 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68441 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68445 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68447 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68449 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68471 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72028 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72073 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72106 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72144 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72147 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72162 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72168 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72198 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72200 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72203 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72213 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72324 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72325 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72336 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72337 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72341 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72369 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72373 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72375 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72379 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72380 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72397 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72404 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72416 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72420 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72423 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72434 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72438 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72440 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72454 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72470 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72472 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72488 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72493 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74257 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74272 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74278 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74291 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74302 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74307 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74314 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74317 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74337 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74342 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74347 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74350 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74356 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74386 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74388 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74389 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74407 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74417 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74445 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74466 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74527 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74544 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74592 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74599 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74600 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74638 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74687 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74713 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74723 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74725 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74729 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74735 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74740 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74747 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80526 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80551 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80554 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80556 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80576 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80579 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80580 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80587 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80602 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80623 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80628 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80629 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80631 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80634 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80636 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80637 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80650 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80654 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80670 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80676 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80694 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80695 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80698 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80771 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80905 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80907 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80920 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80925 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80937 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80980 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80991 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80999 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81016 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89437 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89441 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89452 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89462 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89468 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89472 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89492 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89520 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89543 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89544 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89561 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89567 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89574 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89611 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89622 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89718 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89722 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89738 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89740 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89757 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89762 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89763 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89835 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89837 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89884 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89912 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89933 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89996 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90021 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90023 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90061 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90076 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90083 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90087 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90098 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90105 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90106 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90112 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90116 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90146 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90148 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90149 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90150 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90152 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90153 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90154 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90155 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90156 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90162 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90166 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90167 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90169 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90174 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90179 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90199 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90200 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90204 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90205 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90208 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90229 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90232 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90247 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90259 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90264 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90265 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90273 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90289 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90300 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90301 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90308 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90313 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90320 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90321 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90322 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90328 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90337 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90345 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90358 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90365 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90368 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90375 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90383 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90407 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90410 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90418 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90421 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90433 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92480 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92482 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92488 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92499 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92503 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92520 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93042 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-93047 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93058 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93081 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93091 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93122 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93128 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93150 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93155 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93163 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93168 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93174 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93175 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93179 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93184 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93192 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93196 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93228 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93272 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93282 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93285 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93786 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93790 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93791 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93793 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93796 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93799 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93804 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97409 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97478 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97499 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97500 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97512 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97515 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97518 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97529 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97534 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97535 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97536 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97537 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97554 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97558 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97559 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97562 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97565 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97567 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97587 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97599 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97600 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97609 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97901 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97908 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97918 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97924 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97929 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97935 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97939 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97950 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97953 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97978 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97992 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97994 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98019 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98026 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98043 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98056 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98085 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98103 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98107 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98111 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98114 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98124 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98125 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98126 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98127 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98131 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98142 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98161 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98162 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98170 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98180 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98192 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98193 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98198 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98212 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98248 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98269 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98279 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98288 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98292 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98294 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98309 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98313 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98327 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98333 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98335 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98353 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98355 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98409 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98420 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98503 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98539 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98556 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98652 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98660 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98665 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98745 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98751 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98775 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98778 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98797 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98801 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98812 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98820 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98830 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98833 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98837 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98846 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98850 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52653 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53823 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54030 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54088 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35843 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39990 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40057 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68219 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68334 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68378 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68822 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31486 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43253 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53229 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53284 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63855 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64388 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64513 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68102 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68238 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68241 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68408 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68412 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68418 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72007 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72009 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72254 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72315 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72321 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72376 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72439 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72494 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74261 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74308 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74318 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74338 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74374 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74397 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74536 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74543 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74571 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74653 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74733 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74754 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80611 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80616 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80643 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80653 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80704 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80739 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80786 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80820 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80861 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80866 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80884 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80948 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80974 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80990 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80996 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89484 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89527 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89531 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89539 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89552 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89566 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89598 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89601 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89644 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89645 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89647 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89759 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89795 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89808 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89813 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89862 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89944 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89955 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89958 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89975 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90066 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90084 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90097 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90109 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90119 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90125 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90138 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90139 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90182 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90183 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90187 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90213 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90250 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90267 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90311 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90330 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90335 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90346 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90385 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90389 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92493 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93062 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93072 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93093 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93116 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93129 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93146 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93172 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93186 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93199 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93202 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93208 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93216 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93231 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93243 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93244 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93269 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93794 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93823 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93828 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93829 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97424 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97477 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97479 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97480 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97501 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97530 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97566 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97597 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97605 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97613 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97615 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97616 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97619 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97906 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97984 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97985 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97989 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97997 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98003 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98021 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98044 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98058 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98067 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98073 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98079 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98081 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98087 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98148 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98177 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98179 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98182 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98285 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98289 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98304 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98307 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98317 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98321 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98329 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98332 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98334 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98337 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98338 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98386 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98387 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98389 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98393 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98394 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98399 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98400 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98424 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98425 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98427 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36881 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71225 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64391 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74401 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89682 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89686 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89860 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90041 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97965 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98156 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98174 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98284 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98401 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98471 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98698 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98706 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98707 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98720 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98823 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98824 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98827 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98859 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71193 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23035 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90234 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90235 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97975 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98738 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98767 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40077 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40289 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40311 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40337 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68322 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71065 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63816 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63959 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68083 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68185 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80761 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80847 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89793 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89794 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89832 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89833 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89840 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89906 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89934 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90016 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90029 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93238 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98097 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98099 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98436 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63871 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90379 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97531 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98549 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-30258 | NONE0 | gnupg-l10n 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68972 | NONE0 | gnupg-l10n 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98742 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-20794 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-52771 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53447 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-24864 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26869 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27408 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36024 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36949 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39508 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42107 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46787 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46870 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-50135 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53176 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-53178 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-56729 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57857 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57974 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21732 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21825 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21892 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22115 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38234 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38524 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38717 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39726 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39754 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39927 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39961 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68296 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23004 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23118 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23207 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45949 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46017 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53108 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64038 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72329 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72383 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74264 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74677 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74690 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74700 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74715 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80785 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80883 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80947 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89553 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89719 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89810 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89899 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89913 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89920 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89929 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89956 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90135 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90325 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90326 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90417 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92500 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93099 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93100 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93104 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93176 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93200 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97949 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97988 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98229 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98245 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98507 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98508 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98568 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98598 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98656 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98662 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98672 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98681 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98694 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98695 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98708 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98709 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98734 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98735 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98736 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98737 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98749 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98750 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98752 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98753 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98762 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98768 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98772 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98773 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98785 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98786 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98790 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98800 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98826 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98840 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68081 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-98265 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98711 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-42123 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68768 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90359 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98273 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98435 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98443 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98525 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98565 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98620 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98703 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98722 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98726 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98739 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98764 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98789 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98793 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98795 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98798 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98799 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98807 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98809 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98814 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98819 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98838 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98855 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98856 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98875 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26661 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26662 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26672 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26757 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26758 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26768 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-68337 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98101 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89666 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98453 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98701 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98822 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-16089 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-42156 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42158 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90336 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97532 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97938 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98286 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98456 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98493 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98506 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98544 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98558 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98663 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98664 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98666 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98669 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98670 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98677 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98696 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98721 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98740 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98748 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98756 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98757 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98765 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98766 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98796 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98815 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98816 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98825 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98834 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98847 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98854 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98862 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98761 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98878 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98880 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98882 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98883 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98894 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98897 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98901 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98903 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98904 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98905 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98906 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98908 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98910 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98914 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98916 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98917 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98924 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98926 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98929 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98930 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98931 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98932 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98933 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98934 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98935 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98936 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98937 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98940 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98942 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98946 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98947 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98950 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98954 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98955 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98956 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98957 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98966 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98967 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98969 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98970 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98971 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98972 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98975 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98977 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98978 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98979 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98981 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98983 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98984 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98985 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98989 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98990 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98992 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98993 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98996 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99002 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99005 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99007 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99008 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99009 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99010 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99015 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99019 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99021 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99022 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99024 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99025 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99026 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99027 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99031 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99033 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99034 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99035 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99036 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99037 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99038 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99039 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99040 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99041 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99043 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99045 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99049 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99052 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99057 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99058 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99061 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99063 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99067 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99070 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99071 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99072 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99074 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-99076 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99077 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-99080 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99082 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99083 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-99086 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99087 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99088 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | — | Not Applicable |
| CVE-2026-99089 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | — | Not Applicable |
| CVE-2026-99090 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | — | Not Applicable |
| CVE-2026-99091 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | — | Not Applicable |
| CVE-2026-99095 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | — | Not Applicable |
| DLA-4854-1 | NONE0 | tzdata 2026c-0+deb12u1 fixed in 2026e-0+deb12u1 | — | Not Applicable |
| CVE-2018-1000021 | NONE0 | git-man 1:2.39.5-0+deb12u3 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-24975 | NONE0 | git-man 1:2.39.5-0+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2024-52005 | NONE0 | git-man 1:2.39.5-0+deb12u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2004-0230 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 80.3% Actively Exploited | Not Applicable |
| CVE-2005-3660 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2008-2544 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2008-4609 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 32.1% High Exploitation Risk | Not Applicable |
| CVE-2010-4563 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2010-5321 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2011-4915 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4916 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2011-4917 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2012-4542 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2014-9892 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9900 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-10723 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-0630 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-13694 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 4.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12378 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12379 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12380 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12381 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12382 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12455 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12456 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16229 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16230 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16231 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16232 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-16233 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16234 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19070 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-11725 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-25265 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44032 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44033 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44034 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-45884 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-23039 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-31081 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31085 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-3640 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-39191 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-4134 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-40918 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98802 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-105712 | NONE0 | gnupg-l10n 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89987 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98484 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98732 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3219 | NONE0 | gnupg-l10n 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89642 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90263 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90401 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92485 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98377 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2015-2877 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-50057 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50211 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40268 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40303 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98450 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98451 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98502 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98509 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98551 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98655 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98668 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98679 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98685 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98686 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98700 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98755 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98771 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98777 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98811 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98851 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57062 | NONE0 | gnupg-l10n 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-11191 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-25742 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40180 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40266 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68781 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71198 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43258 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-68203 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68303 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80738 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80747 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80755 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80851 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89797 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89799 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89834 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89838 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89859 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89921 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89938 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89960 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89962 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90002 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90013 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90044 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90045 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93205 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93235 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93239 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93251 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93260 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98102 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98682 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98683 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98684 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | — | Not Applicable |
| CVE-2026-98628 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98671 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98710 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98784 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98831 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98874 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2007-3719 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42155 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98486 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98505 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98697 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98779 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98780 | NONE0 | linux-libc-dev 6.1.190-1 No fix yet | 0.2% 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.