This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker could exploit sandbox escapes in vm2 to achieve remote code execution on the host, or bypass JWT authentication to impersonate any user, leading to full site compromise. Disabling the vm2 sandbox functionality, if not essential, would fully eliminate the sandbox escape vulnerabilities. The JWT bypass requires upgrading the jsonwebtoken package; no other full mitigations are available for the critical findings.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2023-32314 | CRITICAL10 | vm2 3.9.17 fixed in 3.9.18 | 5.6% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2023-37466 | CRITICAL10 | vm2 3.9.17 fixed in 3.10.0 | 2.3% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2023-37903 | CRITICAL10 | vm2 3.9.17 No fix yet | 3.3% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-22709 | CRITICAL10 | vm2 3.9.17 fixed in 3.10.2 | 1.2% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2024-29415 | CRITICAL9.8 | ip 2.0.1 No fix yet | 8.3% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2015-9235 | CRITICAL9.8 | jsonwebtoken 0.1.0 fixed in 4.2.2 | 7.2% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2015-9235 | CRITICAL9.8 | jsonwebtoken 0.4.0 fixed in 4.2.2 | 7.2% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2019-10744 | CRITICAL9.1 | lodash 2.4.2 fixed in 4.17.12 | 5.0% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-26332 | HIGH8.5 | vm2 3.9.17 fixed in 3.11.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-43997 | HIGH8.5 | vm2 3.9.17 fixed in 3.11.0 | 0.7% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-44005 | HIGH8.5 | vm2 3.9.17 fixed in 3.11.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-44006 | HIGH8.5 | vm2 3.9.17 fixed in 3.11.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-44007 | HIGH8.42 | vm2 3.9.17 fixed in 3.11.1 | 0.8% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-31789 | HIGH8.33 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.19-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-26956 | HIGH8.33 | vm2 3.9.17 fixed in 3.10.5 | 0.7% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-44008 | HIGH8.33 | vm2 3.9.17 fixed in 3.11.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44009 | HIGH8.33 | vm2 3.9.17 fixed in 3.11.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45411 | HIGH8.33 | vm2 3.9.17 fixed in 3.11.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-23337 | HIGH8.28 | lodash 2.4.2 fixed in 4.17.21 | 22.4% High Exploitation Risk | Directly Exposed |
| CVE-2026-45447 | HIGH8.1 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33937 | HIGH7.84 | handlebars 4.7.7 fixed in 4.7.9 | 1.3% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-4800 | HIGH7.84 | lodash 4.17.21 fixed in 4.18.0 | 1.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-45445 | HIGH7.73 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-46233 | HIGH7.73 | crypto-js 3.3.0 fixed in 4.2.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-24118 | HIGH7.73 | vm2 3.9.17 fixed in 3.11.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-24120 | HIGH7.73 | vm2 3.9.17 fixed in 3.10.5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.36-9+deb12u10 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.36-9+deb12u10 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4068 | HIGH7.5 | braces 2.3.2 fixed in 3.0.3 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-64756 | HIGH7.5 | glob 10.4.5 fixed in 11.1.0, 10.5.0 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25881 | HIGH7.5 | http-cache-semantics 3.8.1 fixed in 4.1.1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-18214 | HIGH7.5 | moment 2.0.0 fixed in 2.19.3 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24785 | HIGH7.5 | moment 2.0.0 fixed in 2.29.2 | 5.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25887 | HIGH7.5 | sanitize-html 1.4.2 fixed in 2.7.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-32695 | HIGH7.5 | socket.io-parser 4.0.5 fixed in 4.2.3, 3.4.3, 3.3.4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-8203 | HIGH7.4 | lodash.set 4.3.2 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-44001 | HIGH7.31 | vm2 3.9.17 fixed in 3.11.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44004 | HIGH7.31 | vm2 3.9.17 fixed in 3.11.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-15084 | HIGH7.28 | express-jwt 0.1.3 fixed in 6.0.0 | 1.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33941 | MEDIUM6.97 | handlebars 4.7.7 fixed in 4.7.9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6 2.36-9+deb12u10 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.19-1~deb12u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33938 | MEDIUM6.88 | handlebars 4.7.7 fixed in 4.7.9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33940 | MEDIUM6.88 | handlebars 4.7.7 fixed in 4.7.9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-23539 | MEDIUM6.88 | jsonwebtoken 0.1.0 fixed in 9.0.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-23539 | MEDIUM6.88 | jsonwebtoken 0.4.0 fixed in 9.0.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-24781 | MEDIUM6.88 | vm2 3.9.17 fixed in 3.11.0 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-27837 | MEDIUM6.66 | dottie 2.0.6 fixed in 2.0.7 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2022-41940 | MEDIUM6.5 | engine.io 4.1.2 fixed in 3.6.1, 6.2.1 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2018-3721 | MEDIUM6.5 | lodash 2.4.2 fixed in >=4.17.5 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-4055 | MEDIUM6.5 | moment 2.0.0 fixed in >=2.11.2 | 9.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23540 | MEDIUM6.46 | jsonwebtoken 0.1.0 fixed in 9.0.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-23540 | MEDIUM6.46 | jsonwebtoken 0.4.0 fixed in 9.0.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.18-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM6.38 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.19-1~deb12u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM6.38 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33750 | MEDIUM6.38 | brace-expansion 1.1.12 fixed in 5.0.5, 3.0.2, 2.0.3, 1.1.13 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33750 | MEDIUM6.38 | brace-expansion 2.0.2 fixed in 5.0.5, 3.0.2, 2.0.3, 1.1.13 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24001 | MEDIUM6.38 | diff 4.0.2 fixed in 8.0.3, 5.2.2, 4.0.4, 3.5.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33939 | MEDIUM6.38 | handlebars 4.7.7 fixed in 4.7.9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-65945 | MEDIUM6.38 | jws 0.2.6 fixed in 3.2.3, 4.0.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-26996 | MEDIUM6.38 | minimatch 3.0.5 fixed in 10.2.1, 9.0.6, 8.0.5, 7.4.7, 6.2.1, 5.1.7, 4.2.4, 3.1.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-26996 | MEDIUM6.38 | minimatch 3.0.8 fixed in 10.2.1, 9.0.6, 8.0.5, 7.4.7, 6.2.1, 5.1.7, 4.2.4, 3.1.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-26996 | MEDIUM6.38 | minimatch 3.1.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.5% Theoretical Threat | Directly Exposed |
| CVE-2026-26996 | MEDIUM6.38 | minimatch 5.1.6 fixed in 10.2.1, 9.0.6, 8.0.5, 7.4.7, 6.2.1, 5.1.7, 4.2.4, 3.1.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-26996 | MEDIUM6.38 | minimatch 9.0.5 fixed in 10.2.1, 9.0.6, 8.0.5, 7.4.7, 6.2.1, 5.1.7, 4.2.4, 3.1.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-2359 | MEDIUM6.38 | multer 1.4.5-lts.2 fixed in 2.1.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3304 | MEDIUM6.38 | multer 1.4.5-lts.2 fixed in 2.1.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3520 | MEDIUM6.38 | multer 1.4.5-lts.2 fixed in 2.1.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15284 | MEDIUM6.38 | qs 6.13.0 fixed in 6.14.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2391 | MEDIUM6.38 | qs 6.13.0 fixed in 6.14.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-30951 | MEDIUM6.38 | sequelize 6.37.7 fixed in 6.37.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33151 | MEDIUM6.38 | socket.io-parser 4.0.5 fixed in 3.3.5, 3.4.4, 4.2.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-59343 | MEDIUM6.38 | tar-fs 2.1.3 fixed in 3.1.1, 2.1.4, 1.16.6 | 0.5% 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.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45736 | MEDIUM6.38 | ws 8.17.1 fixed in 8.20.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.18-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38355 | MEDIUM6.21 | socket.io 3.1.2 fixed in 2.5.1, 4.6.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-44000 | MEDIUM6.12 | vm2 3.9.17 fixed in 3.11.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-16016 | MEDIUM6.1 | sanitize-html 1.4.2 fixed in 1.11.4 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc6 2.36-9+deb12u10 fixed in 2.36-9+deb12u11 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-37890 | MEDIUM5.9 | ws 7.4.6 fixed in 5.2.4, 6.2.3, 7.5.10, 8.17.1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.17-1~deb12u3 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-16487 | MEDIUM5.6 | lodash 2.4.2 fixed in >=4.17.11 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6 2.36-9+deb12u10 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.36-9+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27904 | MEDIUM5.52 | minimatch 3.0.5 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.8 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.1.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-2026-27904 | MEDIUM5.52 | minimatch 5.1.6 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.5 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-2021-23771 | MEDIUM5.52 | notevil 1.3.3 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-33671 | MEDIUM5.52 | picomatch 2.3.1 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33671 | MEDIUM5.52 | picomatch 4.0.3 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-23541 | MEDIUM5.35 | jsonwebtoken 0.1.0 fixed in 9.0.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-23541 | MEDIUM5.35 | jsonwebtoken 0.4.0 fixed in 9.0.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.36-9+deb12u10 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.36-9+deb12u10 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-33987 | MEDIUM5.3 | got 8.3.2 fixed in 12.1.0, 11.8.5 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4067 | MEDIUM5.3 | micromatch 3.1.10 fixed in 4.0.8 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-26539 | MEDIUM5.3 | sanitize-html 1.4.2 fixed in 2.3.1 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-26540 | MEDIUM5.3 | sanitize-html 1.4.2 fixed in 2.3.2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21501 | MEDIUM5.3 | sanitize-html 1.4.2 fixed in 2.12.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42338 | MEDIUM5.18 | ip-address 10.0.1 fixed in 10.1.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2016-1000237 | MEDIUM5.18 | sanitize-html 1.4.2 fixed in >=1.4.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2019-25225 | MEDIUM5.18 | sanitize-html 1.4.2 fixed in 2.0.0-beta | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.36-9+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6 2.36-9+deb12u10 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.02 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.19-1~deb12u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.18-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.18-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27903 | MEDIUM5.02 | minimatch 3.0.5 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.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27903 | MEDIUM5.02 | minimatch 3.0.8 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.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27903 | MEDIUM5.02 | minimatch 3.1.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.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27903 | MEDIUM5.02 | minimatch 5.1.6 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.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27903 | MEDIUM5.02 | minimatch 9.0.5 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.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44002 | MEDIUM4.93 | vm2 3.9.17 fixed in 3.11.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44003 | MEDIUM4.93 | vm2 3.9.17 fixed in 3.11.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgomp1 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.18-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6 2.36-9+deb12u10 fixed in 2.36-9+deb12u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.36-9+deb12u10 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl3 3.0.17-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31808 | MEDIUM4.5 | file-type 16.5.4 fixed in 21.3.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-64718 | MEDIUM4.5 | js-yaml 3.14.1 fixed in 4.1.1, 3.14.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2950 | MEDIUM4.5 | lodash 2.4.2 fixed in 4.18.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13465 | MEDIUM4.5 | lodash 4.17.21 fixed in 4.17.23 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-2950 | MEDIUM4.5 | lodash 4.17.21 fixed in 4.18.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-48997 | MEDIUM4.5 | multer 1.4.5-lts.2 fixed in 2.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-7338 | MEDIUM4.5 | multer 1.4.5-lts.2 fixed in 2.0.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4867 | MEDIUM4.5 | path-to-regexp 0.1.12 fixed in 0.1.13 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33672 | MEDIUM4.5 | picomatch 2.3.1 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33672 | MEDIUM4.5 | picomatch 4.0.3 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-32313 | MEDIUM4.5 | vm2 3.9.17 fixed in 3.9.18 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.36-9+deb12u10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.36-9+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM4.25 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15467 | MEDIUM4.06 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.18-1~deb12u2 | 48.7% High Exploitation Risk | Post-Exploit |
| CVE-2025-68160 | MEDIUM4 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.18-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33916 | MEDIUM4 | handlebars 4.7.7 fixed in 4.7.9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.36-9+deb12u10 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-26960 | LOW3.62 | tar 4.4.19 fixed in 7.5.8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-26960 | LOW3.62 | tar 6.2.1 fixed in 7.5.8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-26960 | LOW3.62 | tar 7.4.3 fixed in 7.5.8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-8058 | LOW3.57 | libc6 2.36-9+deb12u10 fixed in 2.36-9+deb12u13 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-1010022 | LOW3.53 | libc6 2.36-9+deb12u10 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-47131 | LOW3.48 | vm2 3.9.17 fixed in 3.11.4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-47137 | LOW3.48 | vm2 3.9.17 fixed in 3.11.4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-47140 | LOW3.48 | vm2 3.9.17 fixed in 3.11.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6 2.36-9+deb12u10 fixed in 2.36-9+deb12u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.18-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3449 | LOW3.4 | @tootallnate/once 1.1.2 fixed in 3.0.1, 2.0.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3449 | LOW3.4 | @tootallnate/once 2.0.0 fixed in 3.0.1, 2.0.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-29786 | LOW3.21 | tar 4.4.19 fixed in 7.5.10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-29786 | LOW3.21 | tar 6.2.1 fixed in 7.5.10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-29786 | LOW3.21 | tar 7.4.3 fixed in 7.5.10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6 2.36-9+deb12u10 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45446 | LOW3.15 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47764 | LOW3.15 | cookie 0.4.2 fixed in 0.7.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-23745 | LOW3.11 | tar 4.4.19 fixed in 7.5.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-23745 | LOW3.11 | tar 6.2.1 fixed in 7.5.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-23745 | LOW3.11 | tar 7.4.3 fixed in 7.5.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-9232 | LOW3.1 | libssl3 3.0.17-1~deb12u2 fixed in 3.0.17-1~deb12u3 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31802 | LOW2.8 | tar 4.4.19 fixed in 7.5.11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31802 | LOW2.8 | tar 6.2.1 fixed in 7.5.11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31802 | LOW2.8 | tar 7.4.3 fixed in 7.5.11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-24842 | LOW2.51 | tar 4.4.19 fixed in 7.5.7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-24842 | LOW2.51 | tar 6.2.1 fixed in 7.5.7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-24842 | LOW2.51 | tar 7.4.3 fixed in 7.5.7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-28863 | LOW1.99 | tar 4.4.19 fixed in 6.2.1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-23950 | LOW1.81 | tar 4.4.19 fixed in 7.5.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23950 | LOW1.81 | tar 6.2.1 fixed in 7.5.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23950 | LOW1.81 | tar 7.4.3 fixed in 7.5.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-27587 | NONE0 | libssl3 3.0.17-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| NSWG-ECO-428 | NONE0 | base64url 0.0.6 fixed in >=3.0.0 | — | Not Applicable |
| GHSA-rvg8-pwq2-xj7q | NONE0 | base64url 0.0.6 fixed in 3.0.0 | — | Not Applicable |
| GHSA-7rx3-28cr-v5wh | NONE0 | handlebars 4.7.7 fixed in 4.7.9 | — | Not Applicable |
| GHSA-442j-39wm-28r2 | NONE0 | handlebars 4.7.7 fixed in 4.7.9 | — | Not Applicable |
| CVE-2026-53550 | NONE0 | js-yaml 3.14.1 fixed in 4.2.0 | — | Not Applicable |
| NSWG-ECO-17 | NONE0 | jsonwebtoken 0.1.0 fixed in >=4.2.2 | — | Not Applicable |
| NSWG-ECO-17 | NONE0 | jsonwebtoken 0.4.0 fixed in >=4.2.2 | — | Not Applicable |
| CVE-2016-1000223 | NONE0 | jws 0.2.6 fixed in >=3.0.0 | — | Not Applicable |
| GHSA-5mrr-rgp6-x4gr | NONE0 | marsdb 0.6.11 No fix yet | — | Not Applicable |
| CVE-2025-57349 | NONE0 | messageformat 2.3.0 fixed in 3.0.0-beta.0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-47935 | NONE0 | multer 1.4.5-lts.2 fixed in 2.0.0 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-47944 | NONE0 | multer 1.4.5-lts.2 fixed in 2.0.0 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-5079 | NONE0 | multer 1.4.5-lts.2 fixed in 2.2.0, 3.0.0-alpha.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8723 | NONE0 | qs 6.13.0 fixed in 6.15.2 | 0.3% Theoretical Threat | Not Applicable |
| NSWG-ECO-154 | NONE0 | sanitize-html 1.4.2 fixed in >=1.11.4 | — | Not Applicable |
| CVE-2026-53655 | NONE0 | tar 4.4.19 fixed in 7.5.16 | — | Not Applicable |
| CVE-2026-53655 | NONE0 | tar 6.2.1 fixed in 7.5.16 | — | Not Applicable |
| CVE-2026-53655 | NONE0 | tar 7.4.3 fixed in 7.5.16 | — | Not Applicable |
| CVE-2025-12758 | NONE0 | validator 13.15.15 fixed in 13.15.22 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-56200 | NONE0 | validator 13.15.15 fixed in 13.15.20 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47208 | NONE0 | vm2 3.9.17 fixed in 3.11.4 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-47210 | NONE0 | vm2 3.9.17 fixed in 3.11.4 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-47135 | NONE0 | vm2 3.9.17 fixed in 3.11.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-47139 | NONE0 | vm2 3.9.17 fixed in 3.11.4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-47209 | NONE0 | vm2 3.9.17 fixed in 3.11.4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-47141 | NONE0 | vm2 3.9.17 fixed in 3.11.4 | 0.5% Theoretical Threat | Not Applicable |
| GHSA-2cm2-m3w5-gp2f | NONE0 | vm2 3.9.17 fixed in 3.11.2 | — | Not Applicable |
| GHSA-q3fm-4wcw-g57x | NONE0 | vm2 3.9.17 fixed in 3.11.4 | — | Not Applicable |
| CVE-2026-48779 | NONE0 | ws 7.4.6 fixed in 5.2.5, 6.2.4, 7.5.11, 8.21.0 | — | Not Applicable |
| CVE-2026-48779 | NONE0 | ws 8.17.1 fixed in 5.2.5, 6.2.4, 7.5.11, 8.21.0 | — | Not Applicable |