Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. A database user with ordinary SQL access could exploit CVE-2026-14662 in libpq5 to run code as the postgres OS user, which could expose stored data and give a foothold inside the container. The image requires a password at startup, so an outsider must first obtain database credentials before these flaws can be reached. Several of the same libpq5 issues share this path, so the exposure is concentrated in one package and is best addressed by upgrading PostgreSQL and libpq5 to a patched release, restricting who holds database logins, and limiting network access to port 5432.
Hardening plan for this image · 5 steps
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-6653 | HIGH7.84 | libxml2 2.12.7+dfsg+really2.9.14-2.1 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-14662 | HIGH7.04 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-14664 | HIGH7.04 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-14669 | HIGH7.04 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-14680 | HIGH7.04 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-16239 | HIGH7.04 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-2006 | HIGH7.04 | libpq5 17.6-1.pgdg13+1 fixed in 17.8-0+deb13u1 | 1.2% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6473 | HIGH7.04 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 1.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-74860 | MEDIUM6.8 | libxml2 2.12.7+dfsg+really2.9.14-2.1 No fix yet | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-19499 | MEDIUM6.8 | libc-bin 2.41-12 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM6.8 | libc6 2.41-12 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18408 | MEDIUM6.72 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6477 | MEDIUM6.72 | libpq5 17.6-1.pgdg13+1 fixed in 17.10-0+deb13u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-4105 | MEDIUM6.7 | libsystemd0 257.7-1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM6.7 | libudev1 257.7-1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6478 | MEDIUM6.56 | libpq5 17.6-1.pgdg13+1 fixed in 17.10-0+deb13u1 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-4437 | MEDIUM6.5 | libc-bin 2.41-12 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM6.5 | libc-bin 2.41-12 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM6.5 | libc6 2.41-12 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM6.5 | libc6 2.41-12 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2673 | MEDIUM6.5 | libssl3t64 3.5.1-1 fixed in 3.5.5-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2673 | MEDIUM6.5 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.5-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-14668 | MEDIUM6.48 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6464 | MEDIUM6.48 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-15741 | MEDIUM6.4 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-40225 | MEDIUM6.4 | libsystemd0 257.7-1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM6.4 | libsystemd0 257.7-1 fixed in 257.13-1~deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40225 | MEDIUM6.4 | libudev1 257.7-1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM6.4 | libudev1 257.7-1 fixed in 257.13-1~deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM6.3 | libssl3t64 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM6.3 | libssl3t64 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM6.3 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM6.3 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-86138 | MEDIUM6.24 | libxml2 2.12.7+dfsg+really2.9.14-2.1 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86139 | MEDIUM6.24 | libxml2 2.12.7+dfsg+really2.9.14-2.1 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86140 | MEDIUM6.24 | libxml2 2.12.7+dfsg+really2.9.14-2.1 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86142 | MEDIUM6.24 | libxml2 2.12.7+dfsg+really2.9.14-2.1 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86144 | MEDIUM6.24 | libxml2 2.12.7+dfsg+really2.9.14-2.1 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-11187 | MEDIUM6.1 | libssl3t64 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-11187 | MEDIUM6.1 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-15467 | MEDIUM6 | libssl3t64 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 74.8% Actively Exploited | Directly Exposed |
| CVE-2025-15467 | MEDIUM6 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 74.8% Actively Exploited | Directly Exposed |
| CVE-2026-15742 | MEDIUM6 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6479 | MEDIUM6 | libpq5 17.6-1.pgdg13+1 fixed in 17.10-0+deb13u1 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-12818 | MEDIUM6 | libpq5 17.6-1.pgdg13+1 fixed in 17.7-0+deb13u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-7424 | MEDIUM6 | libxslt1.1 1.1.35-1.2 fixed in 1.1.35-1.2+deb13u1 | 1.3% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-5435 | MEDIUM5.9 | libc-bin 2.41-12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc-bin 2.41-12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc-bin 2.41-12 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc-bin 2.41-12 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.9 | libc-bin 2.41-12 fixed in 2.41-12+deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | libc6 2.41-12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc6 2.41-12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc6 2.41-12 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc6 2.41-12 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.9 | libc6 2.41-12 fixed in 2.41-12+deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-9231 | MEDIUM5.9 | libssl3t64 3.5.1-1 fixed in 3.5.1-1+deb13u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | libssl3t64 3.5.1-1 fixed in 3.5.5-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | libssl3t64 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.9 | libssl3t64 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-72897 | MEDIUM5.9 | libssl3t64 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.9 | libssl3t64 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.9 | libssl3t64 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15468 | MEDIUM5.9 | libssl3t64 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-66199 | MEDIUM5.9 | libssl3t64 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.9 | libssl3t64 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.9 | libssl3t64 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.9 | libssl3t64 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.9 | libssl3t64 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | libssl3t64 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.9 | libssl3t64 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.20.0-2 fixed in 4.20.0-2+deb13u1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9231 | MEDIUM5.9 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.1-1+deb13u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.5-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.9 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-72897 | MEDIUM5.9 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.9 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.9 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15468 | MEDIUM5.9 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-66199 | MEDIUM5.9 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.9 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.9 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.9 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.9 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.9 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42010 | MEDIUM5.88 | libgnutls30t64 3.8.9-3 fixed in 3.8.9-3+deb13u4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-8376 | MEDIUM5.88 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | MEDIUM5.88 | libssl3t64 3.5.1-1 fixed in 3.5.5-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | MEDIUM5.88 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.5-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86143 | MEDIUM5.84 | libxml2 2.12.7+dfsg+really2.9.14-2.1 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6471 | MEDIUM5.76 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6476 | MEDIUM5.76 | libpq5 17.6-1.pgdg13+1 fixed in 17.10-0+deb13u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-14679 | MEDIUM5.68 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-9230 | MEDIUM5.6 | libssl3t64 3.5.1-1 fixed in 3.5.1-1+deb13u1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.1-1+deb13u1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc-bin 2.41-12 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc6 2.41-12 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15469 | MEDIUM5.5 | libssl3t64 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM5.5 | libssl3t64 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM5.5 | libssl3t64 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libsystemd0 257.7-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libudev1 257.7-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15469 | MEDIUM5.5 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM5.5 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM5.5 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM5.5 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | MEDIUM5.46 | libgnutls30t64 3.8.9-3 fixed in 3.8.9-3+deb13u4 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13221 | MEDIUM5.46 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | MEDIUM5.46 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | MEDIUM5.46 | libssl3t64 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | MEDIUM5.46 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-6475 | MEDIUM5.36 | libpq5 17.6-1.pgdg13+1 fixed in 17.10-0+deb13u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-0915 | MEDIUM5.3 | libc-bin 2.41-12 fixed in 2.41-12+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | libc-bin 2.41-12 fixed in 2.41-12+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc-bin 2.41-12 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM5.3 | libc6 2.41-12 fixed in 2.41-12+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | libc6 2.41-12 fixed in 2.41-12+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc6 2.41-12 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42772 | MEDIUM5.3 | libssl3t64 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54873 | MEDIUM5.3 | libssl3t64 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | MEDIUM5.3 | libssl3t64 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM5.3 | libssl3t64 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-84784 | MEDIUM5.3 | libssl3t64 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM5.3 | libssl3t64 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42767 | MEDIUM5.3 | libssl3t64 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42772 | MEDIUM5.3 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54873 | MEDIUM5.3 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | MEDIUM5.3 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM5.3 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-84784 | MEDIUM5.3 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM5.3 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42767 | MEDIUM5.3 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-14670 | MEDIUM5.28 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-14671 | MEDIUM5.28 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-14677 | MEDIUM5.28 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-19385 | MEDIUM5.28 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2004 | MEDIUM5.28 | libpq5 17.6-1.pgdg13+1 fixed in 17.8-0+deb13u1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-2005 | MEDIUM5.28 | libpq5 17.6-1.pgdg13+1 fixed in 17.8-0+deb13u1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-6637 | MEDIUM5.28 | libpq5 17.6-1.pgdg13+1 fixed in 17.10-0+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6638 | MEDIUM5.28 | libpq5 17.6-1.pgdg13+1 fixed in 17.10-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | MEDIUM5.28 | libsystemd0 257.7-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | MEDIUM5.28 | libudev1 257.7-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-16238 | MEDIUM5.28 | postgresql 16.10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-14663 | MEDIUM5.2 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2023-40403 | MEDIUM5.2 | libxslt1.1 1.1.35-1.2 fixed in 1.1.35-1.2+deb13u1 | 1.3% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-57432 | MEDIUM5.04 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-57432 | MEDIUM5.04 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-57432 | MEDIUM5.04 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-57432 | MEDIUM5.04 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM5 | libbz2-1.0 1.0.8-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libc-bin 2.41-12 fixed in 2.41-12+deb13u4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc-bin 2.41-12 fixed in 2.41-12+deb13u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libc6 2.41-12 fixed in 2.41-12+deb13u4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc6 2.41-12 fixed in 2.41-12+deb13u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | libssl3t64 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-85091 | MEDIUM5 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM4.92 | libgnutls30t64 3.8.9-3 fixed in 3.8.9-3+deb13u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM4.92 | libgnutls30t64 3.8.9-3 fixed in 3.8.9-3+deb13u4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-86145 | MEDIUM4.92 | libpcre2-8-0 10.45-1 fixed in 10.46-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc-bin 2.41-12 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc6 2.41-12 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86137 | MEDIUM4.88 | libxml2 2.12.7+dfsg+really2.9.14-2.1 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-28387 | MEDIUM4.86 | libssl3t64 3.5.1-1 fixed in 3.5.5-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45447 | MEDIUM4.86 | libssl3t64 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28387 | MEDIUM4.86 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.5-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45447 | MEDIUM4.86 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | bsdutils 1:2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libblkid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | liblastlog2-2 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libsmartcols1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | mount 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | util-linux 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM4.72 | libxml2 2.12.7+dfsg+really2.9.14-2.1 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 1.0% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54875 | MEDIUM4.7 | libssl3t64 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4.7 | libssl3t64 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54875 | MEDIUM4.7 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4.7 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | bsdutils 1:2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | bsdutils 1:2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libblkid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libblkid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | liblastlog2-2 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | liblastlog2-2 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89161 | MEDIUM4.68 | libpcre2-8-0 10.45-1 fixed in 10.46-1~deb13u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM4.68 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libsmartcols1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libsmartcols1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11822 | MEDIUM4.68 | libsqlite3-0 3.46.1-7 fixed in 3.46.1-7+deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11824 | MEDIUM4.68 | libsqlite3-0 3.46.1-7 fixed in 3.46.1-7+deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM4.68 | libsystemd0 257.7-1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM4.68 | libudev1 257.7-1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | mount 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | mount 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM4.68 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM4.68 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM4.68 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | util-linux 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | util-linux 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-58050 | MEDIUM4.64 | libpcre2-8-0 10.45-1 fixed in 10.46-1~deb13u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-15467 | MEDIUM4.58 | openssl 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 74.8% Actively Exploited | Post-Exploit |
| CVE-2026-103111 | MEDIUM4.56 | libpcre2-8-0 10.45-1 fixed in 10.46-1~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41989 | MEDIUM4.5 | libgcrypt20 1.11.0-7 fixed in 1.11.0-7+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33846 | MEDIUM4.5 | libgnutls30t64 3.8.9-3 fixed in 3.8.9-3+deb13u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | MEDIUM4.5 | libgnutls30t64 3.8.9-3 fixed in 3.8.9-3+deb13u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-40355 | MEDIUM4.5 | libgssapi-krb5-2 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM4.5 | libgssapi-krb5-2 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM4.5 | libk5crypto3 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM4.5 | libk5crypto3 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM4.5 | libkrb5-3 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM4.5 | libkrb5-3 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM4.5 | libkrb5support0 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM4.5 | libkrb5support0 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM4.5 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-57433 | MEDIUM4.5 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM4.5 | libperl5.40 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM4.5 | libsasl2-2 2.1.28+dfsg1-9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM4.5 | libsasl2-modules-db 2.1.28+dfsg1-9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM4.5 | libssl3t64 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | libssl3t64 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM4.5 | libssl3t64 3.5.1-1 fixed in 3.5.5-1~deb13u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM4.5 | libssl3t64 3.5.1-1 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM4.5 | libssl3t64 3.5.1-1 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | libssl3t64 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34183 | MEDIUM4.5 | libssl3t64 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.5 | libssl3t64 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | libssl3t64 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | libssl3t64 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | libssl3t64 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | libssl3t64 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | libssl3t64 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM4.5 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM4.5 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.5-1~deb13u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM4.5 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM4.5 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34183 | MEDIUM4.5 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.5 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM4.5 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-57433 | MEDIUM4.5 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM4.5 | perl 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM4.5 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-57433 | MEDIUM4.5 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM4.5 | perl-base 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM4.5 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-57433 | MEDIUM4.5 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM4.5 | perl-modules-5.40 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM4.44 | libgnutls30t64 3.8.9-3 fixed in 3.8.9-3+deb13u4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM4.44 | libgnutls30t64 3.8.9-3 fixed in 3.8.9-3+deb13u4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-89157 | MEDIUM4.44 | libpcre2-8-0 10.45-1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | MEDIUM4.44 | libssl3t64 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM4.44 | libssl3t64 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM4.44 | libssl3t64 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-84782 | MEDIUM4.44 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM4.44 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM4.44 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-76781 | MEDIUM4.4 | libxml2 2.12.7+dfsg+really2.9.14-2.1 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6472 | MEDIUM4.32 | libpq5 17.6-1.pgdg13+1 fixed in 17.10-0+deb13u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54369 | MEDIUM4.26 | libacl1 2.3.2-2+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM4.26 | libgnutls30t64 3.8.9-3 fixed in 3.8.9-3+deb13u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-14672 | MEDIUM4.24 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53612 | MEDIUM4.2 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53614 | MEDIUM4.2 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | bsdutils 1:2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68973 | MEDIUM4.2 | dirmngr 2.4.7-21+b3 fixed in 2.4.7-21+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68973 | MEDIUM4.2 | gnupg 2.4.7-21 fixed in 2.4.7-21+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68973 | MEDIUM4.2 | gpg 2.4.7-21+b3 fixed in 2.4.7-21+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68973 | MEDIUM4.2 | gpg-agent 2.4.7-21+b3 fixed in 2.4.7-21+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68973 | MEDIUM4.2 | gpgconf 2.4.7-21+b3 fixed in 2.4.7-21+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68973 | MEDIUM4.2 | gpgsm 2.4.7-21+b3 fixed in 2.4.7-21+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53612 | MEDIUM4.2 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53614 | MEDIUM4.2 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libblkid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.2 | libc-bin 2.41-12 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc-bin 2.41-12 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.2 | libc6 2.41-12 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc6 2.41-12 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM4.2 | libcap2 1:2.75-10+b1 fixed in 1:2.75-10+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53612 | MEDIUM4.2 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53614 | MEDIUM4.2 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | liblastlog2-2 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53612 | MEDIUM4.2 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53614 | MEDIUM4.2 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53612 | MEDIUM4.2 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53614 | MEDIUM4.2 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libsmartcols1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53612 | MEDIUM4.2 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53614 | MEDIUM4.2 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53612 | MEDIUM4.2 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53614 | MEDIUM4.2 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53612 | MEDIUM4.2 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53614 | MEDIUM4.2 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | mount 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53612 | MEDIUM4.2 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53614 | MEDIUM4.2 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | util-linux 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc-bin 2.41-12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc-bin 2.41-12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc6 2.41-12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc6 2.41-12 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | MEDIUM4 | libc-bin 2.41-12 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | MEDIUM4 | libc6 2.41-12 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | MEDIUM4 | libssl3t64 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | MEDIUM4 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | LOW3.96 | libgnutls30t64 3.8.9-3 fixed in 3.8.9-3+deb13u4 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libgssapi-krb5-2 1.21.3-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libk5crypto3 1.21.3-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libkrb5-3 1.21.3-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libkrb5support0 1.21.3-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-89158 | LOW3.9 | libpcre2-8-0 10.45-1 fixed in 10.46-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89160 | LOW3.9 | libpcre2-8-0 10.45-1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | LOW3.9 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-19487 | LOW3.9 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2673 | LOW3.9 | openssl 3.5.1-1 fixed in 3.5.5-1~deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.9 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-19487 | LOW3.9 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | LOW3.9 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-19487 | LOW3.9 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | LOW3.9 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-19487 | LOW3.9 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc-bin 2.41-12 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc-bin 2.41-12 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc-bin 2.41-12 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc-bin 2.41-12 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc-bin 2.41-12 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc-bin 2.41-12 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc-bin 2.41-12 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc6 2.41-12 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc6 2.41-12 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc6 2.41-12 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc6 2.41-12 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc6 2.41-12 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc6 2.41-12 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc6 2.41-12 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | LOW3.9 | libldap2 2.6.10+dfsg-1 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | LOW3.9 | libldap2 2.6.10+dfsg-1 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-15719 | LOW3.9 | libldap2 2.6.10+dfsg-1 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-22185 | LOW3.9 | libldap2 2.6.10+dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54370 | LOW3.78 | libacl1 2.3.2-2+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | LOW3.78 | libattr1 1:2.5.2-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | LOW3.78 | openssl 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42768 | LOW3.78 | openssl 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-5958 | LOW3.78 | sed 4.9-2 fixed in 4.9-2+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-9714 | LOW3.74 | libxml2 2.12.7+dfsg+really2.9.14-2.1 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u2 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-10911 | LOW3.74 | libxslt1.1 1.1.35-1.2 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-13757 | LOW3.72 | libp11-kit0 0.25.5-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18938 | LOW3.72 | libp11-kit0 0.25.5-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-3374 | LOW3.7 | libapt-pkg7.0 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc-bin 2.41-12 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc6 2.41-12 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.7 | libssl3t64 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35191 | LOW3.7 | libssl3t64 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.7 | libssl3t64 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | libssl3t64 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.7 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35191 | LOW3.7 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.7 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11187 | LOW3.66 | openssl 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-89156 | LOW3.54 | libpcre2-8-0 10.45-1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-9231 | LOW3.54 | openssl 3.5.1-1 fixed in 3.5.1-1+deb13u1 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-31790 | LOW3.54 | openssl 3.5.1-1 fixed in 3.5.5-1~deb13u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42764 | LOW3.54 | openssl 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-54872 | LOW3.54 | openssl 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-72897 | LOW3.54 | openssl 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-75805 | LOW3.54 | openssl 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-77696 | LOW3.54 | openssl 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15468 | LOW3.54 | openssl 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-66199 | LOW3.54 | openssl 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69420 | LOW3.54 | openssl 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-22796 | LOW3.54 | openssl 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42769 | LOW3.54 | openssl 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.54 | openssl 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63073 | LOW3.54 | openssl 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-9076 | LOW3.54 | openssl 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | LOW3.53 | openssl 3.5.1-1 fixed in 3.5.5-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3.53 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3.53 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3.53 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-14678 | LOW3.44 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-18024 | LOW3.44 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-2003 | LOW3.44 | libpq5 17.6-1.pgdg13+1 fixed in 17.8-0+deb13u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6470 | LOW3.44 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6474 | LOW3.44 | libpq5 17.6-1.pgdg13+1 fixed in 17.10-0+deb13u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-12817 | LOW3.44 | libpq5 17.6-1.pgdg13+1 fixed in 17.7-0+deb13u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-15534 | LOW3.42 | libperl5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | LOW3.42 | perl 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | LOW3.42 | perl-base 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | LOW3.42 | perl-modules-5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9230 | LOW3.36 | openssl 3.5.1-1 fixed in 3.5.1-1+deb13u1 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-14666 | LOW3.36 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-14681 | LOW3.36 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2017-14159 | LOW3.31 | libldap2 2.6.10+dfsg-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libsystemd0 257.7-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libsystemd0 257.7-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libsystemd0 257.7-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libudev1 257.7-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libudev1 257.7-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libudev1 257.7-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-50812 | LOW3.3 | libsqlite3-0 3.46.1-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50813 | LOW3.3 | libsqlite3-0 3.46.1-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15469 | LOW3.3 | openssl 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-22795 | LOW3.3 | openssl 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW3.3 | openssl 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW3.3 | tar 1.35+dfsg-3.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-61801 | LOW3.3 | github.com/moby/sys/user v0.1.0 fixed in 0.4.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-13573 | LOW3.3 | libllvm19 1:19.1.7-3+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13574 | LOW3.3 | libllvm19 1:19.1.7-3+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libsystemd0 257.7-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libudev1 257.7-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | LOW3.28 | openssl 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW3.28 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW3.28 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW3.28 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| DSA-5990-1 | LOW3.2 | libxml2 2.12.7+dfsg+really2.9.14-2.1 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u1 | — | Directly ExposedContext importance: MEDIUM |
| DSA-5979-2 | LOW3.2 | libxslt1.1 1.1.35-1.2 fixed in 1.1.35-1.2+deb13u2 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-13595 | LOW3.18 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | bsdutils 1:2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | LOW3.18 | libgnutls30t64 3.8.9-3 fixed in 3.8.9-3+deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | LOW3.18 | libgnutls30t64 3.8.9-3 fixed in 3.8.9-3+deb13u4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | LOW3.18 | liblzma5 5.8.1-1 fixed in 5.8.1-1+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12087 | LOW3.18 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42772 | LOW3.18 | openssl 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-54873 | LOW3.18 | openssl 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-75804 | LOW3.18 | openssl 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-75806 | LOW3.18 | openssl 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-84784 | LOW3.18 | openssl 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW3.18 | openssl 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42767 | LOW3.18 | openssl 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW3.18 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-12087 | LOW3.18 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-12087 | LOW3.18 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | util-linux 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-7883 | LOW3.15 | libllvm19 1:19.1.7-3+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | LOW3.12 | libxml2 2.12.7+dfsg+really2.9.14-2.1 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-1757 | LOW3.12 | libxml2 2.12.7+dfsg+really2.9.14-2.1 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2015-9019 | LOW3.12 | libxslt1.1 1.1.35-1.2 No fix yet | 2.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2025-9232 | LOW3.1 | libssl3t64 3.5.1-1 fixed in 3.5.1-1+deb13u1 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9232 | LOW3.1 | openssl-provider-legacy 3.5.1-1 fixed in 3.5.1-1+deb13u1 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2011-3389 | LOW3.04 | libgnutls30t64 3.8.9-3 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2026-14673 | LOW3.04 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-16241 | LOW3.04 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6469 | LOW3.04 | libpq5 17.6-1.pgdg13+1 fixed in 17.11-0+deb13u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-2219 | LOW3 | dpkg 1.22.21 fixed in 1.22.22 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW3 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | LOW3 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-7010 | LOW3 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7017 | LOW3 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | LOW3 | openssl 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-48959 | LOW3 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | LOW3 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-7010 | LOW3 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7017 | LOW3 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48959 | LOW3 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | LOW3 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-7010 | LOW3 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7017 | LOW3 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48959 | LOW3 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | LOW3 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-7010 | LOW3 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7017 | LOW3 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW2.96 | libxml2 2.12.7+dfsg+really2.9.14-2.1 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107708 | LOW2.94 | libgssapi-krb5-2 1.21.3-5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libk5crypto3 1.21.3-5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libkrb5-3 1.21.3-5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libkrb5support0 1.21.3-5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | LOW2.92 | libc-bin 2.41-12 fixed in 2.41-12+deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-0861 | LOW2.92 | libc6 2.41-12 fixed in 2.41-12+deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | LOW2.92 | openssl 3.5.1-1 fixed in 3.5.5-1~deb13u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-modules 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-modules-bin 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-runtime 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam0g 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.82 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | dirmngr 2.4.7-21+b3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gnupg 2.4.7-21 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpg 2.4.7-21+b3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpg-agent 2.4.7-21+b3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpgconf 2.4.7-21+b3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpgsm 2.4.7-21+b3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-41991 | LOW2.82 | gzip 1.13-1 fixed in 1.13-1+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54875 | LOW2.82 | openssl 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-68160 | LOW2.82 | openssl 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.82 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-24882 | LOW2.81 | dirmngr 2.4.7-21+b3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW2.81 | gnupg 2.4.7-21 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW2.81 | gpg 2.4.7-21+b3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW2.81 | gpg-agent 2.4.7-21+b3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW2.81 | gpgconf 2.4.7-21+b3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW2.81 | gpgsm 2.4.7-21+b3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libncursesw6 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libtinfo6 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | ncurses-base 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | ncurses-bin 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2013-4392 | LOW2.8 | libsystemd0 257.7-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 257.7-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | LOW2.77 | gcc-14-base 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | libgcc-s1 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | libstdc++6 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW2.7 | gzip 1.13-1 fixed in 1.13-1+deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-69421 | LOW2.7 | openssl 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-14456 | LOW2.7 | openssl 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-28388 | LOW2.7 | openssl 3.5.1-1 fixed in 3.5.5-1~deb13u2 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-28389 | LOW2.7 | openssl 3.5.1-1 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | LOW2.7 | openssl 3.5.1-1 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-18798 | LOW2.7 | openssl 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34183 | LOW2.7 | openssl 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63072 | LOW2.7 | openssl 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-63076 | LOW2.7 | openssl 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-14457 | LOW2.7 | openssl 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-54874 | LOW2.7 | openssl 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63074 | LOW2.7 | openssl 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63075 | LOW2.7 | openssl 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-84782 | LOW2.66 | openssl 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-69419 | LOW2.66 | openssl 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW2.66 | openssl 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-18477 | LOW2.64 | tar 1.35+dfsg-3.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.64 | tar 1.35+dfsg-3.1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86141 | LOW2.64 | libxml2 2.12.7+dfsg+really2.9.14-2.1 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-7709 | LOW2.55 | libsqlite3-0 3.46.1-7 fixed in 3.46.1-7+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | LOW2.52 | gcc-14-base 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW2.52 | libgcc-s1 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW2.52 | libstdc++6 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-9820 | LOW2.4 | libgnutls30t64 3.8.9-3 fixed in 3.8.9-3+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| DSA-6549-1 | LOW2.4 | liblzma5 5.8.1-1 fixed in 5.8.1-1+deb13u2 | — | Directly Exposed |
| TEMP-1147318-639065 | LOW2.4 | liblzma5 5.8.1-1 fixed in 5.8.1-1+deb13u2 | — | Directly Exposed |
| CVE-2026-82560 | LOW2.4 | libperl5.40 5.40.1-6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW2.4 | openssl 3.5.1-1 fixed in 3.5.4-1~deb13u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-82560 | LOW2.4 | perl 5.40.1-6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-82560 | LOW2.4 | perl-base 5.40.1-6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-82560 | LOW2.4 | perl-modules-5.40 5.40.1-6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| DSA-6549-1 | LOW2.4 | xz-utils 5.8.1-1 fixed in 5.8.1-1+deb13u2 | — | Directly Exposed |
| TEMP-1147318-639065 | LOW2.4 | xz-utils 5.8.1-1 fixed in 5.8.1-1+deb13u2 | — | Directly Exposed |
| CVE-2026-39824 | LOW2.4 | golang.org/x/sys v0.13.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW2.34 | bsdutils 1:2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56391 | LOW2.34 | coreutils 9.7-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.34 | coreutils 9.7-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-102473 | LOW2.34 | dash 0.5.12-12 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-102474 | LOW2.34 | dash 0.5.12-12 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53910 | LOW2.34 | diffutils 1:3.10-4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW2.34 | libblkid1 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-6829 | LOW2.34 | libgcrypt20 1.11.0-7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | LOW2.34 | libgcrypt20 1.11.0-7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-67693 | LOW2.34 | libgnutls30t64 3.8.9-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88647 | LOW2.34 | libgnutls30t64 3.8.9-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88648 | LOW2.34 | libgnutls30t64 3.8.9-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95184 | LOW2.34 | libgnutls30t64 3.8.9-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libgssapi-krb5-2 1.21.3-5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libgssapi-krb5-2 1.21.3-5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libgssapi-krb5-2 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libk5crypto3 1.21.3-5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libk5crypto3 1.21.3-5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libk5crypto3 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libkrb5-3 1.21.3-5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libkrb5-3 1.21.3-5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libkrb5-3 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libkrb5support0 1.21.3-5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libkrb5support0 1.21.3-5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libkrb5support0 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | liblastlog2-2 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | libmount1 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | libsmartcols1 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | LOW2.34 | libsqlite3-0 3.46.1-7 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | libuuid1 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | mount 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2005-2541 | LOW2.34 | tar 1.35+dfsg-3.1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-14104 | LOW2.34 | util-linux 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0992 | LOW2.32 | libxml2 2.12.7+dfsg+really2.9.14-2.1 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-8732 | LOW2.24 | libxml2 2.12.7+dfsg+really2.9.14-2.1 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2011-3374 | LOW2.22 | apt 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3832 | LOW2.22 | libgnutls30t64 3.8.9-3 fixed in 3.8.9-3+deb13u4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW2.22 | libgnutls30t64 3.8.9-3 fixed in 3.8.9-3+deb13u4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW2.22 | openssl 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-35191 | LOW2.22 | openssl 3.5.1-1 fixed in 3.5.7-1~deb13u3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW2.22 | openssl 3.5.1-1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-75803 | LOW2.22 | openssl 3.5.1-1 fixed in 3.5.7-1~deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW2.16 | dirmngr 2.4.7-21+b3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gnupg 2.4.7-21 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gpg 2.4.7-21+b3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gpg-agent 2.4.7-21+b3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gpgconf 2.4.7-21+b3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gpgsm 2.4.7-21+b3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11731 | LOW2.1 | libxslt1.1 1.1.35-1.2 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2022-0563 | LOW1.99 | bsdutils 1:2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-18018 | LOW1.99 | coreutils 9.7-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW1.99 | coreutils 9.7-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libgssapi-krb5-2 1.21.3-5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libk5crypto3 1.21.3-5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libkrb5-3 1.21.3-5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libkrb5support0 1.21.3-5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2007-5686 | LOW1.99 | login.defs 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2007-5686 | LOW1.99 | passwd 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | util-linux 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-89162 | LOW1.98 | libpcre2-8-0 10.45-1 fixed in 10.46-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW1.98 | libsqlite3-0 3.46.1-7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | LOW1.91 | xz-utils 5.8.1-1 fixed in 5.8.1-1+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-9232 | LOW1.86 | openssl 3.5.1-1 fixed in 3.5.1-1+deb13u1 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | login.defs 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.74 | dirmngr 2.4.7-21+b3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-57062 | LOW1.74 | gnupg 2.4.7-21 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-57062 | LOW1.74 | gpg 2.4.7-21+b3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-57062 | LOW1.74 | gpg-agent 2.4.7-21+b3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-57062 | LOW1.74 | gpgconf 2.4.7-21+b3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-57062 | LOW1.74 | gpgsm 2.4.7-21+b3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | dirmngr 2.4.7-21+b3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gnupg 2.4.7-21 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gpg 2.4.7-21+b3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gpg-agent 2.4.7-21+b3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gpgconf 2.4.7-21+b3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gpgsm 2.4.7-21+b3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | libncursesw6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | libperl5.40 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | libtinfo6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | ncurses-base 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | ncurses-bin 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | perl 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | perl-base 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | perl-modules-5.40 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| TEMP-0841856-B18BAF | LOW1.5 | bash 5.2.37-2+b5 No fix yet | — | Post-Exploit |
| CVE-2026-95209 | LOW1.5 | libgnutls30t64 3.8.9-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95210 | LOW1.5 | libgnutls30t64 3.8.9-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| TEMP-0628843-DBAD28 | LOW1.5 | login.defs 1:4.17.4-2 No fix yet | — | Post-Exploit |
| TEMP-0628843-DBAD28 | LOW1.5 | passwd 1:4.17.4-2 No fix yet | — | Post-Exploit |
| TEMP-0517018-A83CE6 | LOW1.5 | sysvinit-utils 3.14-4 No fix yet | — | Post-Exploit |
| TEMP-0290435-0B57B5 | LOW1.5 | tar 1.35+dfsg-3.1 No fix yet | — | Post-Exploit |
| CVE-2025-68121 | NONE0 | stdlib v1.18.2 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-24538 | NONE0 | stdlib v1.18.2 fixed in 1.19.8, 1.20.3 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-24540 | NONE0 | stdlib v1.18.2 fixed in 1.19.9, 1.20.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2024-24790 | NONE0 | stdlib v1.18.2 fixed in 1.21.11, 1.22.4 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-22871 | NONE0 | stdlib v1.18.2 fixed in 1.23.8, 1.24.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39821 | NONE0 | stdlib v1.18.2 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-0861 | NONE0 | libc-l10n 2.41-12 fixed in 2.41-12+deb13u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0861 | NONE0 | locales 2.41-12 fixed in 2.41-12+deb13u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56858 | NONE0 | stdlib v1.18.2 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-24882 | NONE0 | gnupg-l10n 2.4.7-21 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-30580 | NONE0 | stdlib v1.18.2 fixed in 1.17.11, 1.18.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-29403 | NONE0 | stdlib v1.18.2 fixed in 1.19.10, 1.20.5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-39822 | NONE0 | stdlib v1.18.2 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-27664 | NONE0 | stdlib v1.18.2 fixed in 1.18.6, 1.19.1 | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-28131 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-2879 | NONE0 | stdlib v1.18.2 fixed in 1.18.7, 1.19.2 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-2880 | NONE0 | stdlib v1.18.2 fixed in 1.18.7, 1.19.2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-29804 | NONE0 | stdlib v1.18.2 fixed in 1.17.11, 1.18.3 | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-30630 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-30631 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-30632 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-30633 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-30634 | NONE0 | stdlib v1.18.2 fixed in 1.17.11, 1.18.3 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-30635 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-32189 | NONE0 | stdlib v1.18.2 fixed in 1.17.13, 1.18.5 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-41715 | NONE0 | stdlib v1.18.2 fixed in 1.18.7, 1.19.2 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-41716 | NONE0 | stdlib v1.18.2 fixed in 1.18.8, 1.19.3 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-41720 | NONE0 | stdlib v1.18.2 fixed in 1.18.9, 1.19.4 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-41722 | NONE0 | stdlib v1.18.2 fixed in 1.19.6, 1.20.1 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-41723 | NONE0 | stdlib v1.18.2 fixed in 1.19.6, 1.20.1 | 4.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-41724 | NONE0 | stdlib v1.18.2 fixed in 1.19.6, 1.20.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-41725 | NONE0 | stdlib v1.18.2 fixed in 1.19.6, 1.20.1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-24534 | NONE0 | stdlib v1.18.2 fixed in 1.19.8, 1.20.3 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2023-24536 | NONE0 | stdlib v1.18.2 fixed in 1.19.8, 1.20.3 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-24537 | NONE0 | stdlib v1.18.2 fixed in 1.19.8, 1.20.3 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-39325 | NONE0 | stdlib v1.18.2 fixed in 1.20.10, 1.21.3 | 3.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-45283 | NONE0 | stdlib v1.18.2 fixed in 1.20.11, 1.21.4, 1.20.12, 1.21.5 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-45287 | NONE0 | stdlib v1.18.2 fixed in 1.20.0 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-45288 | NONE0 | stdlib v1.18.2 fixed in 1.21.9, 1.22.2 | 92.0% Actively Exploited | Not Applicable |
| CVE-2024-34156 | NONE0 | stdlib v1.18.2 fixed in 1.22.7, 1.23.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-61726 | NONE0 | stdlib v1.18.2 fixed in 1.24.12, 1.25.6 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-61729 | NONE0 | stdlib v1.18.2 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25679 | NONE0 | stdlib v1.18.2 fixed in 1.25.8, 1.26.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.18.2 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32280 | NONE0 | stdlib v1.18.2 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32281 | NONE0 | stdlib v1.18.2 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32283 | NONE0 | stdlib v1.18.2 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33811 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-33818 | NONE0 | stdlib v1.18.2 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-39820 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39836 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42499 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.18.2 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56853 | NONE0 | stdlib v1.18.2 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56859 | NONE0 | stdlib v1.18.2 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56860 | NONE0 | stdlib v1.18.2 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-56862 | NONE0 | stdlib v1.18.2 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78667 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78669 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97031 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58183 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58188 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61728 | NONE0 | stdlib v1.18.2 fixed in 1.24.12, 1.25.6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-24539 | NONE0 | stdlib v1.18.2 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-29400 | NONE0 | stdlib v1.18.2 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-68973 | NONE0 | gnupg-l10n 2.4.7-21 fixed in 2.4.7-21+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86805 | NONE0 | libc-l10n 2.41-12 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-95818 | NONE0 | libc-l10n 2.41-12 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86805 | NONE0 | locales 2.41-12 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-95818 | NONE0 | locales 2.41-12 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-47907 | NONE0 | stdlib v1.18.2 fixed in 1.23.12, 1.24.6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-19499 | NONE0 | libc-l10n 2.41-12 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-19499 | NONE0 | locales 2.41-12 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-111943 | NONE0 | stdlib v1.18.2 fixed in 1.26.10, 1.27.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-4673 | NONE0 | stdlib v1.18.2 fixed in 1.23.10, 1.24.4 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-4437 | NONE0 | libc-l10n 2.41-12 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc-l10n 2.41-12 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4437 | NONE0 | locales 2.41-12 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | locales 2.41-12 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-1705 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-32148 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-29406 | NONE0 | stdlib v1.18.2 fixed in 1.19.11, 1.20.6 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-24785 | NONE0 | stdlib v1.18.2 fixed in 1.21.8, 1.22.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-47906 | NONE0 | stdlib v1.18.2 fixed in 1.23.12, 1.24.6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61727 | NONE0 | stdlib v1.18.2 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39825 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56866 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-94439 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32282 | NONE0 | stdlib v1.18.2 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-39318 | NONE0 | stdlib v1.18.2 fixed in 1.20.8, 1.21.1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-39319 | NONE0 | stdlib v1.18.2 fixed in 1.20.8, 1.21.1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-32289 | NONE0 | stdlib v1.18.2 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94448 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc-l10n 2.41-12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6791 | NONE0 | libc-l10n 2.41-12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-77117 | NONE0 | libc-l10n 2.41-12 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80489 | NONE0 | libc-l10n 2.41-12 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15281 | NONE0 | libc-l10n 2.41-12 fixed in 2.41-12+deb13u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | locales 2.41-12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6791 | NONE0 | locales 2.41-12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-77117 | NONE0 | locales 2.41-12 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80489 | NONE0 | locales 2.41-12 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15281 | NONE0 | locales 2.41-12 fixed in 2.41-12+deb13u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-24783 | NONE0 | stdlib v1.18.2 fixed in 1.21.8, 1.22.1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-24791 | NONE0 | stdlib v1.18.2 fixed in 1.21.12, 1.22.5 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-34155 | NONE0 | stdlib v1.18.2 fixed in 1.22.7, 1.23.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-34158 | NONE0 | stdlib v1.18.2 fixed in 1.22.7, 1.23.1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2024-45336 | NONE0 | stdlib v1.18.2 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97032 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-6368 | NONE0 | libc-l10n 2.41-12 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6368 | NONE0 | locales 2.41-12 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-1962 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-24789 | NONE0 | stdlib v1.18.2 fixed in 1.21.11, 1.22.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-0913 | NONE0 | stdlib v1.18.2 fixed in 1.23.10, 1.24.4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32288 | NONE0 | stdlib v1.18.2 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-24784 | NONE0 | stdlib v1.18.2 fixed in 1.21.8, 1.22.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-27142 | NONE0 | stdlib v1.18.2 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39823 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39826 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0915 | NONE0 | libc-l10n 2.41-12 fixed in 2.41-12+deb13u2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | libc-l10n 2.41-12 fixed in 2.41-12+deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8674 | NONE0 | libc-l10n 2.41-12 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-0915 | NONE0 | locales 2.41-12 fixed in 2.41-12+deb13u2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | locales 2.41-12 fixed in 2.41-12+deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8674 | NONE0 | locales 2.41-12 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-41717 | NONE0 | stdlib v1.18.2 fixed in 1.18.9, 1.19.4 | 6.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-24532 | NONE0 | stdlib v1.18.2 fixed in 1.19.7, 1.20.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-29409 | NONE0 | stdlib v1.18.2 fixed in 1.19.12, 1.20.7, 1.21.0-rc.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-39326 | NONE0 | stdlib v1.18.2 fixed in 1.20.12, 1.21.5 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-45284 | NONE0 | stdlib v1.18.2 fixed in 1.20.11, 1.21.4 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45289 | NONE0 | stdlib v1.18.2 fixed in 1.21.8, 1.22.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-45290 | NONE0 | stdlib v1.18.2 fixed in 1.21.8, 1.22.1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-22866 | NONE0 | stdlib v1.18.2 fixed in 1.22.12, 1.23.6, 1.24.0-rc.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22873 | NONE0 | stdlib v1.18.2 fixed in 1.23.9, 1.24.3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-47912 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58185 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58187 | NONE0 | stdlib v1.18.2 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58189 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61723 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-61724 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61725 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61730 | NONE0 | stdlib v1.18.2 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.18.2 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42507 | NONE0 | stdlib v1.18.2 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-78663 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58186 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc-l10n 2.41-12 fixed in 2.41-12+deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc-l10n 2.41-12 fixed in 2.41-12+deb13u4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | locales 2.41-12 fixed in 2.41-12+deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | locales 2.41-12 fixed in 2.41-12+deb13u4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-18374 | NONE0 | libc-l10n 2.41-12 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-18374 | NONE0 | locales 2.41-12 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68972 | NONE0 | gnupg-l10n 2.4.7-21 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22870 | NONE0 | stdlib v1.18.2 fixed in 1.23.7, 1.24.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-19542 | NONE0 | libc-l10n 2.41-12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89092 | NONE0 | libc-l10n 2.41-12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-19542 | NONE0 | locales 2.41-12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89092 | NONE0 | locales 2.41-12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45341 | NONE0 | stdlib v1.18.2 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4438 | NONE0 | libc-l10n 2.41-12 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-4438 | NONE0 | locales 2.41-12 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2010-4756 | NONE0 | libc-l10n 2.41-12 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-20796 | NONE0 | libc-l10n 2.41-12 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc-l10n 2.41-12 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc-l10n 2.41-12 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc-l10n 2.41-12 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc-l10n 2.41-12 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc-l10n 2.41-12 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2010-4756 | NONE0 | locales 2.41-12 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-20796 | NONE0 | locales 2.41-12 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010022 | NONE0 | locales 2.41-12 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010023 | NONE0 | locales 2.41-12 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010024 | NONE0 | locales 2.41-12 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | locales 2.41-12 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | locales 2.41-12 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-97399 | NONE0 | libc-l10n 2.41-12 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97399 | NONE0 | locales 2.41-12 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-105712 | NONE0 | gnupg-l10n 2.4.7-21 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-3219 | NONE0 | gnupg-l10n 2.4.7-21 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56857 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-30629 | NONE0 | stdlib v1.18.2 fixed in 1.17.11, 1.18.3 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-57062 | NONE0 | gnupg-l10n 2.4.7-21 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27139 | NONE0 | stdlib v1.18.2 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.