Last scanned:
This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker who sends a crafted compressed request to the RedisInsight API on port 5540 could crash the service or run code inside the RedisInsight process, gaining control of the application and the Redis connection details it holds. Note: CVE-2026-111181 affects the body parsing path in the default configuration, so anyone who reaches the port can crash the API process with one request. Remediation requires upgrading the vulnerable Node.js runtime and dependencies and rebuilding the image before any production use.
Hardening plan for this image · 4 steps. The first closes an actively exploited CVE.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-111497 | CRITICAL10 | node 22.22.0 No fix yet | 88.0% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2026-111181 | HIGH7.5 | body-parser 1.20.3 fixed in 2.4.0, 1.20.9 | 0.4% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-111181 | HIGH7.5 | body-parser 2.2.1 fixed in 2.4.0, 1.20.9 | 0.4% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-48779 | HIGH7.5 | ws 8.17.1 fixed in 5.2.5, 6.2.4, 7.5.11, 8.21.0 | 1.4% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-21710 | MEDIUM6.9 | node 22.22.0 No fix yet | 25.4% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-69192 | MEDIUM6.88 | ip-address 9.0.5 fixed in 10.3.1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56847 | MEDIUM6.1 | node 22.22.0 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-109461 | MEDIUM6 | @azure/msal-node 5.0.2 fixed in 7.1.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-39244 | MEDIUM6 | adm-zip 0.5.10 fixed in 0.6.0 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-77301 | MEDIUM6 | adm-zip 0.5.10 fixed in 0.6.1 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| GHSA-8238-w5pm-2374 | MEDIUM6 | adm-zip 0.5.10 fixed in 0.6.1 | — | Directly ExposedContext importance: MEDIUM |
| GHSA-rcw4-f5rp-g42v | MEDIUM6 | adm-zip 0.5.10 fixed in 0.6.1 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102276 | MEDIUM6 | brace-expansion 2.0.2 fixed in 5.0.10, 3.0.7, 2.1.5, 1.1.19 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102278 | MEDIUM6 | brace-expansion 2.0.2 fixed in 5.0.11, 3.0.8, 2.1.6, 1.1.20 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-14257 | MEDIUM6 | brace-expansion 2.0.2 fixed in 5.0.8, 3.0.3, 2.1.3, 1.1.17 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-69152 | MEDIUM6 | brace-expansion 2.0.2 fixed in 1.1.18, 2.1.4, 3.0.6, 5.0.9 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33750 | MEDIUM6 | brace-expansion 2.0.2 fixed in 5.0.5, 3.0.2, 2.0.3, 1.1.13 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102599 | MEDIUM6 | engine.io 6.6.2 fixed in 6.6.10 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59724 | MEDIUM6 | engine.io 6.6.2 fixed in 6.6.7 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59725 | MEDIUM6 | engine.io 6.6.2 fixed in 6.6.7 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-45820 | MEDIUM6 | fflate 0.8.2 fixed in 0.4.9, 0.5.4, 0.6.11, 0.7.5, 0.8.3 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-26996 | MEDIUM6 | 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.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-27903 | MEDIUM6 | 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.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-27904 | MEDIUM6 | 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 ExposedContext importance: MEDIUM |
| CVE-2026-113872 | MEDIUM6 | multer 2.0.2 fixed in 2.5.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-2359 | MEDIUM6 | multer 2.0.2 fixed in 2.1.0 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-3304 | MEDIUM6 | multer 2.0.2 fixed in 2.1.0 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-3520 | MEDIUM6 | multer 2.0.2 fixed in 2.1.1 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-5079 | MEDIUM6 | multer 2.0.2 fixed in 2.2.0, 3.0.0-alpha.2 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-77078 | MEDIUM6 | multer 2.0.2 fixed in 2.3.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-82333 | MEDIUM6 | multer 2.0.2 fixed in 2.3.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-5038 | MEDIUM6 | multer 2.0.2 fixed in 2.2.0, 3.0.0-alpha.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-69185 | MEDIUM6 | socket.io-parser 4.2.6 fixed in 4.2.7, 3.4.5, 3.3.6 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-48937 | MEDIUM6 | node 22.22.0 No fix yet | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-63073 | MEDIUM5.9 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-12590 | MEDIUM5.9 | body-parser 1.20.3 fixed in 1.20.6, 2.3.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-12590 | MEDIUM5.9 | body-parser 2.2.1 fixed in 1.20.6, 2.3.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-104844 | MEDIUM5.9 | postcss-selector-parser 7.1.0 fixed in 7.1.6, 6.1.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-21713 | MEDIUM5.9 | node 22.22.0 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-21717 | MEDIUM5.9 | node 22.22.0 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4800 | MEDIUM5.88 | lodash 4.17.21 fixed in 4.18.0 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-73651 | MEDIUM5.7 | typeorm 0.3.29 fixed in 0.3.31, 1.1.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102282 | MEDIUM5.68 | adm-zip 0.5.10 fixed in 0.6.1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6042 | MEDIUM5.5 | musl-utils 1.2.5-r21 fixed in 1.2.5-r22 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90711 | MEDIUM5.46 | proxy-addr 2.0.7 fixed in 2.0.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48758 | MEDIUM5.4 | @sigstore/core 2.0.0 fixed in 3.2.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31808 | MEDIUM5.3 | file-type 16.5.4 fixed in 21.3.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31808 | MEDIUM5.3 | file-type 20.4.1 fixed in 21.3.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32630 | MEDIUM5.3 | file-type 20.4.1 fixed in 21.3.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-21714 | MEDIUM5.3 | node 22.22.0 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-76845 | MEDIUM5.2 | adm-zip 0.5.10 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-58043 | MEDIUM5.04 | node 22.22.0 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-101909 | MEDIUM4.92 | axios 1.16.0 fixed in 0.34.0, 1.20.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48617 | MEDIUM4.92 | node 22.22.0 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42338 | MEDIUM4.88 | ip-address 9.0.5 fixed in 10.1.1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| GHSA-p634-w6r4-rjp2 | MEDIUM4.72 | adm-zip 0.5.10 fixed in 0.6.1 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-40200 | MEDIUM4.68 | musl-utils 1.2.5-r21 fixed in 1.2.5-r23 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22184 | MEDIUM4.68 | zlib 1.3.1-r2 fixed in 1.3.2-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-101901 | MEDIUM4.5 | axios 1.16.0 fixed in 1.20.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-101906 | MEDIUM4.5 | axios 1.16.0 fixed in 1.20.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-67320 | MEDIUM4.5 | axios 1.16.0 fixed in 0.33.0, 1.18.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-67312 | MEDIUM4.5 | axios 1.16.0 fixed in 0.33.0, 1.18.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-67313 | MEDIUM4.5 | axios 1.16.0 fixed in 0.33.0, 1.18.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-67315 | MEDIUM4.5 | axios 1.16.0 fixed in 1.18.0, 0.33.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-67317 | MEDIUM4.5 | axios 1.16.0 fixed in 1.18.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-67321 | MEDIUM4.5 | axios 1.16.0 fixed in 0.33.0, 1.18.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-24001 | MEDIUM4.5 | diff 4.0.2 fixed in 8.0.3, 5.2.2, 4.0.4, 3.5.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-24001 | MEDIUM4.5 | diff 5.2.0 fixed in 8.0.3, 5.2.2, 4.0.4, 3.5.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-111756 | MEDIUM4.5 | follow-redirects 1.16.0 fixed in 1.16.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-12143 | MEDIUM4.5 | form-data 4.0.5 fixed in 2.5.6, 3.0.5, 4.0.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-64756 | MEDIUM4.5 | glob 10.4.5 fixed in 11.1.0, 10.5.0 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-59869 | MEDIUM4.5 | js-yaml 4.1.1 fixed in 3.15.0, 4.3.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-84375 | MEDIUM4.5 | js-yaml 4.1.1 fixed in 4.3.2, 3.15.2 | 0.5% Theoretical Threat | Directly Exposed |
| GHSA-5p4m-2wfm-xmqj | MEDIUM4.5 | js-yaml 4.1.1 fixed in 4.3.1, 3.15.1 | — | Directly Exposed |
| CVE-2026-2391 | MEDIUM4.5 | qs 6.13.0 fixed in 6.14.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-2391 | MEDIUM4.5 | qs 6.14.0 fixed in 6.14.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-101905 | MEDIUM4.44 | axios 1.16.0 fixed in 1.20.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-67316 | MEDIUM4.44 | axios 1.16.0 fixed in 1.18.0, 0.33.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56850 | MEDIUM4.4 | node 22.22.0 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-9358 | MEDIUM4.3 | postcss-selector-parser 7.1.0 fixed in 6.1.3, 7.1.3 | 0.3% Theoretical Threat | Directly Exposed |
| GHSA-c6fg-446q-cg94 | MEDIUM4.24 | adm-zip 0.5.10 fixed in 0.6.1 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-13149 | MEDIUM4.24 | brace-expansion 2.0.2 fixed in 5.0.7, 1.1.16, 2.1.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102277 | MEDIUM4.24 | brace-expansion 2.0.2 fixed in 5.0.12, 3.0.9, 2.1.7, 1.1.21 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-101911 | MEDIUM4.24 | ip-address 9.0.5 fixed in 10.7.1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-101912 | MEDIUM4.24 | ip-address 9.0.5 fixed in 10.7.1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-101913 | MEDIUM4.24 | ip-address 9.0.5 fixed in 10.5.1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-111997 | MEDIUM4.24 | ip-address 9.0.5 fixed in 10.7.4 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107891 | MEDIUM4 | musl 1.2.5-r23 fixed in 1.2.5-r24 | — | Directly Exposed |
| CVE-2026-107891 | MEDIUM4 | musl-utils 1.2.5-r21 fixed in 1.2.5-r24 | — | Directly Exposed |
| CVE-2026-101899 | LOW3.9 | axios 1.16.0 fixed in 1.20.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-101900 | LOW3.9 | axios 1.16.0 fixed in 1.20.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-101904 | LOW3.9 | axios 1.16.0 fixed in 1.20.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-101908 | LOW3.9 | axios 1.16.0 fixed in 1.20.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-67314 | LOW3.9 | axios 1.16.0 fixed in 1.18.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-29786 | LOW3.78 | tar 6.2.1 fixed in 7.5.10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-29786 | LOW3.78 | tar 7.4.3 fixed in 7.5.10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23745 | LOW3.66 | tar 6.2.1 fixed in 7.5.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23745 | LOW3.66 | tar 7.4.3 fixed in 7.5.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-101902 | LOW3.54 | axios 1.16.0 fixed in 0.34.0, 1.20.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-111755 | LOW3.54 | follow-redirects 1.16.0 fixed in 1.16.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | LOW3.3 | zlib 1.3.1-r2 fixed in 1.3.2-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31802 | LOW3.3 | tar 6.2.1 fixed in 7.5.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53655 | LOW3.3 | tar 6.2.1 fixed in 7.5.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31802 | LOW3.3 | tar 7.4.3 fixed in 7.5.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53655 | LOW3.3 | tar 7.4.3 fixed in 7.5.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-21715 | LOW3.3 | node 22.22.0 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-21716 | LOW3.3 | node 22.22.0 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-67318 | LOW3.18 | axios 1.16.0 fixed in 1.18.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-53550 | LOW3.18 | js-yaml 4.1.1 fixed in 4.2.0, 3.15.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-13465 | LOW3.18 | lodash 4.17.21 fixed in 4.17.23 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-2950 | LOW3.18 | lodash 4.17.21 fixed in 4.18.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-82417 | LOW3.18 | qs 6.13.0 fixed in 6.16.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8723 | LOW3.18 | qs 6.13.0 fixed in 6.15.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-82417 | LOW3.18 | qs 6.14.0 fixed in 6.16.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8723 | LOW3.18 | qs 6.14.0 fixed in 6.15.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-85091 | LOW3 | zlib 1.3.1-r2 fixed in 1.3.2-r1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-77063 | LOW2.96 | multer 2.0.2 fixed in 2.3.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-24842 | LOW2.95 | tar 6.2.1 fixed in 7.5.7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-24842 | LOW2.95 | tar 7.4.3 fixed in 7.5.7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-101898 | LOW2.88 | axios 1.16.0 fixed in 1.20.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-93748 | LOW2.7 | http-cache-semantics 4.2.0 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9496 | LOW2.7 | pacote 19.0.1 fixed in 21.5.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9496 | LOW2.7 | pacote 20.0.0 fixed in 21.5.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4926 | LOW2.7 | path-to-regexp 8.2.0 fixed in 8.4.0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-33671 | LOW2.7 | picomatch 4.0.2 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48815 | LOW2.7 | sigstore 3.1.0 fixed in 4.1.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59873 | LOW2.7 | tar 6.2.1 fixed in 7.5.19 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-59874 | LOW2.7 | tar 6.2.1 fixed in 7.5.18 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-73566 | LOW2.7 | tar 6.2.1 fixed in 7.5.21 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-59871 | LOW2.7 | tar 6.2.1 fixed in 7.5.18 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-59873 | LOW2.7 | tar 7.4.3 fixed in 7.5.19 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-59874 | LOW2.7 | tar 7.4.3 fixed in 7.5.18 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-73566 | LOW2.7 | tar 7.4.3 fixed in 7.5.21 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-59871 | LOW2.7 | tar 7.4.3 fixed in 7.5.18 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-41907 | LOW2.7 | uuid 8.3.2 fixed in 11.1.1, 12.0.1, 13.0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-45736 | LOW2.7 | ws 8.17.1 fixed in 8.20.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-26960 | LOW2.56 | tar 6.2.1 fixed in 7.5.8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-26960 | LOW2.56 | tar 7.4.3 fixed in 7.5.8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-67319 | LOW2.22 | axios 1.16.0 fixed in 0.33.0, 1.18.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15284 | LOW2.22 | qs 6.13.0 fixed in 6.14.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15284 | LOW2.22 | qs 6.14.0 fixed in 6.14.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4923 | LOW2.12 | path-to-regexp 8.2.0 fixed in 8.4.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-23950 | LOW2.12 | tar 6.2.1 fixed in 7.5.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-23950 | LOW2.12 | tar 7.4.3 fixed in 7.5.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-33672 | LOW1.91 | picomatch 4.0.2 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59875 | LOW1.91 | tar 6.2.1 fixed in 7.5.17 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59875 | LOW1.91 | tar 7.4.3 fixed in 7.5.17 | 0.4% Theoretical Threat | Post-Exploit |
Want to check another image? Run a full scan with the Docker Security Scanner.