Last scanned:
··This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker sending crafted compressed or header data to the Kibana port could crash the service, corrupt memory, or potentially run code in the container, disrupting the dashboards and data access Kibana provides. CVE-2026-111497 is the main concern because it is listed as actively exploited, although it is not confirmed that Kibana's request path uses this copy of the library. CVE-2026-35213 is reachable in normal operation and needs no special configuration, so it can cause service slowdowns. The data does not show a compensating control that fully removes these risks, so the practical path is to rebuild the image with fixed libbrotli and Node package versions before production use.
Hardening plan for this image · 6 steps. The first targets an actively exploited CVE.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-111497 | HIGH8 | libbrotli 1.0.9-9.el9_7 No fix yet | 82.6% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2026-35213 | HIGH7.5 | @hapi/content 6.0.0 fixed in 6.0.1 | 0.3% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-12143 | HIGH7.5 | form-data 4.0.4 fixed in 2.5.6, 3.0.5, 4.0.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92599 | HIGH7.5 | joi 18.0.2 fixed in 17.13.7, 18.2.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46625 | HIGH7.5 | js-cookie 2.2.1 fixed in 3.0.7 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-59869 | HIGH7.5 | js-yaml 4.1.1 fixed in 3.15.0, 4.3.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-84375 | HIGH7.5 | js-yaml 4.1.1 fixed in 4.3.2, 3.15.2 | 0.5% Theoretical Threat | Directly Exposed |
| GHSA-5p4m-2wfm-xmqj | HIGH7.5 | js-yaml 4.1.1 fixed in 4.3.1, 3.15.1 | — | Directly Exposed |
| CVE-2026-48801 | HIGH7.5 | linkify-it 5.0.0 fixed in 5.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59887 | HIGH7.5 | linkify-it 5.0.0 fixed in 5.0.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-111758 | HIGH7.5 | markdown-it 14.1.0 fixed in 14.3.3, 15.0.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-111759 | HIGH7.5 | markdown-it 14.1.0 fixed in 15.0.2, 14.3.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-2327 | HIGH7.5 | markdown-it 14.1.0 fixed in 14.1.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-26996 | HIGH7.5 | 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.6% Theoretical Threat | Directly Exposed |
| CVE-2026-27903 | HIGH7.5 | 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.6% Theoretical Threat | Directly Exposed |
| CVE-2026-27904 | HIGH7.5 | 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 |
| GHSA-2x7j-588g-ccc2 | HIGH7.5 | nodemailer 7.0.11 fixed in 9.1.0 | — | Directly Exposed |
| GHSA-v53p-9fqp-m79j | HIGH7.5 | nodemailer 7.0.11 fixed in 10.0.6 | — | Directly Exposed |
| CVE-2026-4926 | HIGH7.5 | path-to-regexp 8.2.0 fixed in 8.4.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33671 | HIGH7.5 | picomatch 2.3.1 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2391 | HIGH7.5 | qs 6.13.0 fixed in 6.14.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-2391 | HIGH7.5 | qs 6.14.0 fixed in 6.14.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-41907 | HIGH7.5 | uuid 10.0.0 fixed in 11.1.1, 12.0.1, 13.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41907 | HIGH7.5 | uuid 11.1.0 fixed in 11.1.1, 12.0.1, 13.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41907 | HIGH7.5 | uuid 8.3.2 fixed in 11.1.1, 12.0.1, 13.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41907 | HIGH7.5 | uuid 9.0.1 fixed in 11.1.1, 12.0.1, 13.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48779 | HIGH7.5 | ws 8.18.3 fixed in 5.2.5, 6.2.4, 7.5.11, 8.21.0 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45736 | HIGH7.5 | ws 8.18.3 fixed in 8.20.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-54404 | HIGH7.5 | zod 3.25.76 fixed in 4.6.6 | — | Directly Exposed |
| CVE-2023-54404 | HIGH7.5 | zod 4.1.12 fixed in 4.6.6 | — | Directly Exposed |
| CVE-2026-84782 | HIGH7.4 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.8-2.el9_8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-90711 | HIGH7.28 | proxy-addr 2.0.7 fixed in 2.0.8 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54369 | HIGH7.1 | libacl 2.3.1-4.el9 fixed in 2.4.0-1.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-82659 | HIGH7.1 | nodemailer 7.0.11 fixed in 9.0.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | HIGH7 | libcap 2.48-10.el9 fixed in 2.48-10.el9_8.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM6.9 | cyrus-sasl-lib 2.1.27-22.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM6.9 | glibc 2.34-231.el9_7.10 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM6.9 | glibc 2.34-231.el9_7.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM6.9 | glibc-common 2.34-231.el9_7.10 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM6.9 | glibc-common 2.34-231.el9_7.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM6.9 | glibc-minimal-langpack 2.34-231.el9_7.10 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM6.9 | glibc-minimal-langpack 2.34-231.el9_7.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.9 | krb5-libs 1.21.1-8.el9_6 fixed in 1.21.1-10.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.9 | krb5-libs 1.21.1-8.el9_6 fixed in 1.21.1-10.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM6.9 | libgcc 11.5.0-11.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.9 | libgcc 11.5.0-11.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41989 | MEDIUM6.9 | libgcrypt 1.10.0-11.el9 fixed in 1.10.0-13.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48864 | MEDIUM6.9 | libsolv 0.7.24-3.el9 fixed in 0.7.24-6.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM6.9 | libstdc++ 11.5.0-11.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.9 | libstdc++ 11.5.0-11.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM6.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.8-1.el9_8 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-3.el9_8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34183 | MEDIUM6.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45445 | MEDIUM6.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63072 | MEDIUM6.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.8-1.el9_8 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM6.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.8-1.el9_8 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-2100 | MEDIUM6.9 | p11-kit 0.25.3-3.el9_5 fixed in 0.26.2-1.el9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-2100 | MEDIUM6.9 | p11-kit-trust 0.25.3-3.el9_5 fixed in 0.26.2-1.el9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.9 | systemd-libs 252-55.el9_7.7 fixed in 252-67.el9_8.2 | 0.1% Theoretical Threat | Directly Exposed |
| GHSA-r4q5-vmmm-2653 | MEDIUM6.9 | follow-redirects 1.15.6 fixed in 1.16.0 | — | Directly Exposed |
| CVE-2026-111767 | MEDIUM6.88 | @modelcontextprotocol/sdk 1.25.2 fixed in 1.32.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-114406 | MEDIUM6.8 | ca-certificates 2024.2.69_v8.0.303-91.4.el9_4 fixed in 2026.2.92_v9.0.319-90.3.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM6.8 | openldap 2.6.8-4.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM6.7 | systemd-libs 252-55.el9_7.7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM6.5 | glibc 2.34-231.el9_7.10 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM6.5 | glibc 2.34-231.el9_7.10 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM6.5 | glibc-common 2.34-231.el9_7.10 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM6.5 | glibc-common 2.34-231.el9_7.10 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM6.5 | glibc-minimal-langpack 2.34-231.el9_7.10 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM6.5 | glibc-minimal-langpack 2.34-231.el9_7.10 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM6.5 | krb5-libs 1.21.1-8.el9_6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9149 | MEDIUM6.5 | libsolv 0.7.24-3.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9150 | MEDIUM6.5 | libsolv 0.7.24-3.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2673 | MEDIUM6.5 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-3.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM6.5 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | MEDIUM6.5 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-8769 | MEDIUM6.5 | @ai-sdk/provider-utils 3.0.17 fixed in 3.0.28, 4.0.33, 5.0.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-48022 | MEDIUM6.5 | @hapi/wreck 18.1.0 fixed in 18.1.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-82662 | MEDIUM6.5 | nodemailer 7.0.11 fixed in 8.0.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-110871 | MEDIUM6.5 | nodemailer 7.0.11 fixed in 10.0.10 | 0.4% Theoretical Threat | Directly Exposed |
| GHSA-85x2-q946-cp5h | MEDIUM6.5 | nodemailer 7.0.11 fixed in 10.1.4 | — | Directly Exposed |
| GHSA-8c8m-p3m8-cjg8 | MEDIUM6.5 | nodemailer 7.0.11 fixed in 10.1.4 | — | Directly Exposed |
| GHSA-cc9r-2j5m-2m83 | MEDIUM6.5 | nodemailer 7.0.11 fixed in 9.1.0 | — | Directly Exposed |
| GHSA-m943-m63m-w62w | MEDIUM6.5 | nodemailer 7.0.11 fixed in 10.1.4 | — | Directly Exposed |
| GHSA-wmmp-3585-3rmp | MEDIUM6.5 | nodemailer 7.0.11 fixed in 9.1.0 | — | Directly Exposed |
| CVE-2026-54370 | MEDIUM6.3 | libacl 2.3.1-4.el9 fixed in 2.4.0-1.el9_8 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM6.3 | libattr 2.5.1-3.el9 fixed in 2.6.0-1.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-12345 | MEDIUM6.3 | python3-libs 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44979 | MEDIUM6.3 | @hapi/wreck 18.1.0 fixed in 18.1.1 | 0.4% Theoretical Threat | Directly Exposed |
| GHSA-253c-mchw-3w2r | MEDIUM6.3 | markdown-it 14.1.0 fixed in 15.0.1, 14.3.1 | — | Directly Exposed |
| CVE-2026-92822 | MEDIUM6.2 | libmodulemd 2.13.0-2.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92823 | MEDIUM6.2 | libmodulemd 2.13.0-2.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92824 | MEDIUM6.2 | libmodulemd 2.13.0-2.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM6.2 | p11-kit 0.25.3-3.el9_5 fixed in 0.26.4-1.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM6.2 | p11-kit-trust 0.25.3-3.el9_5 fixed in 0.26.4-1.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44974 | MEDIUM6.16 | @hapi/content 6.0.0 fixed in 6.0.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6019 | MEDIUM6.1 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| GHSA-mrv2-3pqr-j5jr | MEDIUM6.08 | dompurify 3.3.0 fixed in 3.4.17 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-29087 | MEDIUM6 | @hono/node-server 1.19.9 fixed in 1.19.10 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-104850 | MEDIUM6 | @modelcontextprotocol/sdk 1.25.2 fixed in 1.31.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-111768 | MEDIUM6 | @modelcontextprotocol/sdk 1.25.2 fixed in 1.32.0 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-44902 | MEDIUM6 | @opentelemetry/exporter-prometheus 0.208.0 fixed in 0.217.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-44902 | MEDIUM6 | @opentelemetry/sdk-node 0.208.0 fixed in 0.217.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-39244 | MEDIUM6 | adm-zip 0.5.16 fixed in 0.6.0 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-77301 | MEDIUM6 | adm-zip 0.5.16 fixed in 0.6.1 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| GHSA-8238-w5pm-2374 | MEDIUM6 | adm-zip 0.5.16 fixed in 0.6.1 | — | Directly ExposedContext importance: MEDIUM |
| GHSA-rcw4-f5rp-g42v | MEDIUM6 | adm-zip 0.5.16 fixed in 0.6.1 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2025-69873 | MEDIUM6 | ajv 8.17.1 fixed in 8.18.0, 6.14.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-111181 | MEDIUM6 | body-parser 2.2.1 fixed in 2.4.0, 1.20.9 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-45822 | MEDIUM6 | decode-uri-component 0.2.2 fixed in 0.5.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-5713 | MEDIUM6 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | glibc 2.34-231.el9_7.10 fixed in 2.34-274.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | glibc 2.34-231.el9_7.10 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | glibc 2.34-231.el9_7.10 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | glibc 2.34-231.el9_7.10 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | glibc-common 2.34-231.el9_7.10 fixed in 2.34-274.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | glibc-common 2.34-231.el9_7.10 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | glibc-common 2.34-231.el9_7.10 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | glibc-common 2.34-231.el9_7.10 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | glibc-minimal-langpack 2.34-231.el9_7.10 fixed in 2.34-274.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | glibc-minimal-langpack 2.34-231.el9_7.10 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | glibc-minimal-langpack 2.34-231.el9_7.10 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | glibc-minimal-langpack 2.34-231.el9_7.10 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | openssl-fips-provider 3.0.7-8.el9 fixed in 3.0.7-11.el9_8 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | openssl-fips-provider-so 3.0.7-8.el9 fixed in 3.0.7-11.el9_8 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-2.el9_8 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.9 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-72897 | MEDIUM5.9 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.9 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.9 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-17495 | MEDIUM5.9 | moment 2.30.1 fixed in 2.31.0 | 0.5% Theoretical Threat | Directly Exposed |
| GHSA-6vj9-mwq6-2f5v | MEDIUM5.9 | nodemailer 7.0.11 fixed in 10.0.2 | — | Directly Exposed |
| GHSA-8m3c-c648-2xjj | MEDIUM5.9 | nodemailer 7.0.11 fixed in 9.1.1 | — | Directly Exposed |
| GHSA-8vvx-rff5-p5rq | MEDIUM5.9 | nodemailer 7.0.11 fixed in 10.0.2 | — | Directly Exposed |
| CVE-2026-4923 | MEDIUM5.9 | path-to-regexp 8.2.0 fixed in 8.4.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27699 | MEDIUM5.88 | basic-ftp 5.0.3 fixed in 5.2.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-40190 | MEDIUM5.88 | langsmith 0.3.72 fixed in 0.5.18 | 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-41242 | MEDIUM5.88 | protobufjs 7.5.4 fixed in 8.0.1, 7.5.5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-1525 | MEDIUM5.88 | undici 6.23.0 fixed in 6.24.0, 7.24.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1525 | MEDIUM5.88 | undici 7.18.2 fixed in 6.24.0, 7.24.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-49919 | MEDIUM5.8 | freetype 2.10.4-10.el9_5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-104872 | MEDIUM5.8 | @opentelemetry/instrumentation-cassandra-driver 0.54.0 fixed in 0.66.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-104872 | MEDIUM5.8 | @opentelemetry/instrumentation-knex 0.53.1 fixed in 0.65.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-104872 | MEDIUM5.8 | @opentelemetry/instrumentation-mongoose 0.55.0 fixed in 0.67.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-104872 | MEDIUM5.8 | @opentelemetry/instrumentation-mysql 0.54.0 fixed in 0.67.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-104872 | MEDIUM5.8 | @opentelemetry/instrumentation-mysql2 0.55.0 fixed in 0.67.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-104872 | MEDIUM5.8 | @opentelemetry/instrumentation-oracledb 0.34.0 fixed in 0.46.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-104872 | MEDIUM5.8 | @opentelemetry/instrumentation-pg 0.61.1 fixed in 0.73.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-104872 | MEDIUM5.8 | @opentelemetry/instrumentation-tedious 0.27.0 fixed in 0.40.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25536 | MEDIUM5.68 | @modelcontextprotocol/sdk 1.25.2 fixed in 1.26.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102282 | MEDIUM5.68 | adm-zip 0.5.16 fixed in 0.6.1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-68154 | MEDIUM5.59 | systeminformation 5.23.8 fixed in 5.27.14 | 13.0% High Exploitation Risk | Directly Exposed |
| CVE-2026-25896 | MEDIUM5.58 | fast-xml-parser 4.4.1 fixed in 5.3.5, 4.5.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM5.52 | python-unversioned-command 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-4224 | MEDIUM5.52 | python-unversioned-command 3.9.25-3.el9_7 No fix yet | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-7210 | MEDIUM5.52 | python-unversioned-command 3.9.25-3.el9_7 No fix yet | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-3644 | MEDIUM5.52 | python3 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-4224 | MEDIUM5.52 | python3 3.9.25-3.el9_7 No fix yet | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-7210 | MEDIUM5.52 | python3 3.9.25-3.el9_7 No fix yet | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-3644 | MEDIUM5.52 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-4224 | MEDIUM5.52 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-7210 | MEDIUM5.52 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-41238 | MEDIUM5.52 | dompurify 3.3.0 fixed in 3.4.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-95512 | MEDIUM5.5 | freetype 2.10.4-10.el9_5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | glibc 2.34-231.el9_7.10 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | glibc-common 2.34-231.el9_7.10 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | glibc-minimal-langpack 2.34-231.el9_7.10 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-82327 | MEDIUM5.5 | libsolv 0.7.24-3.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM5.5 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM5.5 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42308 | MEDIUM5.5 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | systemd-libs 252-55.el9_7.7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33896 | MEDIUM5.46 | node-forge 1.3.3 fixed in 1.4.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13697 | MEDIUM5.46 | undici 7.18.2 fixed in 7.29.0, 8.9.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-111771 | MEDIUM5.44 | @modelcontextprotocol/sdk 1.25.2 fixed in 1.32.0 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-41239 | MEDIUM5.44 | dompurify 3.3.0 fixed in 3.4.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| GHSA-268h-hp4c-crq3 | MEDIUM5.4 | nodemailer 7.0.11 fixed in 8.0.9 | — | Directly Exposed |
| GHSA-wqvq-jvpq-h66f | MEDIUM5.4 | nodemailer 7.0.11 fixed in 8.0.9 | — | Directly Exposed |
| CVE-2026-58016 | MEDIUM5.34 | glib2 2.68.4-18.el9_7.1 fixed in 2.68.4-19.el9_8.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | MEDIUM5.34 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42010 | MEDIUM5.34 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-23865 | MEDIUM5.3 | freetype 2.10.4-10.el9_5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | glibc 2.34-231.el9_7.10 fixed in 2.34-270.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | glibc 2.34-231.el9_7.10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | glibc-common 2.34-231.el9_7.10 fixed in 2.34-270.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | glibc-common 2.34-231.el9_7.10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | glibc-minimal-langpack 2.34-231.el9_7.10 fixed in 2.34-270.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | glibc-minimal-langpack 2.34-231.el9_7.10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22693 | MEDIUM5.3 | harfbuzz 2.7.4-10.el9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42772 | MEDIUM5.3 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54873 | MEDIUM5.3 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | MEDIUM5.3 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM5.3 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-84784 | MEDIUM5.3 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM5.3 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-19672 | MEDIUM5.3 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM5.3 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM5.3 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM5.3 | xz-libs 5.2.5-8.el9_0 fixed in 5.2.5-8.el9_8.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48049 | MEDIUM5.3 | @hapi/inert 7.1.0 fixed in 7.1.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-54285 | MEDIUM5.3 | @opentelemetry/core 1.30.1 fixed in 2.8.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54285 | MEDIUM5.3 | @opentelemetry/core 2.2.0 fixed in 2.8.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54285 | MEDIUM5.3 | @opentelemetry/core 2.3.0 fixed in 2.8.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44288 | MEDIUM5.3 | @protobufjs/utf8 1.1.0 fixed in 1.1.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-2739 | MEDIUM5.3 | bn.js 4.11.9 fixed in 4.12.3, 5.2.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48038 | MEDIUM5.3 | joi 18.0.2 fixed in 18.2.1, 17.13.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53550 | MEDIUM5.3 | js-yaml 4.1.1 fixed in 4.2.0, 3.15.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48988 | MEDIUM5.3 | markdown-it 14.1.0 fixed in 14.2.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33672 | MEDIUM5.3 | picomatch 2.3.1 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-82417 | MEDIUM5.3 | qs 6.13.0 fixed in 6.16.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8723 | MEDIUM5.3 | qs 6.13.0 fixed in 6.15.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-82417 | MEDIUM5.3 | qs 6.14.0 fixed in 6.16.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8723 | MEDIUM5.3 | qs 6.14.0 fixed in 6.15.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31988 | MEDIUM5.3 | yauzl 3.2.0 fixed in 3.2.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44293 | MEDIUM5.28 | protobufjs 7.5.4 fixed in 7.5.6, 8.0.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-26318 | MEDIUM5.28 | systeminformation 5.23.8 fixed in 5.31.0 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-50289 | MEDIUM5.28 | systeminformation 5.23.8 fixed in 5.31.7 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-111769 | MEDIUM5.2 | @modelcontextprotocol/sdk 1.25.2 fixed in 1.32.0 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-76845 | MEDIUM5.2 | adm-zip 0.5.16 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-63387 | MEDIUM5.16 | libevent 2.1.12-8.el9_4 fixed in 2.1.13-1.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-69192 | MEDIUM5.16 | ip-address 9.0.5 fixed in 10.3.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-74860 | MEDIUM5.1 | libxml2 2.9.13-14.el9_7 fixed in 2.9.13-14.el9_8.5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63388 | MEDIUM5.04 | libevent 2.1.12-8.el9_4 fixed in 2.1.13-1.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM5 | bzip2-libs 1.0.8-10.el9_5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | glibc 2.34-231.el9_7.10 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | glibc 2.34-231.el9_7.10 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | glibc-common 2.34-231.el9_7.10 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | glibc-common 2.34-231.el9_7.10 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | glibc-minimal-langpack 2.34-231.el9_7.10 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | glibc-minimal-langpack 2.34-231.el9_7.10 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM5 | krb5-libs 1.21.1-8.el9_6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-77214 | MEDIUM4.92 | expat 2.5.0-5.el9_7.1 fixed in 2.5.0-6.el9_8.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86145 | MEDIUM4.92 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86145 | MEDIUM4.92 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| GHSA-6v7q-wjvx-w8wg | MEDIUM4.92 | basic-ftp 5.0.3 fixed in 5.2.2 | — | Directly Exposed |
| CVE-2026-84933 | MEDIUM4.92 | undici 7.18.2 fixed in 7.29.1, 8.10.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | glibc 2.34-231.el9_7.10 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | glibc-common 2.34-231.el9_7.10 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | glibc-minimal-langpack 2.34-231.el9_7.10 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.9 | krb5-libs 1.21.1-8.el9_6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| GHSA-vvjj-xcjg-gr5g | MEDIUM4.9 | nodemailer 7.0.11 fixed in 8.0.5 | — | Directly Exposed |
| CVE-2026-0540 | MEDIUM4.88 | dompurify 3.3.0 fixed in 3.3.2, 2.5.9 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-41240 | MEDIUM4.88 | dompurify 3.3.0 fixed in 3.4.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-49458 | MEDIUM4.88 | dompurify 3.3.0 fixed in 3.4.6 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-49459 | MEDIUM4.88 | dompurify 3.3.0 fixed in 3.4.6 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-49978 | MEDIUM4.88 | dompurify 3.3.0 fixed in 3.4.7 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-65902 | MEDIUM4.88 | dompurify 3.3.0 fixed in 3.4.7 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-65903 | MEDIUM4.88 | dompurify 3.3.0 fixed in 3.4.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-65912 | MEDIUM4.88 | dompurify 3.3.0 fixed in 3.3.2 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-65913 | MEDIUM4.88 | dompurify 3.3.0 fixed in 3.3.2 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-65914 | MEDIUM4.88 | dompurify 3.3.0 fixed in 3.3.2 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-65899 | MEDIUM4.88 | dompurify 3.3.0 fixed in 3.4.9 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-65900 | MEDIUM4.88 | dompurify 3.3.0 fixed in 3.4.8 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-65901 | MEDIUM4.88 | dompurify 3.3.0 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-66010 | MEDIUM4.88 | dompurify 3.3.0 fixed in 3.4.12 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-25646 | MEDIUM4.86 | libpng 2:1.6.37-12.el9_7.1 fixed in 2:1.6.37-12.el9_7.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | MEDIUM4.86 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-19445 | MEDIUM4.86 | python3-libs 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM4.86 | python3-libs 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-19693 | MEDIUM4.86 | extract-zip 2.0.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56876 | MEDIUM4.86 | extract-zip 2.0.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-102992 | MEDIUM4.86 | piscina 3.2.0 fixed in 5.3.2, 4.9.4, 6.0.0-rc.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-55388 | MEDIUM4.86 | piscina 3.2.0 fixed in 5.2.0, 4.9.3, 6.0.0-rc.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44291 | MEDIUM4.86 | protobufjs 7.5.4 fixed in 7.5.6, 8.0.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libblkid 2.37.4-21.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libmount 2.37.4-21.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libsmartcols 2.37.4-21.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libuuid 2.37.4-21.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.8 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.8 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| GHSA-frvp-7c67-39w9 | MEDIUM4.72 | @hono/node-server 1.19.9 fixed in 2.0.5, 1.19.15 | — | Directly ExposedContext importance: MEDIUM |
| GHSA-p634-w6r4-rjp2 | MEDIUM4.72 | adm-zip 0.5.16 fixed in 0.6.1 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-12590 | MEDIUM4.72 | body-parser 2.2.1 fixed in 1.20.6, 2.3.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54875 | MEDIUM4.7 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86140 | MEDIUM4.68 | libxml2 2.9.13-14.el9_7 fixed in 2.9.13-14.el9_8.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89161 | MEDIUM4.68 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-89161 | MEDIUM4.68 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11822 | MEDIUM4.68 | sqlite-libs 3.34.1-9.el9_7 fixed in 3.34.1-11.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11824 | MEDIUM4.68 | sqlite-libs 3.34.1-9.el9_7 fixed in 3.34.1-11.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-26280 | MEDIUM4.68 | systeminformation 5.23.8 fixed in 5.30.8 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-44724 | MEDIUM4.68 | systeminformation 5.23.8 fixed in 5.31.6 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63382 | MEDIUM4.62 | libevent 2.1.12-8.el9_4 fixed in 2.1.13-1.el9_8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-63385 | MEDIUM4.62 | libevent 2.1.12-8.el9_4 fixed in 2.1.13-1.el9_8 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-53382 | MEDIUM4.59 | prismjs 1.27.0 fixed in 1.30.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-103111 | MEDIUM4.56 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-103111 | MEDIUM4.56 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8927 | MEDIUM4.5 | curl-minimal 7.76.1-35.el9_7.3 fixed in 7.76.1-40.el9_8.7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45186 | MEDIUM4.5 | expat 2.5.0-5.el9_7.1 fixed in 2.5.0-6.el9_8.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-66046 | MEDIUM4.5 | expat 2.5.0-5.el9_7.1 fixed in 2.5.0-6.el9_8.5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-76641 | MEDIUM4.5 | expat 2.5.0-5.el9_7.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-93990 | MEDIUM4.5 | expat 2.5.0-5.el9_7.1 fixed in 2.5.0-6.el9_8.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33846 | MEDIUM4.5 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | MEDIUM4.5 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-4424 | MEDIUM4.5 | libarchive 3.5.3-6.el9_6 fixed in 3.5.3-9.el9_7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-8927 | MEDIUM4.5 | libcurl-minimal 7.76.1-35.el9_7.3 fixed in 7.76.1-40.el9_8.7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63383 | MEDIUM4.5 | libevent 2.1.12-8.el9_4 fixed in 2.1.13-1.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63384 | MEDIUM4.5 | libevent 2.1.12-8.el9_4 fixed in 2.1.13-1.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.8-1.el9_8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM4.5 | python3-libs 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-57585 | MEDIUM4.5 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48068 | MEDIUM4.5 | @grpc/grpc-js 1.14.3 fixed in 1.9.16, 1.10.12, 1.11.4, 1.12.7, 1.13.5, 1.14.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-48069 | MEDIUM4.5 | @grpc/grpc-js 1.14.3 fixed in 1.9.16, 1.10.12, 1.11.4, 1.12.7, 1.13.5, 1.14.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-59892 | MEDIUM4.5 | @opentelemetry/propagator-jaeger 2.2.0 fixed in 2.9.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-102990 | MEDIUM4.5 | basic-ftp 5.0.3 fixed in 6.2.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41324 | MEDIUM4.5 | basic-ftp 5.0.3 fixed in 5.3.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44240 | MEDIUM4.5 | basic-ftp 5.0.3 fixed in 5.3.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-102276 | MEDIUM4.5 | brace-expansion 1.1.12 fixed in 5.0.10, 3.0.7, 2.1.5, 1.1.19 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-102278 | MEDIUM4.5 | brace-expansion 1.1.12 fixed in 5.0.11, 3.0.8, 2.1.6, 1.1.20 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-14257 | MEDIUM4.5 | brace-expansion 1.1.12 fixed in 5.0.8, 3.0.3, 2.1.3, 1.1.17 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-69152 | MEDIUM4.5 | brace-expansion 1.1.12 fixed in 1.1.18, 2.1.4, 3.0.6, 5.0.9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33750 | MEDIUM4.5 | 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-13676 | MEDIUM4.5 | fast-uri 3.0.3 fixed in 4.0.1, 3.1.3, 2.4.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-16221 | MEDIUM4.5 | fast-uri 3.0.3 fixed in 2.4.3, 3.1.4, 4.1.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-18446 | MEDIUM4.5 | fast-uri 3.0.3 fixed in 2.4.4, 3.1.5, 4.1.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6321 | MEDIUM4.5 | fast-uri 3.0.3 fixed in 3.1.1, 2.4.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6322 | MEDIUM4.5 | fast-uri 3.0.3 fixed in 3.1.2, 2.4.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75975 | MEDIUM4.5 | fast-uri 3.0.3 fixed in 2.4.5, 3.1.6, 4.1.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76172 | MEDIUM4.5 | fast-uri 3.0.3 fixed in 2.4.5, 3.1.6, 4.1.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-84292 | MEDIUM4.5 | fast-uri 3.0.3 fixed in 2.4.6, 3.1.7, 4.1.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-26278 | MEDIUM4.5 | fast-xml-parser 4.4.1 fixed in 4.5.4, 5.3.6 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-33036 | MEDIUM4.5 | fast-xml-parser 4.4.1 fixed in 5.5.6, 4.5.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-27942 | MEDIUM4.5 | fast-xml-parser 4.4.1 fixed in 5.3.8, 4.5.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33891 | MEDIUM4.5 | node-forge 1.3.3 fixed in 1.4.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33894 | MEDIUM4.5 | node-forge 1.3.3 fixed in 1.4.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33895 | MEDIUM4.5 | node-forge 1.3.3 fixed in 1.4.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-85393 | MEDIUM4.5 | node-forge 1.3.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44289 | MEDIUM4.5 | protobufjs 7.5.4 fixed in 7.5.6, 8.0.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44290 | MEDIUM4.5 | protobufjs 7.5.4 fixed in 7.5.6, 8.0.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48712 | MEDIUM4.5 | protobufjs 7.5.4 fixed in 7.6.1, 8.4.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45740 | MEDIUM4.5 | protobufjs 7.5.4 fixed in 7.5.8, 8.2.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59877 | MEDIUM4.5 | protobufjs 7.5.4 fixed in 7.6.5, 8.6.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59873 | MEDIUM4.5 | tar 7.5.4 fixed in 7.5.19 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-59874 | MEDIUM4.5 | tar 7.5.4 fixed in 7.5.18 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-73566 | MEDIUM4.5 | tar 7.5.4 fixed in 7.5.21 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59871 | MEDIUM4.5 | tar 7.5.4 fixed in 7.5.18 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-109869 | MEDIUM4.5 | undici 6.23.0 fixed in 6.29.1, 7.30.1, 8.12.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-12151 | MEDIUM4.5 | undici 6.23.0 fixed in 6.27.0, 7.28.0, 8.5.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-1526 | MEDIUM4.5 | undici 6.23.0 fixed in 6.24.0, 7.24.0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-1528 | MEDIUM4.5 | undici 6.23.0 fixed in 6.24.0, 7.24.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-19534 | MEDIUM4.5 | undici 6.23.0 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2229 | MEDIUM4.5 | undici 6.23.0 fixed in 6.24.0, 7.24.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-109924 | MEDIUM4.5 | undici 6.23.0 fixed in 6.29.1, 7.30.1, 8.12.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109869 | MEDIUM4.5 | undici 7.18.2 fixed in 6.29.1, 7.30.1, 8.12.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-12151 | MEDIUM4.5 | undici 7.18.2 fixed in 6.27.0, 7.28.0, 8.5.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-1526 | MEDIUM4.5 | undici 7.18.2 fixed in 6.24.0, 7.24.0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-1528 | MEDIUM4.5 | undici 7.18.2 fixed in 6.24.0, 7.24.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-19534 | MEDIUM4.5 | undici 7.18.2 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2229 | MEDIUM4.5 | undici 7.18.2 fixed in 6.24.0, 7.24.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-109841 | MEDIUM4.5 | undici 7.18.2 fixed in 7.30.1, 8.12.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109924 | MEDIUM4.5 | undici 7.18.2 fixed in 6.29.1, 7.30.1, 8.12.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-14643 | MEDIUM4.5 | undici 7.18.2 fixed in 7.29.0, 8.9.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-85014 | MEDIUM4.5 | undici 7.18.2 fixed in 7.29.1, 8.10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | MEDIUM4.5 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | MEDIUM4.5 | python3-libs 3.9.25-3.el9_7 fixed in 3.9.25-5.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | MEDIUM4.5 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | MEDIUM4.44 | curl-minimal 7.76.1-35.el9_7.3 fixed in 7.76.1-40.el9_8.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | MEDIUM4.44 | libcurl-minimal 7.76.1-35.el9_7.3 fixed in 7.76.1-40.el9_8.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-19553 | MEDIUM4.44 | python3-libs 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-101916 | MEDIUM4.44 | @grpc/grpc-js 1.14.3 fixed in 1.13.6, 1.14.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | MEDIUM4.38 | python3-libs 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | MEDIUM4.33 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65898 | MEDIUM4.32 | dompurify 3.3.0 fixed in 3.4.11 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33532 | MEDIUM4.3 | yaml 1.10.2 fixed in 2.8.3, 1.10.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33532 | MEDIUM4.3 | yaml 2.3.4 fixed in 2.8.3, 1.10.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33532 | MEDIUM4.3 | yaml 2.8.1 fixed in 2.8.3, 1.10.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4786 | MEDIUM4.26 | python3-libs 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45134 | MEDIUM4.26 | langsmith 0.3.72 fixed in 0.6.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-26960 | MEDIUM4.26 | tar 7.5.4 fixed in 7.5.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39406 | MEDIUM4.24 | @hono/node-server 1.19.9 fixed in 1.19.13 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| GHSA-c6fg-446q-cg94 | MEDIUM4.24 | adm-zip 0.5.16 fixed in 0.6.1 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53613 | MEDIUM4.2 | libblkid 2.37.4-21.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libmount 2.37.4-21.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libsmartcols 2.37.4-21.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libuuid 2.37.4-21.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | glibc 2.34-231.el9_7.10 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | glibc 2.34-231.el9_7.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | glibc-common 2.34-231.el9_7.10 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | glibc-common 2.34-231.el9_7.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | glibc-minimal-langpack 2.34-231.el9_7.10 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | glibc-minimal-langpack 2.34-231.el9_7.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5773 | MEDIUM4.14 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-8932 | MEDIUM4.14 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9080 | MEDIUM4.14 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9545 | MEDIUM4.14 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9546 | MEDIUM4.14 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-56132 | MEDIUM4.14 | expat 2.5.0-5.el9_7.1 fixed in 2.5.0-6.el9_8.3 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM4.14 | expat 2.5.0-5.el9_7.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM4.14 | expat 2.5.0-5.el9_7.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM4.14 | expat 2.5.0-5.el9_7.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM4.14 | expat 2.5.0-5.el9_7.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56407 | MEDIUM4.14 | expat 2.5.0-5.el9_7.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76957 | MEDIUM4.14 | expat 2.5.0-5.el9_7.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40468 | MEDIUM4.14 | gawk 5.1.0-6.el9 fixed in 5.1.0-6.el9_8.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40553 | MEDIUM4.14 | gawk 5.1.0-6.el9 fixed in 5.1.0-6.el9_8.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-14087 | MEDIUM4.14 | glib2 2.68.4-18.el9_7.1 fixed in 2.68.4-19.el9_8.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | MEDIUM4.14 | glib2 2.68.4-18.el9_7.1 fixed in 2.68.4-19.el9_8.10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM4.14 | glib2 2.68.4-18.el9_7.1 fixed in 2.68.4-19.el9_8.9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM4.14 | glib2 2.68.4-18.el9_7.1 fixed in 2.68.4-19.el9_8.9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM4.14 | glib2 2.68.4-18.el9_7.1 fixed in 2.68.4-19.el9_8.9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM4.14 | glib2 2.68.4-18.el9_7.1 fixed in 2.68.4-19.el9_8.9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | MEDIUM4.14 | glib2 2.68.4-18.el9_7.1 fixed in 2.68.4-19.el9_8.9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM4.14 | glib2 2.68.4-18.el9_7.1 fixed in 2.68.4-19.el9_8.9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM4.14 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM4.14 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM4.14 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM4.14 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM4.14 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-88647 | MEDIUM4.14 | gnutls 3.8.3-9.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88648 | MEDIUM4.14 | gnutls 3.8.3-9.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-14164 | MEDIUM4.14 | libarchive 3.5.3-6.el9_6 fixed in 3.5.3-11.el9_8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-5121 | MEDIUM4.14 | libarchive 3.5.3-6.el9_6 fixed in 3.5.3-9.el9_7 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5773 | MEDIUM4.14 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-8932 | MEDIUM4.14 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9080 | MEDIUM4.14 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9545 | MEDIUM4.14 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9546 | MEDIUM4.14 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-22695 | MEDIUM4.14 | libpng 2:1.6.37-12.el9_7.1 fixed in 2:1.6.37-12.el9_7.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22801 | MEDIUM4.14 | libpng 2:1.6.37-12.el9_7.1 fixed in 2:1.6.37-12.el9_7.2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33416 | MEDIUM4.14 | libpng 2:1.6.37-12.el9_7.1 fixed in 2:1.6.37-15.el9_8.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33636 | MEDIUM4.14 | libpng 2:1.6.37-12.el9_7.1 fixed in 2:1.6.37-15.el9_8.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | MEDIUM4.14 | libxml2 2.9.13-14.el9_7 fixed in 2.9.13-14.el9_8.4 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6653 | MEDIUM4.14 | libxml2 2.9.13-14.el9_7 fixed in 2.9.13-14.el9_8.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86138 | MEDIUM4.14 | libxml2 2.9.13-14.el9_7 fixed in 2.9.13-14.el9_8.5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86142 | MEDIUM4.14 | libxml2 2.9.13-14.el9_7 fixed in 2.9.13-14.el9_8.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86143 | MEDIUM4.14 | libxml2 2.9.13-14.el9_7 fixed in 2.9.13-14.el9_8.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86144 | MEDIUM4.14 | libxml2 2.9.13-14.el9_7 fixed in 2.9.13-14.el9_8.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89157 | MEDIUM4.14 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-89157 | MEDIUM4.14 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM4.14 | python3-libs 3.9.25-3.el9_7 fixed in 3.9.25-3.el9_7.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM4.14 | python3-libs 3.9.25-3.el9_7 fixed in 3.9.25-3.el9_7.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM4.14 | python3-libs 3.9.25-3.el9_7 fixed in 3.9.25-3.el9_7.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32284 | MEDIUM4.14 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-78367 | MEDIUM4.14 | rpm 4.16.1.3-39.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-84837 | MEDIUM4.14 | rpm 4.16.1.3-39.el9 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-95519 | MEDIUM4.14 | rpm 4.16.1.3-39.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95520 | MEDIUM4.14 | rpm 4.16.1.3-39.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95521 | MEDIUM4.14 | rpm 4.16.1.3-39.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-103242 | MEDIUM4.14 | rpm-libs 4.16.1.3-39.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78367 | MEDIUM4.14 | rpm-libs 4.16.1.3-39.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-84837 | MEDIUM4.14 | rpm-libs 4.16.1.3-39.el9 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-95519 | MEDIUM4.14 | rpm-libs 4.16.1.3-39.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95520 | MEDIUM4.14 | rpm-libs 4.16.1.3-39.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95521 | MEDIUM4.14 | rpm-libs 4.16.1.3-39.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-13034 | MEDIUM4.08 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1965 | MEDIUM4.08 | curl-minimal 7.76.1-35.el9_7.3 fixed in 7.76.1-40.el9_8.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13034 | MEDIUM4.08 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1965 | MEDIUM4.08 | libcurl-minimal 7.76.1-35.el9_7.3 fixed in 7.76.1-40.el9_8.5 | 0.3% Theoretical Threat | Directly Exposed |
| GHSA-55q2-fjhq-7xh7 | MEDIUM4.08 | dompurify 3.3.0 fixed in 3.4.13 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42014 | LOW3.96 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63381 | LOW3.96 | libevent 2.1.12-8.el9_4 fixed in 2.1.13-1.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11856 | LOW3.9 | curl-minimal 7.76.1-35.el9_7.3 fixed in 7.76.1-40.el9_8.8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-19931 | LOW3.9 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-3784 | LOW3.9 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5545 | LOW3.9 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6429 | LOW3.9 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8924 | LOW3.9 | curl-minimal 7.76.1-35.el9_7.3 fixed in 7.76.1-40.el9_8.8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-14512 | LOW3.9 | glib2 2.68.4-18.el9_7.1 fixed in 2.68.4-19.el9_8.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4426 | LOW3.9 | libarchive 3.5.3-6.el9_6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11856 | LOW3.9 | libcurl-minimal 7.76.1-35.el9_7.3 fixed in 7.76.1-40.el9_8.8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-19931 | LOW3.9 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-3784 | LOW3.9 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5545 | LOW3.9 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6429 | LOW3.9 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8924 | LOW3.9 | libcurl-minimal 7.76.1-35.el9_7.3 fixed in 7.76.1-40.el9_8.8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63379 | LOW3.9 | libevent 2.1.12-8.el9_4 fixed in 2.1.13-1.el9_8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-89158 | LOW3.9 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89158 | LOW3.9 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | LOW3.9 | python-unversioned-command 3.9.25-3.el9_7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7774 | LOW3.9 | python-unversioned-command 3.9.25-3.el9_7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.9 | python3 3.9.25-3.el9_7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7774 | LOW3.9 | python3 3.9.25-3.el9_7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-13346 | LOW3.9 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-16728 | LOW3.9 | undici 6.23.0 fixed in 6.28.0, 7.29.0, 8.9.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-16729 | LOW3.9 | undici 6.23.0 fixed in 6.28.0, 7.29.0, 8.9.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-16728 | LOW3.9 | undici 7.18.2 fixed in 6.28.0, 7.29.0, 8.9.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-16729 | LOW3.9 | undici 7.18.2 fixed in 6.28.0, 7.29.0, 8.9.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.9 | glibc 2.34-231.el9_7.10 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.9 | glibc-common 2.34-231.el9_7.10 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.9 | glibc-minimal-langpack 2.34-231.el9_7.10 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13151 | LOW3.9 | libtasn1 4.16.0-9.el9 fixed in 4.16.0-10.el9_8 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-41996 | LOW3.9 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | LOW3.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.8-1.el9_8 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28387 | LOW3.9 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | LOW3.9 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | LOW3.9 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | LOW3.9 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | LOW3.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34181 | LOW3.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42765 | LOW3.9 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | LOW3.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42767 | LOW3.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | LOW3.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | LOW3.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | LOW3.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54874 | LOW3.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.8-1.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63073 | LOW3.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.8-1.el9_8 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63074 | LOW3.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.8-1.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | LOW3.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.8-1.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | LOW3.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | LOW3.9 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | LOW3.9 | zlib 1.2.11-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-12345 | LOW3.78 | python-unversioned-command 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12345 | LOW3.78 | python3 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5958 | LOW3.78 | sed 4.8-9.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-29786 | LOW3.78 | tar 7.5.4 fixed in 7.5.10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1757 | LOW3.72 | libxml2 2.9.13-14.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | glibc 2.34-231.el9_7.10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | glibc-common 2.34-231.el9_7.10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | glibc-minimal-langpack 2.34-231.el9_7.10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.7 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35191 | LOW3.7 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.7 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.8-1.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| GHSA-6475-r3vj-m8vf | LOW3.7 | @smithy/config-resolver 4.3.0 fixed in 4.4.0 | — | Directly Exposed |
| CVE-2026-90771 | LOW3.7 | joi 18.0.2 fixed in 17.13.8, 18.2.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84367 | LOW3.7 | joi 18.0.2 fixed in 17.13.5, 18.2.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84368 | LOW3.7 | joi 18.0.2 fixed in 17.13.6, 18.2.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-111766 | LOW3.7 | markdown-it 14.1.0 fixed in 14.3.3, 15.0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15284 | LOW3.7 | qs 6.13.0 fixed in 6.14.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15284 | LOW3.7 | qs 6.14.0 fixed in 6.14.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56391 | LOW3.66 | coreutils-single 8.32-39.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW3.66 | coreutils-single 8.32-39.el9 fixed in 8.32-41.el9_8.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-64506 | LOW3.66 | libpng 2:1.6.37-12.el9_7.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | LOW3.66 | python-unversioned-command 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.66 | python3 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-110306 | LOW3.66 | fast-uri 3.0.3 fixed in 2.4.8, 3.1.9, 4.2.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41650 | LOW3.66 | fast-xml-parser 4.4.1 fixed in 5.7.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42338 | LOW3.66 | ip-address 9.0.5 fixed in 10.1.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42043 | LOW3.6 | axios 1.12.1 fixed in 1.15.1, 0.31.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-5713 | LOW3.6 | python-unversioned-command 3.9.25-3.el9_7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5713 | LOW3.6 | python3 3.9.25-3.el9_7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-62718 | LOW3.56 | axios 1.12.1 fixed in 1.15.0, 0.31.0 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-102633 | LOW3.54 | expat 2.5.0-5.el9_7.1 fixed in 2.5.0-6.el9_8.7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-113351 | LOW3.54 | expat 2.5.0-5.el9_7.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | LOW3.54 | expat 2.5.0-5.el9_7.1 fixed in 2.5.0-6.el9_8.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | LOW3.54 | expat 2.5.0-5.el9_7.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-67693 | LOW3.54 | gnutls 3.8.3-9.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46675 | LOW3.54 | libpng 2:1.6.37-12.el9_7.1 No fix yet | — | Directly Exposed |
| CVE-2026-0990 | LOW3.54 | libxml2 2.9.13-14.el9_7 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-33349 | LOW3.54 | fast-xml-parser 4.4.1 fixed in 4.5.5, 5.5.7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9679 | LOW3.54 | undici 6.23.0 fixed in 6.27.0, 7.28.0, 8.5.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18149 | LOW3.54 | undici 7.18.2 fixed in 7.29.1, 8.10.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-2581 | LOW3.54 | undici 7.18.2 fixed in 7.24.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-84890 | LOW3.54 | undici 7.18.2 fixed in 7.29.1, 8.10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9678 | LOW3.54 | undici 7.18.2 fixed in 7.28.0, 8.5.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9679 | LOW3.54 | undici 7.18.2 fixed in 6.27.0, 7.28.0, 8.5.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-106446 | LOW3.53 | handlebars 4.7.8 fixed in 4.7.10 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-33937 | LOW3.53 | handlebars 4.7.8 fixed in 4.7.9 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-25528 | LOW3.48 | langsmith 0.3.72 fixed in 0.4.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3783 | LOW3.42 | curl-minimal 7.76.1-35.el9_7.3 fixed in 7.76.1-40.el9_8.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3783 | LOW3.42 | libcurl-minimal 7.76.1-35.el9_7.3 fixed in 7.76.1-40.el9_8.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | LOW3.31 | libgcc 11.5.0-11.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW3.31 | libgcc 11.5.0-11.el9 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | LOW3.31 | libstdc++ 11.5.0-11.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW3.31 | libstdc++ 11.5.0-11.el9 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2020-12413 | LOW3.31 | nspr 4.36.0-4.el9_4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-7531 | LOW3.31 | nspr 4.36.0-4.el9_4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-12413 | LOW3.31 | nss 3.112.0-4.el9_4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-7531 | LOW3.31 | nss 3.112.0-4.el9_4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-12413 | LOW3.31 | nss-softokn 3.112.0-4.el9_4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-7531 | LOW3.31 | nss-softokn 3.112.0-4.el9_4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-12413 | LOW3.31 | nss-softokn-freebl 3.112.0-4.el9_4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-7531 | LOW3.31 | nss-softokn-freebl 3.112.0-4.el9_4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-12413 | LOW3.31 | nss-sysinit 3.112.0-4.el9_4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-7531 | LOW3.31 | nss-sysinit 3.112.0-4.el9_4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-12413 | LOW3.31 | nss-util 3.112.0-4.el9_4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-7531 | LOW3.31 | nss-util 3.112.0-4.el9_4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | LOW3.31 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | LOW3.3 | expat 2.5.0-5.el9_7.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | LOW3.3 | expat 2.5.0-5.el9_7.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | LOW3.3 | expat 2.5.0-5.el9_7.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-60753 | LOW3.3 | libarchive 3.5.3-6.el9_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5745 | LOW3.3 | libarchive 3.5.3-6.el9_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | LOW3.3 | python-unversioned-command 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW3.3 | python-unversioned-command 3.9.25-3.el9_7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42308 | LOW3.3 | python-unversioned-command 3.9.25-3.el9_7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13837 | LOW3.3 | python3 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW3.3 | python3 3.9.25-3.el9_7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42308 | LOW3.3 | python3 3.9.25-3.el9_7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-25645 | LOW3.3 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50812 | LOW3.3 | sqlite-libs 3.34.1-9.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31802 | LOW3.3 | tar 7.5.4 fixed in 7.5.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53655 | LOW3.3 | tar 7.5.4 fixed in 7.5.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41990 | LOW3.3 | libgcrypt 1.10.0-11.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW3.3 | python3-libs 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW3.3 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW3.3 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW3.3 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3449 | LOW3.3 | @tootallnate/once 2.0.0 fixed in 3.0.1, 2.0.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42264 | LOW3.28 | axios 1.12.1 fixed in 1.15.2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-42044 | LOW3.28 | axios 1.12.1 fixed in 1.15.2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1489 | LOW3.24 | glib2 2.68.4-18.el9_7.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40930 | LOW3.24 | libpng 2:1.6.37-12.el9_7.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15157 | LOW3.24 | undici 6.23.0 fixed in 6.28.0, 7.29.0, 8.9.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15157 | LOW3.24 | undici 7.18.2 fixed in 6.28.0, 7.29.0, 8.9.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4873 | LOW3.18 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6253 | LOW3.18 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7168 | LOW3.18 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-15588 | LOW3.18 | glib2 2.68.4-18.el9_7.1 fixed in 2.68.4-19.el9_8.9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86469 | LOW3.18 | glib2 2.68.4-18.el9_7.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | LOW3.18 | gnutls 3.8.3-9.el9 fixed in 3.8.3-10.el9_7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | LOW3.18 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libblkid 2.37.4-21.el9_7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4873 | LOW3.18 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6253 | LOW3.18 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7168 | LOW3.18 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libmount 2.37.4-21.el9_7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libsmartcols 2.37.4-21.el9_7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libuuid 2.37.4-21.el9_7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | LOW3.18 | python-unversioned-command 3.9.25-3.el9_7 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-19672 | LOW3.18 | python-unversioned-command 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW3.18 | python-unversioned-command 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4360 | LOW3.18 | python-unversioned-command 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW3.18 | python3 3.9.25-3.el9_7 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-19672 | LOW3.18 | python3 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW3.18 | python3 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4360 | LOW3.18 | python3 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-45409 | LOW3.18 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13149 | LOW3.18 | brace-expansion 1.1.12 fixed in 5.0.7, 1.1.16, 2.1.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102277 | LOW3.18 | brace-expansion 1.1.12 fixed in 5.0.12, 3.0.9, 2.1.7, 1.1.21 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-101911 | LOW3.18 | ip-address 9.0.5 fixed in 10.7.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-101912 | LOW3.18 | ip-address 9.0.5 fixed in 10.7.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-101913 | LOW3.18 | ip-address 9.0.5 fixed in 10.5.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-111997 | LOW3.18 | ip-address 9.0.5 fixed in 10.7.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41182 | LOW3.18 | langsmith 0.3.72 fixed in 0.5.19 | 0.2% 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-44288 | LOW3.18 | protobufjs 7.5.4 fixed in 7.5.6, 8.0.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44292 | LOW3.18 | protobufjs 7.5.4 fixed in 7.5.6, 8.0.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44294 | LOW3.18 | protobufjs 7.5.4 fixed in 7.5.6, 8.0.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54269 | LOW3.18 | protobufjs 7.5.4 fixed in 7.6.3, 8.6.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59875 | LOW3.18 | tar 7.5.4 fixed in 7.5.17 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84947 | LOW3.18 | undici 7.18.2 fixed in 7.29.1, 8.10.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85008 | LOW3.18 | undici 7.18.2 fixed in 7.29.1, 8.10.2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-44494 | LOW3.13 | axios 1.12.1 fixed in 1.16.0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-50181 | LOW3.11 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-50182 | LOW3.11 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-9232 | LOW3.1 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-28164 | LOW3 | libpng 2:1.6.37-12.el9_7.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44490 | LOW2.95 | axios 1.12.1 fixed in 1.16.0, 0.32.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-33941 | LOW2.95 | handlebars 4.7.8 fixed in 4.7.9 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-24842 | LOW2.95 | tar 7.5.4 fixed in 7.5.7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | LOW2.92 | curl-minimal 7.76.1-35.el9_7.3 fixed in 7.76.1-40.el9_8.5 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.92 | curl-minimal 7.76.1-35.el9_7.3 fixed in 7.76.1-40.el9_8.7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | LOW2.92 | libcurl-minimal 7.76.1-35.el9_7.3 fixed in 7.76.1-40.el9_8.5 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.92 | libcurl-minimal 7.76.1-35.el9_7.3 fixed in 7.76.1-40.el9_8.7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19445 | LOW2.92 | python-unversioned-command 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8.6 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | LOW2.92 | python-unversioned-command 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-19445 | LOW2.92 | python3 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8.6 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | LOW2.92 | python3 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-106445 | LOW2.92 | handlebars 4.7.8 fixed in 4.7.10 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-33938 | LOW2.92 | handlebars 4.7.8 fixed in 4.7.9 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-33940 | LOW2.92 | handlebars 4.7.8 fixed in 4.7.9 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.88 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | LOW2.88 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | LOW2.88 | python-unversioned-command 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.88 | python-unversioned-command 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.88 | python3 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.88 | python3 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-86472 | LOW2.88 | fast-uri 3.0.3 fixed in 2.4.7, 3.1.8, 4.1.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.82 | libblkid 2.37.4-21.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libmount 2.37.4-21.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libsmartcols 2.37.4-21.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libuuid 2.37.4-21.el9_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18503 | LOW2.8 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-44495 | LOW2.77 | axios 1.12.1 fixed in 1.15.2, 0.31.1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-1527 | LOW2.76 | undici 6.23.0 fixed in 6.24.0, 7.24.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1527 | LOW2.76 | undici 7.18.2 fixed in 6.24.0, 7.24.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4111 | LOW2.7 | libarchive 3.5.3-6.el9_6 fixed in 3.5.3-7.el9_7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-27135 | LOW2.7 | libnghttp2 1.43.0-6.el9 fixed in 1.43.0-6.el9_7.1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-15308 | LOW2.7 | python-unversioned-command 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8.2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-15308 | LOW2.7 | python3 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8.2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-114613 | LOW2.7 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-25639 | LOW2.7 | axios 1.12.1 fixed in 1.13.5, 0.30.3 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-44486 | LOW2.7 | axios 1.12.1 fixed in 1.16.0, 0.32.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-44487 | LOW2.7 | axios 1.12.1 fixed in 1.16.0, 0.32.0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-44488 | LOW2.7 | axios 1.12.1 fixed in 1.16.0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-44496 | LOW2.7 | axios 1.12.1 fixed in 1.16.0, 0.32.0 | 5.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42038 | LOW2.7 | axios 1.12.1 fixed in 1.15.1, 0.31.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42039 | LOW2.7 | axios 1.12.1 fixed in 1.15.1, 0.31.1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-67312 | LOW2.7 | axios 1.12.1 fixed in 0.33.0, 1.18.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-67313 | LOW2.7 | axios 1.12.1 fixed in 0.33.0, 1.18.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-67317 | LOW2.7 | axios 1.12.1 fixed in 1.18.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-33939 | LOW2.7 | handlebars 4.7.8 fixed in 4.7.9 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-30571 | LOW2.7 | libarchive 3.5.3-6.el9_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47081 | LOW2.7 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-56131 | LOW2.7 | expat 2.5.0-5.el9_7.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW2.7 | python-unversioned-command 3.9.25-3.el9_7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.7 | python-unversioned-command 3.9.25-3.el9_7 fixed in 3.9.25-5.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.7 | python-unversioned-command 3.9.25-3.el9_7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW2.7 | python3 3.9.25-3.el9_7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.7 | python3 3.9.25-3.el9_7 fixed in 3.9.25-5.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.7 | python3 3.9.25-3.el9_7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-7264 | LOW2.69 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 20.2% High Exploitation Risk | Directly Exposed |
| CVE-2024-7264 | LOW2.69 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 20.2% High Exploitation Risk | Directly Exposed |
| CVE-2026-19553 | LOW2.66 | python-unversioned-command 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8.6 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-19553 | LOW2.66 | python3 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8.6 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42033 | LOW2.66 | axios 1.12.1 fixed in 1.15.1, 0.31.1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-42035 | LOW2.66 | axios 1.12.1 fixed in 1.15.1, 0.31.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-67316 | LOW2.66 | axios 1.12.1 fixed in 1.18.0, 0.33.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-64505 | LOW2.64 | libpng 2:1.6.37-12.el9_7.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34757 | LOW2.64 | libpng 2:1.6.37-12.el9_7.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | LOW2.63 | python-unversioned-command 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8.3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-11940 | LOW2.63 | python3 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8.3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-1795 | LOW2.63 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | LOW2.6 | python-unversioned-command 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-4516 | LOW2.6 | python3 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4786 | LOW2.56 | python-unversioned-command 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4786 | LOW2.56 | python3 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1484 | LOW2.52 | glib2 2.68.4-18.el9_7.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18739 | LOW2.5 | popt 1.18-8.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18743 | LOW2.5 | popt 1.18-8.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40467 | LOW2.48 | gawk 5.1.0-6.el9 fixed in 5.1.0-6.el9_8.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW2.48 | python-unversioned-command 3.9.25-3.el9_7 fixed in 3.9.25-3.el9_7.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW2.48 | python-unversioned-command 3.9.25-3.el9_7 fixed in 3.9.25-3.el9_7.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-1299 | LOW2.48 | python-unversioned-command 3.9.25-3.el9_7 fixed in 3.9.25-3.el9_7.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW2.48 | python3 3.9.25-3.el9_7 fixed in 3.9.25-3.el9_7.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW2.48 | python3 3.9.25-3.el9_7 fixed in 3.9.25-3.el9_7.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-1299 | LOW2.48 | python3 3.9.25-3.el9_7 fixed in 3.9.25-3.el9_7.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-103242 | LOW2.48 | rpm 4.16.1.3-39.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-101900 | LOW2.34 | axios 1.12.1 fixed in 1.20.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-101904 | LOW2.34 | axios 1.12.1 fixed in 1.20.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-101908 | LOW2.34 | axios 1.12.1 fixed in 1.20.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42041 | LOW2.34 | axios 1.12.1 fixed in 1.15.1, 0.31.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-11053 | LOW2.34 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-9681 | LOW2.34 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14524 | LOW2.34 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | LOW2.34 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | LOW2.34 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6276 | LOW2.34 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86409 | LOW2.34 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-86414 | LOW2.34 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW2.34 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | LOW2.34 | expat 2.5.0-5.el9_7.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-24883 | LOW2.34 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-9820 | LOW2.34 | gnutls 3.8.3-9.el9 fixed in 3.8.3-10.el9_7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15028 | LOW2.34 | libarchive 3.5.3-6.el9_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-11053 | LOW2.34 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-9681 | LOW2.34 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14524 | LOW2.34 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | LOW2.34 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | LOW2.34 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6276 | LOW2.34 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86409 | LOW2.34 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-86414 | LOW2.34 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW2.34 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-34459 | LOW2.34 | libxml2 2.9.13-14.el9_7 fixed in 2.9.13-14.el9_8.1 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-27113 | LOW2.34 | libxml2 2.9.13-14.el9_7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-50495 | LOW2.34 | ncurses-base 6.2-12.20210508.el9 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-50495 | LOW2.34 | ncurses-libs 6.2-12.20210508.el9 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-41409 | LOW2.34 | pcre2 10.40-6.el9 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-89156 | LOW2.34 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-89160 | LOW2.34 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | LOW2.34 | pcre2-syntax 10.40-6.el9 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-89156 | LOW2.34 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-89160 | LOW2.34 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-3572 | LOW2.34 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-44605 | LOW2.34 | rpm 4.16.1.3-39.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44605 | LOW2.34 | rpm-libs 4.16.1.3-39.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| GHSA-c7w3-x93f-qmm8 | LOW2.3 | nodemailer 7.0.11 fixed in 8.0.4 | — | Directly Exposed |
| CVE-2025-5278 | LOW2.24 | coreutils-single 8.32-39.el9 fixed in 8.32-41.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW2.22 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-41080 | LOW2.22 | expat 2.5.0-5.el9_7.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0988 | LOW2.22 | glib2 2.68.4-18.el9_7.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3832 | LOW2.22 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW2.22 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-0989 | LOW2.22 | libxml2 2.9.13-14.el9_7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-101915 | LOW2.22 | @grpc/grpc-js 1.14.3 fixed in 1.13.6, 1.14.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-110095 | LOW2.22 | fast-uri 3.0.3 fixed in 2.4.8, 3.1.9, 4.2.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-110725 | LOW2.22 | fast-uri 3.0.3 fixed in 2.4.8, 3.1.9, 4.2.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11525 | LOW2.22 | undici 6.23.0 fixed in 6.27.0, 7.28.0, 8.5.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18540 | LOW2.22 | undici 6.23.0 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6733 | LOW2.22 | undici 6.23.0 fixed in 6.27.0, 7.28.0, 8.5.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11525 | LOW2.22 | undici 7.18.2 fixed in 6.27.0, 7.28.0, 8.5.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18540 | LOW2.22 | undici 7.18.2 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6733 | LOW2.22 | undici 7.18.2 fixed in 6.27.0, 7.28.0, 8.5.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18839 | LOW2.2 | popt 1.18-8.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-17591 | LOW2.16 | libarchive 3.5.3-6.el9_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-45803 | LOW2.14 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-101902 | LOW2.12 | axios 1.12.1 fixed in 0.34.0, 1.20.0 | 0.4% Theoretical Threat | Post-Exploit |
| GHSA-6688-9rhm-gjv2 | LOW2 | dompurify 3.3.0 fixed in 3.4.16 | — | Directly ExposedContext importance: MEDIUM |
| GHSA-c6gr-qvv4-5v3f | LOW2 | dompurify 3.3.0 fixed in 3.4.17 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2023-4156 | LOW1.99 | gawk 5.1.0-6.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-32636 | LOW1.99 | glib2 2.68.4-18.el9_7.1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-30258 | LOW1.99 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1632 | LOW1.99 | libarchive 3.5.3-6.el9_6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5915 | LOW1.99 | libarchive 3.5.3-6.el9_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5916 | LOW1.99 | libarchive 3.5.3-6.el9_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5917 | LOW1.99 | libarchive 3.5.3-6.el9_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5918 | LOW1.99 | libarchive 3.5.3-6.el9_6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-45322 | LOW1.99 | libxml2 2.9.13-14.el9_7 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-0232 | LOW1.99 | sqlite-libs 3.34.1-9.el9_7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-94266 | LOW1.98 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-94266 | LOW1.98 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW1.98 | python-unversioned-command 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.98 | python-unversioned-command 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.98 | python-unversioned-command 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.98 | python-unversioned-command 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.98 | python3 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.98 | python3 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.98 | python3 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.98 | python3 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-70873 | LOW1.98 | sqlite-libs 3.34.1-9.el9_7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58055 | LOW1.94 | libnghttp2 1.43.0-6.el9 fixed in 1.43.0-6.el9_8.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42042 | LOW1.94 | axios 1.12.1 fixed in 1.15.1, 0.31.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42034 | LOW1.91 | axios 1.12.1 fixed in 1.15.1, 0.31.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42036 | LOW1.91 | axios 1.12.1 fixed in 1.15.1, 0.31.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42037 | LOW1.91 | axios 1.12.1 fixed in 1.15.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3360 | LOW1.89 | glib2 2.68.4-18.el9_7.1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-7039 | LOW1.89 | glib2 2.68.4-18.el9_7.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-82209 | LOW1.86 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-82209 | LOW1.86 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-57062 | LOW1.74 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0992 | LOW1.74 | libxml2 2.9.13-14.el9_7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40175 | LOW1.73 | axios 1.12.1 fixed in 1.15.0, 0.31.0 | 1.9% Low-Moderate Risk | Post-Exploit |
| GHSA-7rx3-28cr-v5wh | LOW1.73 | handlebars 4.7.8 fixed in 4.7.9 | — | Post-Exploit |
| CVE-2026-106444 | LOW1.69 | handlebars 4.7.8 fixed in 4.7.10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-33916 | LOW1.69 | handlebars 4.7.8 fixed in 4.7.9 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1485 | LOW1.68 | glib2 2.68.4-18.el9_7.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18503 | LOW1.68 | python-unversioned-command 3.9.25-3.el9_7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18503 | LOW1.68 | python3 3.9.25-3.el9_7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1795 | LOW1.58 | python-unversioned-command 3.9.25-3.el9_7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1795 | LOW1.58 | python3 3.9.25-3.el9_7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-24515 | LOW1.5 | expat 2.5.0-5.el9_7.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-67319 | LOW1.33 | axios 1.12.1 fixed in 0.33.0, 1.18.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42040 | LOW1.33 | axios 1.12.1 fixed in 1.15.1, 0.31.1 | 0.2% Theoretical Threat | Post-Exploit |
| GHSA-442j-39wm-28r2 | LOW1.33 | handlebars 4.7.8 fixed in 4.7.9 | — | Post-Exploit |
| CVE-2025-6170 | LOW1.27 | libxml2 2.9.13-14.el9_7 fixed in 2.9.13-14.el9_8.2 | 0.3% Theoretical Threat | Directly Exposed |
Want to check another image? Run a full scan with the Docker Security Scanner.