Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker could disrupt availability by hanging the Node/Express process via CVE-2022-24999 or by forcing excessive XML entity expansion via CVE-2026-26278, and could potentially expose credential headers in redirect scenarios. Note: CVE-2026-26278 can be fully mitigated by disabling DOCTYPE parsing through the processEntities: false option, but the remaining high-severity exposed findings still require patching or strict access controls.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2022-24999 | HIGH8.62 | qs 6.5.2 fixed in 6.10.3, 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, 6.2.4 | 15.6% High Exploitation Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-26278 | HIGH7.5 | fast-xml-parser 5.2.5 fixed in 4.5.4, 5.3.6 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-111756 | HIGH7.5 | follow-redirects 1.16.0 fixed in 1.16.1 | — | Directly Exposed |
| CVE-2026-111759 | HIGH7.5 | markdown-it 13.0.2 fixed in 15.0.2, 14.3.2 | — | Directly Exposed |
| CVE-2026-16742 | HIGH7.48 | libsystemd0 252.39-1~deb12u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | HIGH7.48 | libudev1 252.39-1~deb12u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-84933 | MEDIUM6.97 | undici 8.10.0 fixed in 7.29.1, 8.10.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-83605 | MEDIUM6.88 | @xmldom/xmldom 0.8.10 fixed in 0.9.11, 0.8.14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83607 | MEDIUM6.88 | @xmldom/xmldom 0.8.10 fixed in 0.9.11, 0.8.14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83605 | MEDIUM6.88 | @xmldom/xmldom 0.8.13 fixed in 0.9.11, 0.8.14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83607 | MEDIUM6.88 | @xmldom/xmldom 0.8.13 fixed in 0.9.11, 0.8.14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM6.8 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM6.8 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM6.8 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM6.8 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM6.71 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM6.71 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM6.71 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM6.71 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM6.63 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM6.63 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM6.63 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM6.63 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM6.63 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM6.63 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM6.63 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM6.63 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-26920 | MEDIUM6.5 | fast-xml-parser 3.21.1 fixed in 4.1.2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34601 | MEDIUM6.38 | @xmldom/xmldom 0.8.10 fixed in 0.8.12, 0.9.9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-41672 | MEDIUM6.38 | @xmldom/xmldom 0.8.10 fixed in 0.8.13, 0.9.10 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-41673 | MEDIUM6.38 | @xmldom/xmldom 0.8.10 fixed in 0.8.13, 0.9.10 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-41674 | MEDIUM6.38 | @xmldom/xmldom 0.8.10 fixed in 0.8.13, 0.9.10 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-41675 | MEDIUM6.38 | @xmldom/xmldom 0.8.10 fixed in 0.8.13, 0.9.10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83613 | MEDIUM6.38 | @xmldom/xmldom 0.8.10 fixed in 0.8.15, 0.9.12 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83614 | MEDIUM6.38 | @xmldom/xmldom 0.8.10 fixed in 0.8.15, 0.9.12 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83615 | MEDIUM6.38 | @xmldom/xmldom 0.8.10 fixed in 0.8.15, 0.9.12 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83616 | MEDIUM6.38 | @xmldom/xmldom 0.8.10 fixed in 0.8.15, 0.9.12 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83619 | MEDIUM6.38 | @xmldom/xmldom 0.8.10 fixed in 0.8.15 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-83613 | MEDIUM6.38 | @xmldom/xmldom 0.8.13 fixed in 0.8.15, 0.9.12 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83614 | MEDIUM6.38 | @xmldom/xmldom 0.8.13 fixed in 0.8.15, 0.9.12 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83615 | MEDIUM6.38 | @xmldom/xmldom 0.8.13 fixed in 0.8.15, 0.9.12 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83616 | MEDIUM6.38 | @xmldom/xmldom 0.8.13 fixed in 0.8.15, 0.9.12 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83619 | MEDIUM6.38 | @xmldom/xmldom 0.8.13 fixed in 0.8.15 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69873 | MEDIUM6.38 | ajv 6.12.6 fixed in 8.18.0, 6.14.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-102990 | MEDIUM6.38 | basic-ftp 5.3.1 fixed in 6.2.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102276 | MEDIUM6.38 | brace-expansion 1.1.11 fixed in 5.0.10, 3.0.7, 2.1.5, 1.1.19 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13149 | MEDIUM6.38 | brace-expansion 1.1.11 fixed in 5.0.7, 1.1.16, 2.1.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-14257 | MEDIUM6.38 | brace-expansion 1.1.11 fixed in 5.0.8, 3.0.3, 2.1.3, 1.1.17 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-69152 | MEDIUM6.38 | brace-expansion 1.1.11 fixed in 1.1.18, 2.1.4, 3.0.6, 5.0.9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33750 | MEDIUM6.38 | brace-expansion 1.1.11 fixed in 5.0.5, 3.0.2, 2.0.3, 1.1.13 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-102276 | MEDIUM6.38 | brace-expansion 2.0.1 fixed in 5.0.10, 3.0.7, 2.1.5, 1.1.19 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13149 | MEDIUM6.38 | brace-expansion 2.0.1 fixed in 5.0.7, 1.1.16, 2.1.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-14257 | MEDIUM6.38 | brace-expansion 2.0.1 fixed in 5.0.8, 3.0.3, 2.1.3, 1.1.17 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-69152 | MEDIUM6.38 | brace-expansion 2.0.1 fixed in 1.1.18, 2.1.4, 3.0.6, 5.0.9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33750 | MEDIUM6.38 | brace-expansion 2.0.1 fixed in 5.0.5, 3.0.2, 2.0.3, 1.1.13 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-102276 | MEDIUM6.38 | brace-expansion 5.0.6 fixed in 5.0.10, 3.0.7, 2.1.5, 1.1.19 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13149 | MEDIUM6.38 | brace-expansion 5.0.6 fixed in 5.0.7, 1.1.16, 2.1.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-14257 | MEDIUM6.38 | brace-expansion 5.0.6 fixed in 5.0.8, 3.0.3, 2.1.3, 1.1.17 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-69152 | MEDIUM6.38 | brace-expansion 5.0.6 fixed in 1.1.18, 2.1.4, 3.0.6, 5.0.9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-102276 | MEDIUM6.38 | brace-expansion 5.0.9 fixed in 5.0.10, 3.0.7, 2.1.5, 1.1.19 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45822 | MEDIUM6.38 | decode-uri-component 0.2.2 fixed in 0.5.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33036 | MEDIUM6.38 | fast-xml-parser 4.1.2 fixed in 5.5.6, 4.5.5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-27942 | MEDIUM6.38 | fast-xml-parser 4.1.2 fixed in 5.3.8, 4.5.4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-33036 | MEDIUM6.38 | fast-xml-parser 5.2.5 fixed in 5.5.6, 4.5.5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-27942 | MEDIUM6.38 | fast-xml-parser 5.2.5 fixed in 5.3.8, 4.5.4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-12143 | MEDIUM6.38 | form-data 2.3.3 fixed in 2.5.6, 3.0.5, 4.0.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-93748 | MEDIUM6.38 | http-cache-semantics 4.2.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-59869 | MEDIUM6.38 | js-yaml 4.1.1 fixed in 3.15.0, 4.3.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-84375 | MEDIUM6.38 | js-yaml 4.1.1 fixed in 4.3.2, 3.15.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59869 | MEDIUM6.38 | js-yaml 4.2.0 fixed in 3.15.0, 4.3.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-84375 | MEDIUM6.38 | js-yaml 4.2.0 fixed in 4.3.2, 3.15.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48801 | MEDIUM6.38 | linkify-it 4.0.1 fixed in 5.0.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59887 | MEDIUM6.38 | linkify-it 4.0.1 fixed in 5.0.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-2327 | MEDIUM6.38 | markdown-it 13.0.2 fixed in 14.1.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-26996 | MEDIUM6.38 | minimatch 10.1.1 fixed in 10.2.1, 9.0.6, 8.0.5, 7.4.7, 6.2.1, 5.1.7, 4.2.4, 3.1.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-26996 | MEDIUM6.38 | minimatch 3.0.4 fixed in 10.2.1, 9.0.6, 8.0.5, 7.4.7, 6.2.1, 5.1.7, 4.2.4, 3.1.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-26996 | MEDIUM6.38 | minimatch 9.0.2 fixed in 10.2.1, 9.0.6, 8.0.5, 7.4.7, 6.2.1, 5.1.7, 4.2.4, 3.1.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-67213 | MEDIUM6.38 | nanoid 3.3.7 fixed in 3.3.18, 5.1.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-67214 | MEDIUM6.38 | nanoid 3.3.7 fixed in 3.3.16, 5.1.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-14874 | MEDIUM6.38 | nodemailer 6.10.1 fixed in 7.0.11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-13033 | MEDIUM6.38 | nodemailer 6.10.1 fixed in 7.0.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-15284 | MEDIUM6.38 | qs 6.11.2 fixed in 6.14.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-82417 | MEDIUM6.38 | qs 6.11.2 fixed in 6.16.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2391 | MEDIUM6.38 | qs 6.11.2 fixed in 6.14.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15284 | MEDIUM6.38 | qs 6.5.2 fixed in 6.14.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-82417 | MEDIUM6.38 | qs 6.5.2 fixed in 6.16.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109869 | MEDIUM6.38 | undici 6.27.0 fixed in 6.29.1, 7.30.1, 8.12.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19534 | MEDIUM6.38 | undici 6.27.0 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109924 | MEDIUM6.38 | undici 6.27.0 fixed in 6.29.1, 7.30.1, 8.12.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109869 | MEDIUM6.38 | undici 6.28.0 fixed in 6.29.1, 7.30.1, 8.12.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19534 | MEDIUM6.38 | undici 6.28.0 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109924 | MEDIUM6.38 | undici 6.28.0 fixed in 6.29.1, 7.30.1, 8.12.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109869 | MEDIUM6.38 | undici 8.10.0 fixed in 6.29.1, 7.30.1, 8.12.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19534 | MEDIUM6.38 | undici 8.10.0 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109841 | MEDIUM6.38 | undici 8.10.0 fixed in 7.30.1, 8.12.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109924 | MEDIUM6.38 | undici 8.10.0 fixed in 6.29.1, 7.30.1, 8.12.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85014 | MEDIUM6.38 | undici 8.10.0 fixed in 7.29.1, 8.10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41907 | MEDIUM6.38 | uuid 13.0.0 fixed in 11.1.1, 12.0.1, 13.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41907 | MEDIUM6.38 | uuid 3.4.0 fixed in 11.1.1, 12.0.1, 13.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41907 | MEDIUM6.38 | uuid 8.3.2 fixed in 11.1.1, 12.0.1, 13.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-88647 | MEDIUM6.29 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88648 | MEDIUM6.29 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-73086 | MEDIUM6.29 | nanoid 3.3.7 fixed in 3.3.12, 5.1.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85152 | MEDIUM6.29 | undici 8.10.0 fixed in 8.10.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl1 2.3.1-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102282 | MEDIUM6.03 | adm-zip 0.5.18 fixed in 0.6.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25896 | MEDIUM6.03 | fast-xml-parser 5.2.5 fixed in 5.3.5, 4.5.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-82659 | MEDIUM6.03 | nodemailer 6.10.1 fixed in 9.0.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM5.95 | libc-bin 2.36-9+deb12u14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM5.95 | libc-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM5.95 | libc6 2.36-9+deb12u14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM5.95 | libc6 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.10.1-3+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.19.0-2+deb12u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-111755 | MEDIUM5.9 | follow-redirects 1.16.0 fixed in 1.16.1 | — | Directly Exposed |
| CVE-2026-19499 | MEDIUM5.78 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM5.78 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25547 | MEDIUM5.52 | @isaacs/brace-expansion 5.0.0 fixed in 5.0.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-39244 | MEDIUM5.52 | adm-zip 0.5.18 fixed in 0.6.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-77301 | MEDIUM5.52 | adm-zip 0.5.18 fixed in 0.6.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-76845 | MEDIUM5.52 | adm-zip 0.5.18 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102278 | MEDIUM5.52 | brace-expansion 1.1.11 fixed in 5.0.11, 3.0.8, 2.1.6, 1.1.20 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102278 | MEDIUM5.52 | brace-expansion 2.0.1 fixed in 5.0.11, 3.0.8, 2.1.6, 1.1.20 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102278 | MEDIUM5.52 | brace-expansion 5.0.6 fixed in 5.0.11, 3.0.8, 2.1.6, 1.1.20 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102278 | MEDIUM5.52 | brace-expansion 5.0.9 fixed in 5.0.11, 3.0.8, 2.1.6, 1.1.20 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-71330 | MEDIUM5.52 | image-size 1.0.0 fixed in 2.0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27904 | MEDIUM5.52 | minimatch 10.1.1 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27904 | MEDIUM5.52 | minimatch 3.0.4 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27904 | MEDIUM5.52 | minimatch 9.0.2 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-55565 | MEDIUM5.52 | nanoid 3.3.7 fixed in 5.0.9, 3.3.8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-82662 | MEDIUM5.52 | nodemailer 6.10.1 fixed in 8.0.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-110871 | MEDIUM5.52 | nodemailer 6.10.1 fixed in 10.0.10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-33671 | MEDIUM5.52 | picomatch 2.3.0 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33671 | MEDIUM5.52 | picomatch 4.0.2 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-16728 | MEDIUM5.52 | undici 6.27.0 fixed in 6.28.0, 7.29.0, 8.9.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-16729 | MEDIUM5.52 | undici 6.27.0 fixed in 6.28.0, 7.29.0, 8.9.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7783 | MEDIUM5.4 | form-data 2.3.3 fixed in 2.5.4, 3.0.4, 4.0.4 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl1 2.3.1-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM5.35 | libattr1 1:2.5.1-4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.36-9+deb12u14 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.36-9+deb12u14 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13465 | MEDIUM5.3 | lodash 4.17.21 fixed in 4.17.23 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0842 | MEDIUM5.3 | xml2js 0.4.23 fixed in 0.5.0 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.24.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18938 | MEDIUM5.27 | libp11-kit0 0.24.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-28155 | MEDIUM5.18 | request 2.88.2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-67693 | MEDIUM5.02 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33349 | MEDIUM5.02 | fast-xml-parser 4.1.2 fixed in 4.5.5, 5.5.7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33349 | MEDIUM5.02 | fast-xml-parser 5.2.5 fixed in 4.5.5, 5.5.7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27903 | MEDIUM5.02 | minimatch 10.1.1 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-27903 | MEDIUM5.02 | minimatch 3.0.4 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-27903 | MEDIUM5.02 | minimatch 9.0.2 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-17495 | MEDIUM5.02 | moment 2.30.1 fixed in 2.31.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-104844 | MEDIUM5.02 | postcss-selector-parser 7.1.4 fixed in 7.1.6, 6.1.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-85024 | MEDIUM5.02 | undici 6.27.0 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-85024 | MEDIUM5.02 | undici 6.28.0 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-18149 | MEDIUM5.02 | undici 8.10.0 fixed in 7.29.1, 8.10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84890 | MEDIUM5.02 | undici 8.10.0 fixed in 7.29.1, 8.10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-85024 | MEDIUM5.02 | undici 8.10.0 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc6 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM4.67 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM4.67 | libudev1 252.39-1~deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41650 | MEDIUM4.59 | fast-xml-parser 3.21.1 fixed in 5.7.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41650 | MEDIUM4.59 | fast-xml-parser 4.1.2 fixed in 5.7.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41650 | MEDIUM4.59 | fast-xml-parser 5.2.5 fixed in 5.7.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15157 | MEDIUM4.59 | undici 6.27.0 fixed in 6.28.0, 7.29.0, 8.9.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM4.5 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM4.5 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-95184 | MEDIUM4.5 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-83610 | MEDIUM4.5 | @xmldom/xmldom 0.8.10 fixed in 0.8.15, 0.9.12 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83611 | MEDIUM4.5 | @xmldom/xmldom 0.8.10 fixed in 0.8.15, 0.9.12 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83610 | MEDIUM4.5 | @xmldom/xmldom 0.8.13 fixed in 0.8.15, 0.9.12 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83611 | MEDIUM4.5 | @xmldom/xmldom 0.8.13 fixed in 0.8.15, 0.9.12 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-102277 | MEDIUM4.5 | brace-expansion 1.1.11 fixed in 5.0.12, 3.0.9, 2.1.7, 1.1.21 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102277 | MEDIUM4.5 | brace-expansion 2.0.1 fixed in 5.0.12, 3.0.9, 2.1.7, 1.1.21 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102277 | MEDIUM4.5 | brace-expansion 5.0.6 fixed in 5.0.12, 3.0.9, 2.1.7, 1.1.21 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102277 | MEDIUM4.5 | brace-expansion 5.0.9 fixed in 5.0.12, 3.0.9, 2.1.7, 1.1.21 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25128 | MEDIUM4.5 | fast-xml-parser 5.2.5 fixed in 5.3.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-31808 | MEDIUM4.5 | file-type 16.5.4 fixed in 21.3.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-101910 | MEDIUM4.5 | ip-address 10.5.0 fixed in 10.5.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-101911 | MEDIUM4.5 | ip-address 10.5.0 fixed in 10.7.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-101912 | MEDIUM4.5 | ip-address 10.5.0 fixed in 10.7.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-101913 | MEDIUM4.5 | ip-address 10.5.0 fixed in 10.5.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-111997 | MEDIUM4.5 | ip-address 10.5.0 fixed in 10.7.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53550 | MEDIUM4.5 | js-yaml 4.1.1 fixed in 4.2.0, 3.15.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2950 | MEDIUM4.5 | lodash 4.17.21 fixed in 4.18.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48988 | MEDIUM4.5 | markdown-it 13.0.2 fixed in 14.2.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33672 | MEDIUM4.5 | picomatch 2.3.0 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33672 | MEDIUM4.5 | picomatch 4.0.2 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8723 | MEDIUM4.5 | qs 6.11.2 fixed in 6.15.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84947 | MEDIUM4.5 | undici 8.10.0 fixed in 7.29.1, 8.10.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85008 | MEDIUM4.5 | undici 8.10.0 fixed in 7.29.1, 8.10.2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-7608 | MEDIUM4.5 | yargs-parser 7.0.0 fixed in 13.1.2, 15.0.1, 18.1.1, 5.0.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-5+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.36-9+deb12u14 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.36-9+deb12u14 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc6 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.03 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-103923 | MEDIUM4 | katex 0.16.23 fixed in 0.18.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-76642 | LOW3.98 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW3.98 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW3.98 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW3.98 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW3.98 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW3.98 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW3.98 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW3.98 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.12-1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59873 | LOW3.82 | tar 6.1.11 fixed in 7.5.19 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-59874 | LOW3.82 | tar 6.1.11 fixed in 7.5.18 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-73566 | LOW3.82 | tar 6.1.11 fixed in 7.5.21 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-59871 | LOW3.82 | tar 6.1.11 fixed in 7.5.18 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-73566 | LOW3.82 | tar 7.5.19 fixed in 7.5.21 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-21538 | LOW3.74 | cross-spawn 7.0.3 fixed in 7.0.5, 6.0.6 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2011-3374 | LOW3.7 | libapt-pkg6.0 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-111766 | LOW3.7 | markdown-it 13.0.2 fixed in 14.3.3, 15.0.3 | — | Directly Exposed |
| CVE-2026-26960 | LOW3.62 | tar 6.1.11 fixed in 7.5.8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-53613 | LOW3.57 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW3.57 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW3.57 | mount 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW3.57 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW3.57 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW3.57 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW3.57 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW3.57 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-19542 | LOW3.57 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-45853 | LOW3.53 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 3.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4800 | LOW3.53 | lodash 4.17.21 fixed in 4.18.0 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-26136 | LOW3.53 | tough-cookie 2.5.0 fixed in 4.1.3 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2016-2781 | LOW3.31 | coreutils 9.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-28863 | LOW3.31 | tar 6.1.11 fixed in 6.2.1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-29786 | LOW3.21 | tar 6.1.11 fixed in 7.5.10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-bin 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-97399 | LOW3.15 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.15 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18540 | LOW3.15 | undici 6.27.0 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18540 | LOW3.15 | undici 6.28.0 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18540 | LOW3.15 | undici 8.10.0 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56391 | LOW3.11 | coreutils 9.1-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW3.11 | coreutils 9.1-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23745 | LOW3.11 | tar 6.1.11 fixed in 7.5.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-23950 | LOW3.01 | tar 6.1.11 fixed in 7.5.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-31486 | LOW2.92 | perl-base 5.36.0-7+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-15534 | LOW2.91 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-102473 | LOW2.8 | dash 0.5.12-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31802 | LOW2.8 | tar 6.1.11 fixed in 7.5.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53655 | LOW2.8 | tar 6.1.11 fixed in 7.5.16 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2013-4392 | LOW2.8 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 252.39-1~deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-84961 | LOW2.78 | undici 8.10.0 fixed in 7.29.1, 8.10.2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc-bin 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9192 | LOW2.7 | libc-bin 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc6 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9192 | LOW2.7 | libc6 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6829 | LOW2.7 | libgcrypt20 1.10.1-3+deb12u1 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3807 | LOW2.7 | ansi-regex 3.0.0 fixed in 6.0.1, 5.0.1, 4.1.1, 3.0.1 | 3.6% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4068 | LOW2.7 | braces 3.0.2 fixed in 3.0.3 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-64756 | LOW2.7 | glob 10.3.1 fixed in 11.1.0, 10.5.0 | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-37620 | LOW2.7 | html-minifier 4.0.0 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-3517 | LOW2.7 | minimatch 3.0.4 fixed in 3.0.5 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-25883 | LOW2.7 | semver 6.3.0 fixed in 7.5.2, 6.3.1, 5.7.2 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-25883 | LOW2.7 | semver 7.3.5 fixed in 7.5.2, 6.3.1, 5.7.2 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53910 | LOW2.7 | diffutils 1:3.8-4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-5891 | LOW2.7 | pm2 5.4.3 fixed in 7.0.0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-59875 | LOW2.7 | tar 6.1.11 fixed in 7.5.17 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-83608 | LOW2.63 | @xmldom/xmldom 0.8.10 fixed in 0.8.15, 0.9.12 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83608 | LOW2.63 | @xmldom/xmldom 0.8.13 fixed in 0.8.15, 0.9.12 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-5889 | LOW2.63 | brace-expansion 1.1.11 fixed in 2.0.2, 1.1.12, 3.0.1, 4.0.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-5889 | LOW2.63 | brace-expansion 2.0.1 fixed in 2.0.2, 1.1.12, 3.0.1, 4.0.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-46653 | LOW2.63 | formidable 2.1.2 fixed in 3.5.3, 2.1.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24842 | LOW2.51 | tar 6.1.11 fixed in 7.5.7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.45 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.45 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.45 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.45 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.42 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.42 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.42 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.12-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-18477 | LOW2.24 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.24 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-102474 | LOW2.04 | dash 0.5.12-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | NONE0 | libtinfo6 6.4-4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.4-4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.4-4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libtinfo6 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-bin 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2007-5686 | NONE0 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.5.2-6+deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.5.2-6+deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.5.2-6+deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.5.2-6+deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-30258 | NONE0 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68972 | NONE0 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules-bin 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-runtime 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam0g 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-105712 | NONE0 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-3219 | NONE0 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57062 | NONE0 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.15-2+b13 No fix yet | — | Not Applicable |
| CVE-2026-95209 | NONE0 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95210 | NONE0 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-82560 | NONE0 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 3.06-4 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | — | Not Applicable |
| DLA-4854-1 | NONE0 | tzdata 2026c-0+deb12u1 fixed in 2026e-0+deb12u1 | — | Not Applicable |
| CVE-2026-85091 | NONE0 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-27789 | NONE0 | @babel/runtime 7.22.5 fixed in 7.26.10, 8.0.0-alpha.17 | 0.6% Theoretical Threat | Not Applicable |
| GHSA-8238-w5pm-2374 | NONE0 | adm-zip 0.5.18 fixed in 0.6.1 | — | Not Applicable |
| GHSA-rcw4-f5rp-g42v | NONE0 | adm-zip 0.5.18 fixed in 0.6.1 | — | Not Applicable |
| GHSA-c6fg-446q-cg94 | NONE0 | adm-zip 0.5.18 fixed in 0.6.1 | — | Not Applicable |
| GHSA-p634-w6r4-rjp2 | NONE0 | adm-zip 0.5.18 fixed in 0.6.1 | — | Not Applicable |
| GHSA-5p4m-2wfm-xmqj | NONE0 | js-yaml 4.1.1 fixed in 4.3.1, 3.15.1 | — | Not Applicable |
| GHSA-5p4m-2wfm-xmqj | NONE0 | js-yaml 4.2.0 fixed in 4.3.1, 3.15.1 | — | Not Applicable |
| GHSA-253c-mchw-3w2r | NONE0 | markdown-it 13.0.2 fixed in 15.0.1, 14.3.1 | — | Not Applicable |
| GHSA-2x7j-588g-ccc2 | NONE0 | nodemailer 6.10.1 fixed in 9.1.0 | — | Not Applicable |
| GHSA-v53p-9fqp-m79j | NONE0 | nodemailer 6.10.1 fixed in 10.0.6 | — | Not Applicable |
| GHSA-268h-hp4c-crq3 | NONE0 | nodemailer 6.10.1 fixed in 8.0.9 | — | Not Applicable |
| GHSA-6vj9-mwq6-2f5v | NONE0 | nodemailer 6.10.1 fixed in 10.0.2 | — | Not Applicable |
| GHSA-85x2-q946-cp5h | NONE0 | nodemailer 6.10.1 fixed in 10.1.4 | — | Not Applicable |
| GHSA-8c8m-p3m8-cjg8 | NONE0 | nodemailer 6.10.1 fixed in 10.1.4 | — | Not Applicable |
| GHSA-8m3c-c648-2xjj | NONE0 | nodemailer 6.10.1 fixed in 9.1.1 | — | Not Applicable |
| GHSA-8vvx-rff5-p5rq | NONE0 | nodemailer 6.10.1 fixed in 10.0.2 | — | Not Applicable |
| GHSA-cc9r-2j5m-2m83 | NONE0 | nodemailer 6.10.1 fixed in 9.1.0 | — | Not Applicable |
| GHSA-m943-m63m-w62w | NONE0 | nodemailer 6.10.1 fixed in 10.1.4 | — | Not Applicable |
| GHSA-vvjj-xcjg-gr5g | NONE0 | nodemailer 6.10.1 fixed in 8.0.5 | — | Not Applicable |
| GHSA-wmmp-3585-3rmp | NONE0 | nodemailer 6.10.1 fixed in 9.1.0 | — | Not Applicable |
| GHSA-wqvq-jvpq-h66f | NONE0 | nodemailer 6.10.1 fixed in 8.0.9 | — | Not Applicable |
| GHSA-c7w3-x93f-qmm8 | NONE0 | nodemailer 6.10.1 fixed in 8.0.4 | — | Not Applicable |
| GHSA-rgj7-g3m4-5g8c | NONE0 | sharp 0.35.0 fixed in 0.35.4 | — | Not Applicable |
| GHSA-wq5f-xc86-pv6w | NONE0 | sharp 0.35.0 fixed in 0.35.5 | — | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.