Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker could exhaust CPU or memory through crafted HTTP/2 and TLS traffic, slowing or crashing the service on its exposed TLS ports. The most impactful reachable issue is CVE-2026-78669, a denial-of-service flaw that an unauthenticated client can trigger through default HTTP/2 handling. Note: CVE-2025-68121 only applies if the bundled Go program changes its TLS configuration at runtime between handshakes. Remediating the Go standard library findings should be completed before this image is used in production.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2025-68121 | HIGH8 | stdlib v1.25.3 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.9% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78669 | HIGH7.5 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-78659 | HIGH7.5 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-56862 | HIGH7.5 | stdlib v1.26.4 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-78669 | HIGH7.5 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-78659 | HIGH7.5 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-32283 | HIGH7.5 | stdlib v1.25.8 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-42499 | HIGH7.5 | stdlib v1.25.8 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42504 | HIGH7.5 | stdlib v1.25.8 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56862 | HIGH7.5 | stdlib v1.25.8 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-78669 | HIGH7.5 | stdlib v1.25.8 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-78659 | HIGH7.5 | stdlib v1.25.8 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2025-61726 | HIGH7.5 | stdlib v1.25.3 fixed in 1.24.12, 1.25.6 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-61729 | HIGH7.5 | stdlib v1.25.3 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25679 | HIGH7.5 | stdlib v1.25.3 fixed in 1.25.8, 1.26.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-32283 | HIGH7.5 | stdlib v1.25.3 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-42499 | HIGH7.5 | stdlib v1.25.3 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42504 | HIGH7.5 | stdlib v1.25.3 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56862 | HIGH7.5 | stdlib v1.25.3 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-78669 | HIGH7.5 | stdlib v1.25.3 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2025-61728 | HIGH7.5 | stdlib v1.25.3 fixed in 1.24.12, 1.25.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-78659 | HIGH7.5 | stdlib v1.25.3 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-32283 | HIGH7.5 | stdlib v1.26.1 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-42499 | HIGH7.5 | stdlib v1.26.1 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42504 | HIGH7.5 | stdlib v1.26.1 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56862 | HIGH7.5 | stdlib v1.26.1 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-78669 | HIGH7.5 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-78659 | HIGH7.5 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-78669 | HIGH7.5 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-78659 | HIGH7.5 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-19553 | HIGH7.4 | python3 3.9.25-7.el9_8.3 fixed in 3.9.25-7.el9_8.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-19553 | HIGH7.4 | python3-libs 3.9.25-7.el9_8.3 fixed in 3.9.25-7.el9_8.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-102268 | HIGH7.28 | PyJWT 2.13.0 fixed in 2.14.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102266 | HIGH7.28 | PyJWT 2.13.0 fixed in 2.14.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102267 | HIGH7.28 | PyJWT 2.13.0 fixed in 2.14.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-39828 | HIGH7.04 | golang.org/x/crypto v0.49.0 fixed in 0.52.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| GHSA-hrxh-6v49-42gf | HIGH7.04 | google.golang.org/grpc v1.80.0 fixed in 1.82.1 | — | Directly ExposedContext importance: MEDIUM |
| GHSA-hrxh-6v49-42gf | HIGH7.04 | google.golang.org/grpc v1.79.3 fixed in 1.82.1 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-39832 | MEDIUM6.96 | golang.org/x/crypto v0.49.0 fixed in 0.52.0 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107161 | MEDIUM6.9 | cyrus-sasl-lib 2.1.27-21.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM6.9 | cyrus-sasl-md5 2.1.27-21.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM6.9 | cyrus-sasl-plain 2.1.27-21.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM6.9 | glibc 2.34-283.el9_8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM6.9 | glibc 2.34-283.el9_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM6.9 | glibc-common 2.34-283.el9_8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM6.9 | glibc-common 2.34-283.el9_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM6.9 | glibc-minimal-langpack 2.34-283.el9_8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM6.9 | glibc-minimal-langpack 2.34-283.el9_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-88647 | MEDIUM6.9 | gnutls 3.8.10-9.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88648 | MEDIUM6.9 | gnutls 3.8.10-9.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.9 | python3 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.9 | python3 3.9.25-7.el9_8.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.9 | python3 3.9.25-7.el9_8.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.9 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.9 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.9 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-114406 | MEDIUM6.8 | ca-certificates 2025.2.80_v9.0.305-91.el9 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-111943 | MEDIUM6.8 | stdlib v1.27.0 fixed in 1.26.10, 1.27.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-111943 | MEDIUM6.8 | stdlib v1.26.4 fixed in 1.26.10, 1.27.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-111943 | MEDIUM6.8 | stdlib v1.25.8 fixed in 1.26.10, 1.27.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-111943 | MEDIUM6.8 | stdlib v1.25.3 fixed in 1.26.10, 1.27.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-111943 | MEDIUM6.8 | stdlib v1.26.1 fixed in 1.26.10, 1.27.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-111943 | MEDIUM6.8 | stdlib v1.26.8 fixed in 1.26.10, 1.27.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM6.7 | systemd-libs 252-67.el9_8.6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM6.7 | systemd-rpm-macros 252-67.el9_8.6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-102275 | MEDIUM6.56 | PyJWT 2.13.0 fixed in 2.15.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-39821 | MEDIUM6.56 | stdlib v1.26.4 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 1.8% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-39821 | MEDIUM6.56 | golang.org/x/net v0.52.0 fixed in 0.55.0 | 1.8% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-39821 | MEDIUM6.56 | stdlib v1.25.8 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 1.8% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-39821 | MEDIUM6.56 | stdlib v1.25.3 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 1.8% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-39821 | MEDIUM6.56 | golang.org/x/net v0.51.0 fixed in 0.55.0 | 1.8% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-39821 | MEDIUM6.56 | stdlib v1.26.1 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 1.8% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107778 | MEDIUM6.5 | krb5-libs 1.21.1-10.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4426 | MEDIUM6.5 | libarchive 3.5.3-11.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9149 | MEDIUM6.5 | libsolv 0.7.24-6.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9150 | MEDIUM6.5 | libsolv 0.7.24-6.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM6.5 | python3 3.9.25-7.el9_8.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | MEDIUM6.5 | python3 3.9.25-7.el9_8.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM6.5 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | MEDIUM6.5 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-54911 | MEDIUM6.5 | ujson 5.12.1 fixed in 5.13.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-47180 | MEDIUM6.5 | zeroconf 0.38.7 fixed in 0.149.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-47183 | MEDIUM6.5 | zeroconf 0.38.7 fixed in 0.149.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-47184 | MEDIUM6.5 | zeroconf 0.38.7 fixed in 0.149.7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48045 | MEDIUM6.5 | zeroconf 0.38.7 fixed in 0.149.12 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56866 | MEDIUM6.5 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-94439 | MEDIUM6.5 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56866 | MEDIUM6.5 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-94439 | MEDIUM6.5 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-81871 | MEDIUM6.5 | go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc v0.18.0 fixed in 0.21.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39825 | MEDIUM6.5 | stdlib v1.25.8 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56866 | MEDIUM6.5 | stdlib v1.25.8 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-94439 | MEDIUM6.5 | stdlib v1.25.8 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61727 | MEDIUM6.5 | stdlib v1.25.3 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39825 | MEDIUM6.5 | stdlib v1.25.3 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56866 | MEDIUM6.5 | stdlib v1.25.3 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-94439 | MEDIUM6.5 | stdlib v1.25.3 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39825 | MEDIUM6.5 | stdlib v1.26.1 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56866 | MEDIUM6.5 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-94439 | MEDIUM6.5 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56866 | MEDIUM6.5 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-94439 | MEDIUM6.5 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-19445 | MEDIUM6.48 | python3 3.9.25-7.el9_8.3 fixed in 3.9.25-7.el9_8.6 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-19445 | MEDIUM6.48 | python3-libs 3.9.25-7.el9_8.3 fixed in 3.9.25-7.el9_8.6 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-39831 | MEDIUM6.48 | golang.org/x/crypto v0.49.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-25681 | MEDIUM6.48 | golang.org/x/net v0.52.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-27136 | MEDIUM6.48 | golang.org/x/net v0.52.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-25681 | MEDIUM6.48 | golang.org/x/net v0.51.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-27136 | MEDIUM6.48 | golang.org/x/net v0.51.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-32282 | MEDIUM6.4 | stdlib v1.25.8 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32282 | MEDIUM6.4 | stdlib v1.25.3 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32282 | MEDIUM6.4 | stdlib v1.26.1 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-12345 | MEDIUM6.3 | python3 3.9.25-7.el9_8.3 fixed in 3.9.25-7.el9_8.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-12345 | MEDIUM6.3 | python3-libs 3.9.25-7.el9_8.3 fixed in 3.9.25-7.el9_8.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5958 | MEDIUM6.3 | sed 4.8-10.el9 No fix yet | 0.1% Theoretical Threat | 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-1757 | MEDIUM6.2 | libxml2 2.9.13-14.el9_8.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56391 | MEDIUM6.1 | coreutils-single 8.32-41.el9_8.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM6.1 | python3 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM6.1 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59890 | MEDIUM6.1 | setuptools 80.10.2 fixed in 83.0.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-94448 | MEDIUM6.1 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97030 | MEDIUM6.1 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-94448 | MEDIUM6.1 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97030 | MEDIUM6.1 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32289 | MEDIUM6.1 | stdlib v1.25.8 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-94448 | MEDIUM6.1 | stdlib v1.25.8 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97030 | MEDIUM6.1 | stdlib v1.25.8 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32289 | MEDIUM6.1 | stdlib v1.25.3 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-94448 | MEDIUM6.1 | stdlib v1.25.3 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97030 | MEDIUM6.1 | stdlib v1.25.3 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32289 | MEDIUM6.1 | stdlib v1.26.1 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-94448 | MEDIUM6.1 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97030 | MEDIUM6.1 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-94448 | MEDIUM6.1 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97030 | MEDIUM6.1 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-101917 | MEDIUM6 | PyJWT 2.13.0 fixed in 2.14.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-101918 | MEDIUM6 | PyJWT 2.13.0 fixed in 2.15.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102274 | MEDIUM6 | PyJWT 2.13.0 fixed in 2.14.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59884 | MEDIUM6 | pyasn1 0.6.3 fixed in 0.6.4 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59885 | MEDIUM6 | pyasn1 0.6.3 fixed in 0.6.4 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59886 | MEDIUM6 | pyasn1 0.6.3 fixed in 0.6.4 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-100352 | MEDIUM6 | github.com/getkin/kin-openapi v0.146.0 fixed in 0.148.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-100353 | MEDIUM6 | github.com/getkin/kin-openapi v0.146.0 fixed in 0.149.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-100354 | MEDIUM6 | github.com/getkin/kin-openapi v0.146.0 fixed in 0.149.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78669 | MEDIUM6 | golang.org/x/net v0.57.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78659 | MEDIUM6 | golang.org/x/net v0.57.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78660 | MEDIUM6 | golang.org/x/net v0.57.0 fixed in 0.60.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-84304 | MEDIUM6 | google.golang.org/grpc v1.82.1 fixed in 1.83.1 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-84445 | MEDIUM6 | google.golang.org/grpc v1.82.1 fixed in 1.82.2, 1.83.2, 1.84.0-dev.0.20260825144003-d5a41119e0e3, 1.85.0-dev.0.20260825072537-93e31b48545e | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78667 | MEDIUM6 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97031 | MEDIUM6 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78660 | MEDIUM6 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-94440 | MEDIUM6 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33818 | MEDIUM6 | stdlib v1.26.4 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56853 | MEDIUM6 | stdlib v1.26.4 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78667 | MEDIUM6 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97031 | MEDIUM6 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78660 | MEDIUM6 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-94440 | MEDIUM6 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-39829 | MEDIUM6 | golang.org/x/crypto v0.49.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-39830 | MEDIUM6 | golang.org/x/crypto v0.49.0 fixed in 0.52.0 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-39835 | MEDIUM6 | golang.org/x/crypto v0.49.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-46597 | MEDIUM6 | golang.org/x/crypto v0.49.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33814 | MEDIUM6 | golang.org/x/net v0.52.0 fixed in 0.53.0 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-46600 | MEDIUM6 | golang.org/x/net v0.52.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78669 | MEDIUM6 | golang.org/x/net v0.52.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78659 | MEDIUM6 | golang.org/x/net v0.52.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78660 | MEDIUM6 | golang.org/x/net v0.52.0 fixed in 0.60.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-84304 | MEDIUM6 | google.golang.org/grpc v1.80.0 fixed in 1.83.1 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-84445 | MEDIUM6 | google.golang.org/grpc v1.80.0 fixed in 1.82.2, 1.83.2, 1.84.0-dev.0.20260825144003-d5a41119e0e3, 1.85.0-dev.0.20260825072537-93e31b48545e | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-27145 | MEDIUM6 | stdlib v1.25.8 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-32280 | MEDIUM6 | stdlib v1.25.8 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33818 | MEDIUM6 | stdlib v1.25.8 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56853 | MEDIUM6 | stdlib v1.25.8 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78667 | MEDIUM6 | stdlib v1.25.8 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97031 | MEDIUM6 | stdlib v1.25.8 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78660 | MEDIUM6 | stdlib v1.25.8 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-94440 | MEDIUM6 | stdlib v1.25.8 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-46600 | MEDIUM6 | golang.org/x/net v0.55.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78669 | MEDIUM6 | golang.org/x/net v0.55.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78659 | MEDIUM6 | golang.org/x/net v0.55.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78660 | MEDIUM6 | golang.org/x/net v0.55.0 fixed in 0.60.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-84304 | MEDIUM6 | google.golang.org/grpc v1.79.3 fixed in 1.83.1 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-84445 | MEDIUM6 | google.golang.org/grpc v1.79.3 fixed in 1.82.2, 1.83.2, 1.84.0-dev.0.20260825144003-d5a41119e0e3, 1.85.0-dev.0.20260825072537-93e31b48545e | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-27145 | MEDIUM6 | stdlib v1.25.3 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-32280 | MEDIUM6 | stdlib v1.25.3 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33818 | MEDIUM6 | stdlib v1.25.3 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56853 | MEDIUM6 | stdlib v1.25.3 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78667 | MEDIUM6 | stdlib v1.25.3 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97031 | MEDIUM6 | stdlib v1.25.3 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78660 | MEDIUM6 | stdlib v1.25.3 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-94440 | MEDIUM6 | stdlib v1.25.3 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33814 | MEDIUM6 | golang.org/x/net v0.51.0 fixed in 0.53.0 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-46600 | MEDIUM6 | golang.org/x/net v0.51.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78669 | MEDIUM6 | golang.org/x/net v0.51.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78659 | MEDIUM6 | golang.org/x/net v0.51.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78660 | MEDIUM6 | golang.org/x/net v0.51.0 fixed in 0.60.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-27145 | MEDIUM6 | stdlib v1.26.1 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-32280 | MEDIUM6 | stdlib v1.26.1 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33818 | MEDIUM6 | stdlib v1.26.1 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56853 | MEDIUM6 | stdlib v1.26.1 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78667 | MEDIUM6 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97031 | MEDIUM6 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78660 | MEDIUM6 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-94440 | MEDIUM6 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78667 | MEDIUM6 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97031 | MEDIUM6 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78660 | MEDIUM6 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-94440 | MEDIUM6 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-5713 | MEDIUM6 | python3 3.9.25-7.el9_8.3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5713 | MEDIUM6 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-102271 | MEDIUM5.92 | PyJWT 2.13.0 fixed in 2.14.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102272 | MEDIUM5.92 | PyJWT 2.13.0 fixed in 2.14.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102273 | MEDIUM5.92 | PyJWT 2.13.0 fixed in 2.14.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| GHSA-pxh4-856f-4h89 | MEDIUM5.92 | PyJWT 2.13.0 fixed in 2.14.0 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-100351 | MEDIUM5.92 | github.com/getkin/kin-openapi v0.146.0 fixed in 0.147.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42508 | MEDIUM5.92 | golang.org/x/crypto v0.49.0 fixed in 0.52.0 | 6.9% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-67693 | MEDIUM5.9 | gnutls 3.8.10-9.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.9 | libxml2 2.9.13-14.el9_8.5 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-72897 | MEDIUM5.9 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.9 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.9 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-97032 | MEDIUM5.9 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| GHSA-xmrv-pmrh-hhx2 | MEDIUM5.9 | github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream v1.7.4 fixed in 1.7.8 | — | Directly Exposed |
| GHSA-xmrv-pmrh-hhx2 | MEDIUM5.9 | github.com/aws/aws-sdk-go-v2/service/s3 v1.95.1 fixed in 1.97.3 | — | Directly Exposed |
| CVE-2026-97032 | MEDIUM5.9 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-97032 | MEDIUM5.9 | stdlib v1.25.8 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-97032 | MEDIUM5.9 | stdlib v1.25.3 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-97032 | MEDIUM5.9 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-97032 | MEDIUM5.9 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46595 | MEDIUM5.68 | golang.org/x/crypto v0.49.0 fixed in 0.52.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-60753 | MEDIUM5.5 | libarchive 3.5.3-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5745 | MEDIUM5.5 | libarchive 3.5.3-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-82327 | MEDIUM5.5 | libsolv 0.7.24-6.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59677 | MEDIUM5.5 | policycoreutils 3.6-9.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-59677 | MEDIUM5.5 | policycoreutils-python-utils 3.6-9.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM5.5 | python3 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM5.5 | python3 3.9.25-7.el9_8.3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42308 | MEDIUM5.5 | python3 3.9.25-7.el9_8.3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM5.5 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM5.5 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42308 | MEDIUM5.5 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-59677 | MEDIUM5.5 | python3-policycoreutils 3.6-9.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-50812 | MEDIUM5.5 | sqlite-libs 3.34.1-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | systemd-libs 252-67.el9_8.6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | systemd-rpm-macros 252-67.el9_8.6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25645 | MEDIUM5.5 | requests 2.32.3 fixed in 2.33.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32288 | MEDIUM5.5 | stdlib v1.25.8 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32288 | MEDIUM5.5 | stdlib v1.25.3 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32288 | MEDIUM5.5 | stdlib v1.26.1 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| GHSA-6q48-6c7w-9gw2 | MEDIUM5.46 | certifi 2024.7.4 fixed in 2026.10.18 | — | Directly Exposed |
| CVE-2026-56854 | MEDIUM5.44 | golang.org/x/crypto v0.54.0 fixed in 0.55.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56854 | MEDIUM5.44 | golang.org/x/crypto v0.49.0 fixed in 0.55.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56854 | MEDIUM5.44 | golang.org/x/crypto v0.52.0 fixed in 0.55.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-1489 | MEDIUM5.4 | glib2 2.68.4-19.el9_8.10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39823 | MEDIUM5.4 | stdlib v1.25.8 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39826 | MEDIUM5.4 | stdlib v1.25.8 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27142 | MEDIUM5.4 | stdlib v1.25.3 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39823 | MEDIUM5.4 | stdlib v1.25.3 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39826 | MEDIUM5.4 | stdlib v1.25.3 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39823 | MEDIUM5.4 | stdlib v1.26.1 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39826 | MEDIUM5.4 | stdlib v1.26.1 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86469 | MEDIUM5.3 | glib2 2.68.4-19.el9_8.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | glibc 2.34-283.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | glibc-common 2.34-283.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | glibc-minimal-langpack 2.34-283.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42772 | MEDIUM5.3 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54873 | MEDIUM5.3 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | MEDIUM5.3 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM5.3 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-84784 | MEDIUM5.3 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-59676 | MEDIUM5.3 | policycoreutils 3.6-9.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-59676 | MEDIUM5.3 | policycoreutils-python-utils 3.6-9.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM5.3 | python3 3.9.25-7.el9_8.3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-19672 | MEDIUM5.3 | python3 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM5.3 | python3 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM5.3 | python3 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM5.3 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-19672 | MEDIUM5.3 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM5.3 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM5.3 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59676 | MEDIUM5.3 | python3-policycoreutils 3.6-9.el9 No fix yet | 0.1% 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-2025-66221 | MEDIUM5.3 | Werkzeug 3.1.3 fixed in 3.1.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-102598 | MEDIUM5.3 | Werkzeug 3.1.3 fixed in 3.1.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-21860 | MEDIUM5.3 | Werkzeug 3.1.3 fixed in 3.1.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27199 | MEDIUM5.3 | Werkzeug 3.1.3 fixed in 3.1.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45409 | MEDIUM5.3 | idna 3.10 fixed in 3.15 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48487 | MEDIUM5.3 | zeroconf 0.38.7 fixed in 0.149.16 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | MEDIUM5.3 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42505 | MEDIUM5.3 | stdlib v1.26.4 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | MEDIUM5.3 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-81872 | MEDIUM5.3 | go.opentelemetry.io/otel/sdk/log v0.19.0 fixed in 0.21.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42505 | MEDIUM5.3 | stdlib v1.25.8 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42507 | MEDIUM5.3 | stdlib v1.25.8 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | MEDIUM5.3 | stdlib v1.25.8 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61730 | MEDIUM5.3 | stdlib v1.25.3 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42505 | MEDIUM5.3 | stdlib v1.25.3 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42507 | MEDIUM5.3 | stdlib v1.25.3 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | MEDIUM5.3 | stdlib v1.25.3 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42505 | MEDIUM5.3 | stdlib v1.26.1 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42507 | MEDIUM5.3 | stdlib v1.26.1 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | MEDIUM5.3 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | MEDIUM5.3 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56865 | MEDIUM5.28 | golang.org/x/mod v0.38.0 fixed in 0.40.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56865 | MEDIUM5.28 | golang.org/x/mod v0.33.0 fixed in 0.40.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-103001 | MEDIUM5.2 | PyJWT 2.13.0 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-39827 | MEDIUM5.2 | golang.org/x/crypto v0.49.0 fixed in 0.52.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-39834 | MEDIUM5.2 | golang.org/x/crypto v0.49.0 fixed in 0.52.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-25680 | MEDIUM5.2 | golang.org/x/net v0.52.0 fixed in 0.55.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-25680 | MEDIUM5.2 | golang.org/x/net v0.51.0 fixed in 0.55.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-84303 | MEDIUM5.04 | google.golang.org/grpc v1.82.1 fixed in 1.83.1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-84303 | MEDIUM5.04 | google.golang.org/grpc v1.80.0 fixed in 1.83.1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-84303 | MEDIUM5.04 | google.golang.org/grpc v1.79.3 fixed in 1.83.1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42250 | MEDIUM5 | bzip2-libs 1.0.8-11.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM5 | krb5-libs 1.21.1-10.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-77214 | MEDIUM4.92 | expat 2.5.0-6.el9_8.5 fixed in 2.5.0-6.el9_8.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.9 | krb5-libs 1.21.1-10.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42502 | MEDIUM4.88 | golang.org/x/net v0.52.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42502 | MEDIUM4.88 | golang.org/x/net v0.51.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97687 | MEDIUM4.86 | python3-urllib3 1.26.5-8.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-97687 | MEDIUM4.86 | urllib3 2.7.0 fixed in 2.8.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56858 | MEDIUM4.86 | stdlib v1.26.4 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56864 | MEDIUM4.86 | golang.org/x/mod v0.38.0 fixed in 0.40.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56864 | MEDIUM4.86 | golang.org/x/mod v0.33.0 fixed in 0.40.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56858 | MEDIUM4.86 | stdlib v1.25.8 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56858 | MEDIUM4.86 | stdlib v1.25.3 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56858 | MEDIUM4.86 | stdlib v1.26.1 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libblkid 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libfdisk 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libmount 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libsmartcols 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libuuid 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.8 | python3 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.8 | python3 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.8 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.8 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | MEDIUM4.72 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54872 | MEDIUM4.72 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97032 | MEDIUM4.72 | golang.org/x/net v0.57.0 fixed in 0.60.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97032 | MEDIUM4.72 | golang.org/x/net v0.52.0 fixed in 0.60.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97032 | MEDIUM4.72 | golang.org/x/net v0.55.0 fixed in 0.60.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97032 | MEDIUM4.72 | golang.org/x/net v0.51.0 fixed in 0.60.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54875 | MEDIUM4.7 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-39822 | MEDIUM4.68 | stdlib v1.26.4 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39822 | MEDIUM4.68 | stdlib v1.25.8 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39822 | MEDIUM4.68 | stdlib v1.25.3 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39822 | MEDIUM4.68 | stdlib v1.26.1 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76641 | MEDIUM4.5 | expat 2.5.0-6.el9_8.5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-97689 | MEDIUM4.5 | python3-urllib3 1.26.5-8.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97689 | MEDIUM4.5 | urllib3 2.7.0 fixed in 2.8.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32952 | MEDIUM4.5 | github.com/Azure/go-ntlmssp v0.0.0-20221128193559-754e69321358 fixed in 0.1.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56851 | MEDIUM4.5 | golang.org/x/text v0.40.0 fixed in 0.41.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46600 | MEDIUM4.5 | stdlib v1.26.4 fixed in 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56859 | MEDIUM4.5 | stdlib v1.26.4 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56860 | MEDIUM4.5 | stdlib v1.26.4 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56851 | MEDIUM4.5 | golang.org/x/text v0.38.0 fixed in 0.41.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56852 | MEDIUM4.5 | golang.org/x/text v0.38.0 fixed in 0.39.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56851 | MEDIUM4.5 | golang.org/x/text v0.35.0 fixed in 0.41.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56852 | MEDIUM4.5 | golang.org/x/text v0.35.0 fixed in 0.39.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-32281 | MEDIUM4.5 | stdlib v1.25.8 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33811 | MEDIUM4.5 | stdlib v1.25.8 fixed in 1.25.10, 1.26.3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM4.5 | stdlib v1.25.8 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39820 | MEDIUM4.5 | stdlib v1.25.8 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39836 | MEDIUM4.5 | stdlib v1.25.8 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56859 | MEDIUM4.5 | stdlib v1.25.8 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56860 | MEDIUM4.5 | stdlib v1.25.8 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56851 | MEDIUM4.5 | golang.org/x/text v0.37.0 fixed in 0.41.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56852 | MEDIUM4.5 | golang.org/x/text v0.37.0 fixed in 0.39.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63209 | MEDIUM4.5 | github.com/klauspost/compress v1.17.9 fixed in 1.18.7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63209 | MEDIUM4.5 | github.com/klauspost/compress v1.18.5 fixed in 1.18.7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-32281 | MEDIUM4.5 | stdlib v1.25.3 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33811 | MEDIUM4.5 | stdlib v1.25.3 fixed in 1.25.10, 1.26.3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM4.5 | stdlib v1.25.3 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39820 | MEDIUM4.5 | stdlib v1.25.3 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39836 | MEDIUM4.5 | stdlib v1.25.3 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56859 | MEDIUM4.5 | stdlib v1.25.3 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56860 | MEDIUM4.5 | stdlib v1.25.3 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56851 | MEDIUM4.5 | golang.org/x/text v0.25.0 fixed in 0.41.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56852 | MEDIUM4.5 | golang.org/x/text v0.25.0 fixed in 0.39.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63209 | MEDIUM4.5 | github.com/klauspost/compress v1.18.4 fixed in 1.18.7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-32281 | MEDIUM4.5 | stdlib v1.26.1 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33811 | MEDIUM4.5 | stdlib v1.26.1 fixed in 1.25.10, 1.26.3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM4.5 | stdlib v1.26.1 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39820 | MEDIUM4.5 | stdlib v1.26.1 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39836 | MEDIUM4.5 | stdlib v1.26.1 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46600 | MEDIUM4.5 | stdlib v1.26.1 fixed in 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56859 | MEDIUM4.5 | stdlib v1.26.1 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56860 | MEDIUM4.5 | stdlib v1.26.1 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-30571 | MEDIUM4.5 | libarchive 3.5.3-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47081 | MEDIUM4.5 | requests 2.32.3 fixed in 2.32.4 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | MEDIUM4.5 | python3 3.9.25-7.el9_8.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | MEDIUM4.5 | python3 3.9.25-7.el9_8.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | MEDIUM4.5 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | MEDIUM4.5 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69277 | MEDIUM4.5 | PyNaCl 1.5.0 fixed in 1.6.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63374 | MEDIUM4.44 | anyio 4.9.0 fixed in 4.14.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39833 | MEDIUM4.4 | golang.org/x/crypto v0.49.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-19079 | MEDIUM4.4 | policycoreutils 3.6-9.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-19079 | MEDIUM4.4 | policycoreutils-python-utils 3.6-9.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-19079 | MEDIUM4.4 | python3-policycoreutils 3.6-9.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | MEDIUM4.33 | python3 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | MEDIUM4.33 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102269 | MEDIUM4.32 | PyJWT 2.13.0 fixed in 2.14.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42506 | MEDIUM4.32 | golang.org/x/net v0.52.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42506 | MEDIUM4.32 | golang.org/x/net v0.51.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-27205 | MEDIUM4.3 | Flask 3.0.0 fixed in 3.1.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-112940 | MEDIUM4.26 | filelock 3.32.7 fixed in 4.2.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102265 | MEDIUM4.24 | PyJWT 2.13.0 fixed in 2.14.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56855 | MEDIUM4.24 | golang.org/x/crypto v0.54.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78662 | MEDIUM4.24 | golang.org/x/crypto v0.54.0 fixed in 0.56.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78663 | MEDIUM4.24 | golang.org/x/net v0.57.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-46598 | MEDIUM4.24 | golang.org/x/crypto v0.49.0 fixed in 0.52.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56855 | MEDIUM4.24 | golang.org/x/crypto v0.49.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78662 | MEDIUM4.24 | golang.org/x/crypto v0.49.0 fixed in 0.56.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78663 | MEDIUM4.24 | golang.org/x/net v0.52.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56855 | MEDIUM4.24 | golang.org/x/crypto v0.52.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78662 | MEDIUM4.24 | golang.org/x/crypto v0.52.0 fixed in 0.56.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78663 | MEDIUM4.24 | golang.org/x/net v0.55.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78663 | MEDIUM4.24 | golang.org/x/net v0.51.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53613 | MEDIUM4.2 | libblkid 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libfdisk 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libmount 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libsmartcols 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libuuid 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1484 | MEDIUM4.2 | glib2 2.68.4-19.el9_8.10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | glibc 2.34-283.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | glibc-common 2.34-283.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | glibc-minimal-langpack 2.34-283.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-8932 | MEDIUM4.14 | curl 7.76.1-40.el9_8.8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9080 | MEDIUM4.14 | curl 7.76.1-40.el9_8.8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9545 | MEDIUM4.14 | curl 7.76.1-40.el9_8.8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9546 | MEDIUM4.14 | curl 7.76.1-40.el9_8.8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM4.14 | expat 2.5.0-6.el9_8.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM4.14 | expat 2.5.0-6.el9_8.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM4.14 | expat 2.5.0-6.el9_8.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM4.14 | expat 2.5.0-6.el9_8.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56407 | MEDIUM4.14 | expat 2.5.0-6.el9_8.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76957 | MEDIUM4.14 | expat 2.5.0-6.el9_8.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.14 | libatomic 11.5.0-15.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.14 | libatomic 11.5.0-15.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8932 | MEDIUM4.14 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9080 | MEDIUM4.14 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9545 | MEDIUM4.14 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9546 | MEDIUM4.14 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.14 | libgcc 11.5.0-14.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.14 | libgcc 11.5.0-14.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.14 | libgomp 11.5.0-14.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.14 | libgomp 11.5.0-14.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.14 | libstdc++ 11.5.0-14.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.14 | libstdc++ 11.5.0-14.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32284 | MEDIUM4.14 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-103242 | MEDIUM4.14 | python3-rpm 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78367 | MEDIUM4.14 | python3-rpm 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-84837 | MEDIUM4.14 | python3-rpm 4.16.1.3-40.el9 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-95519 | MEDIUM4.14 | python3-rpm 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95520 | MEDIUM4.14 | python3-rpm 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95521 | MEDIUM4.14 | python3-rpm 4.16.1.3-40.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78367 | MEDIUM4.14 | rpm 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-84837 | MEDIUM4.14 | rpm 4.16.1.3-40.el9 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-95519 | MEDIUM4.14 | rpm 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95520 | MEDIUM4.14 | rpm 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95521 | MEDIUM4.14 | rpm 4.16.1.3-40.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-103242 | MEDIUM4.14 | rpm-build-libs 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78367 | MEDIUM4.14 | rpm-build-libs 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-84837 | MEDIUM4.14 | rpm-build-libs 4.16.1.3-40.el9 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-95519 | MEDIUM4.14 | rpm-build-libs 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95520 | MEDIUM4.14 | rpm-build-libs 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95521 | MEDIUM4.14 | rpm-build-libs 4.16.1.3-40.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-103242 | MEDIUM4.14 | rpm-libs 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78367 | MEDIUM4.14 | rpm-libs 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-84837 | MEDIUM4.14 | rpm-libs 4.16.1.3-40.el9 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-95519 | MEDIUM4.14 | rpm-libs 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95520 | MEDIUM4.14 | rpm-libs 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95521 | MEDIUM4.14 | rpm-libs 4.16.1.3-40.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-103242 | MEDIUM4.14 | rpm-plugin-selinux 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78367 | MEDIUM4.14 | rpm-plugin-selinux 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-84837 | MEDIUM4.14 | rpm-plugin-selinux 4.16.1.3-40.el9 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-95519 | MEDIUM4.14 | rpm-plugin-selinux 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95520 | MEDIUM4.14 | rpm-plugin-selinux 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95521 | MEDIUM4.14 | rpm-plugin-selinux 4.16.1.3-40.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-103242 | MEDIUM4.14 | rpm-sign-libs 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78367 | MEDIUM4.14 | rpm-sign-libs 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-84837 | MEDIUM4.14 | rpm-sign-libs 4.16.1.3-40.el9 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-95519 | MEDIUM4.14 | rpm-sign-libs 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95520 | MEDIUM4.14 | rpm-sign-libs 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95521 | MEDIUM4.14 | rpm-sign-libs 4.16.1.3-40.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-59871 | MEDIUM4.14 | tar 2:1.34-13.el9_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-39881 | MEDIUM4.14 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-13034 | MEDIUM4.08 | curl 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13034 | MEDIUM4.08 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39824 | MEDIUM4 | golang.org/x/sys v0.34.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-39824 | MEDIUM4 | golang.org/x/sys v0.42.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-39824 | MEDIUM4 | golang.org/x/sys v0.33.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-39824 | MEDIUM4 | golang.org/x/sys v0.41.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | LOW3.96 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90829 | LOW3.96 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90831 | LOW3.96 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28419 | LOW3.96 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102270 | LOW3.92 | PyJWT 2.13.0 fixed in 2.14.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-19931 | LOW3.9 | curl 7.76.1-40.el9_8.8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-3784 | LOW3.9 | curl 7.76.1-40.el9_8.8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5545 | LOW3.9 | curl 7.76.1-40.el9_8.8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6429 | LOW3.9 | curl 7.76.1-40.el9_8.8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | curl 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19931 | LOW3.9 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-3784 | LOW3.9 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5545 | LOW3.9 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6429 | LOW3.9 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13346 | LOW3.9 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-33056 | LOW3.9 | tar 2:1.34-13.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-15028 | LOW3.9 | libarchive 3.5.3-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-27113 | LOW3.9 | libxml2 2.9.13-14.el9_8.5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-41996 | LOW3.9 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28387 | LOW3.9 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | LOW3.9 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | LOW3.9 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | LOW3.9 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42765 | LOW3.9 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | LOW3.9 | pcre2 10.40-7.el9_8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41409 | LOW3.9 | pcre2-syntax 10.40-7.el9_8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-27171 | LOW3.9 | zlib 1.2.11-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-29040 | LOW3.74 | tpm2-tss 3.2.3-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0988 | LOW3.7 | glib2 2.68.4-19.el9_8.10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | glibc 2.34-283.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | glibc-common 2.34-283.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | glibc-minimal-langpack 2.34-283.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.7 | libxml2 2.9.13-14.el9_8.5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.7 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35191 | LOW3.7 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-26958 | LOW3.7 | filippo.io/edwards25519 v1.1.0 fixed in 1.1.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-90804 | LOW3.66 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-57451 | LOW3.66 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-17591 | LOW3.6 | libarchive 3.5.3-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102633 | LOW3.54 | expat 2.5.0-6.el9_8.5 fixed in 2.5.0-6.el9_8.7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-113351 | LOW3.54 | expat 2.5.0-6.el9_8.5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | LOW3.54 | expat 2.5.0-6.el9_8.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-72897 | LOW3.54 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-75805 | LOW3.54 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-77696 | LOW3.54 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.52 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | LOW3.52 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | LOW3.52 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44405 | LOW3.4 | paramiko 3.4.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | LOW3.36 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.31 | elfutils-default-yama-scope 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | LOW3.31 | elfutils-default-yama-scope 0.194-1.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | LOW3.31 | elfutils-default-yama-scope 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | LOW3.31 | elfutils-default-yama-scope 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.31 | elfutils-libelf 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | LOW3.31 | elfutils-libelf 0.194-1.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | LOW3.31 | elfutils-libelf 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | LOW3.31 | elfutils-libelf 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.31 | elfutils-libs 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | LOW3.31 | elfutils-libs 0.194-1.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | LOW3.31 | elfutils-libs 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | LOW3.31 | elfutils-libs 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-32636 | LOW3.31 | glib2 2.68.4-19.el9_8.10 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1632 | LOW3.31 | libarchive 3.5.3-11.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5915 | LOW3.31 | libarchive 3.5.3-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5916 | LOW3.31 | libarchive 3.5.3-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5917 | LOW3.31 | libarchive 3.5.3-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5918 | LOW3.31 | libarchive 3.5.3-11.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-45322 | LOW3.31 | libxml2 2.9.13-14.el9_8.5 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | LOW3.31 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-0232 | LOW3.31 | sqlite-libs 3.34.1-11.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | LOW3.3 | expat 2.5.0-6.el9_8.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | LOW3.3 | expat 2.5.0-6.el9_8.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | LOW3.3 | expat 2.5.0-6.el9_8.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | LOW3.3 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-90830 | LOW3.3 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25645 | LOW3.3 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53655 | LOW3.3 | tar 2:1.34-13.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28418 | LOW3.3 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45130 | LOW3.3 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-73070 | LOW3.3 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64847 | LOW3.3 | anyio 4.9.0 fixed in 4.14.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41990 | LOW3.3 | libgcrypt 1.10.0-13.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW3.3 | python3 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW3.3 | python3 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW3.3 | python3 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW3.3 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW3.3 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW3.3 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW3.3 | sqlite-libs 3.34.1-11.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56857 | LOW3.3 | stdlib v1.27.0 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56857 | LOW3.3 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-81870 | LOW3.3 | go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.43.0 fixed in 1.45.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-81870 | LOW3.3 | go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.42.0 fixed in 1.45.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-81870 | LOW3.3 | go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp v1.43.0 fixed in 1.45.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-81870 | LOW3.3 | go.opentelemetry.io/otel/sdk v1.43.0 fixed in 1.45.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56857 | LOW3.3 | stdlib v1.25.8 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56857 | LOW3.3 | stdlib v1.25.3 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56857 | LOW3.3 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56857 | LOW3.3 | stdlib v1.26.8 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| GO-2026-5932 | LOW3.2 | golang.org/x/crypto v0.54.0 No fix yet | — | Directly ExposedContext importance: MEDIUM |
| GO-2026-5932 | LOW3.2 | golang.org/x/crypto v0.49.0 No fix yet | — | Directly ExposedContext importance: MEDIUM |
| GO-2026-5932 | LOW3.2 | golang.org/x/crypto v0.52.0 No fix yet | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-4873 | LOW3.18 | curl 7.76.1-40.el9_8.8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6253 | LOW3.18 | curl 7.76.1-40.el9_8.8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7168 | LOW3.18 | curl 7.76.1-40.el9_8.8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libblkid 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4873 | LOW3.18 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6253 | LOW3.18 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7168 | LOW3.18 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libfdisk 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libmount 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libsmartcols 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libuuid 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42772 | LOW3.18 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-54873 | LOW3.18 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-75804 | LOW3.18 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-75806 | LOW3.18 | openssl 1:3.5.8-2.el9_8 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-84784 | LOW3.18 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45409 | LOW3.18 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59875 | LOW3.18 | tar 2:1.34-13.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | util-linux 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | util-linux-core 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-44656 | LOW3.18 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-97688 | LOW3.18 | urllib3 2.7.0 fixed in 2.8.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3360 | LOW3.15 | glib2 2.68.4-19.el9_8.10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-7039 | LOW3.15 | glib2 2.68.4-19.el9_8.10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-29923 | LOW3.15 | github.com/redis/go-redis/v9 v9.7.0 fixed in 9.7.3, 9.6.3, 9.5.5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-50181 | LOW3.11 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-50182 | LOW3.11 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-9232 | LOW3.1 | openssl-libs 1:3.5.8-2.el9_8 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-6845 | LOW3 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-90802 | LOW3 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33810 | LOW2.95 | stdlib v1.26.1 fixed in 1.26.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-0992 | LOW2.9 | libxml2 2.9.13-14.el9_8.5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | LOW2.88 | util-linux 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | util-linux-core 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.88 | curl 7.76.1-40.el9_8.8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | LOW2.88 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.1% 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-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libfdisk 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libmount 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libsmartcols 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libuuid 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54875 | LOW2.82 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-64118 | LOW2.82 | tar 2:1.34-13.el9_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | util-linux 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | util-linux-core 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-57452 | LOW2.82 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43961 | LOW2.81 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1485 | LOW2.8 | glib2 2.68.4-19.el9_8.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18503 | LOW2.8 | python3 3.9.25-7.el9_8.3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18503 | LOW2.8 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-114613 | LOW2.7 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-57585 | LOW2.7 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-47081 | LOW2.7 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-56131 | LOW2.7 | expat 2.5.0-6.el9_8.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-7264 | LOW2.69 | curl 7.76.1-40.el9_8.8 No fix yet | 20.2% High Exploitation Risk | Directly Exposed |
| CVE-2024-7264 | LOW2.69 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 20.2% High Exploitation Risk | Directly Exposed |
| CVE-2026-42307 | LOW2.64 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1795 | LOW2.63 | python3 3.9.25-7.el9_8.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1795 | LOW2.63 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | LOW2.52 | util-linux 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | util-linux-core 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| 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-27139 | LOW2.5 | stdlib v1.25.3 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5773 | LOW2.48 | curl 7.76.1-40.el9_8.8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW2.48 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-103242 | LOW2.48 | rpm 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW2.48 | tar 2:1.34-13.el9_8 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-90803 | LOW2.45 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-11053 | LOW2.34 | curl 7.76.1-40.el9_8.8 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-9681 | LOW2.34 | curl 7.76.1-40.el9_8.8 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14524 | LOW2.34 | curl 7.76.1-40.el9_8.8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | LOW2.34 | curl 7.76.1-40.el9_8.8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | LOW2.34 | curl 7.76.1-40.el9_8.8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6276 | LOW2.34 | curl 7.76.1-40.el9_8.8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86409 | LOW2.34 | curl 7.76.1-40.el9_8.8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW2.34 | curl 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW2.34 | curl 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53910 | LOW2.34 | diffutils 3.7-12.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66382 | LOW2.34 | expat 2.5.0-6.el9_8.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | LOW2.34 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-66864 | LOW2.34 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | LOW2.34 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | LOW2.34 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | LOW2.34 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | LOW2.34 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.3% 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-2024-11053 | LOW2.34 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-9681 | LOW2.34 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14524 | LOW2.34 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | LOW2.34 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | LOW2.34 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6276 | LOW2.34 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86409 | LOW2.34 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW2.34 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW2.34 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | 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-2024-41996 | LOW2.34 | openssl 1:3.5.8-2.el9_8 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28387 | LOW2.34 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-28388 | LOW2.34 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-28389 | LOW2.34 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | LOW2.34 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42765 | LOW2.34 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2021-3572 | LOW2.34 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-44605 | LOW2.34 | python3-rpm 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44605 | LOW2.34 | rpm 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44605 | LOW2.34 | rpm-build-libs 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44605 | LOW2.34 | rpm-libs 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44605 | LOW2.34 | rpm-plugin-selinux 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44605 | LOW2.34 | rpm-sign-libs 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-3927 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3968 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3973 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3974 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-4136 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-4166 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-4173 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-4187 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0213 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1616 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1619 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1620 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1674 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1720 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2042 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2124 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2125 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2126 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2129 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2175 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2182 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2183 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2206 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2207 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2208 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2210 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2257 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2284 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2285 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2286 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2287 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2304 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2343 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2344 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2345 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3278 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3705 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5344 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-26269 | LOW2.34 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-29768 | LOW2.24 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | curl 7.76.1-40.el9_8.8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | curl 7.76.1-40.el9_8.8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | curl 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | curl 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | curl 7.76.1-40.el9_8.8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW2.22 | expat 2.5.0-6.el9_8.5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW2.22 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-35191 | LOW2.22 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| 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-2023-45803 | LOW2.14 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4156 | LOW1.99 | gawk 5.1.0-6.el9_8.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47007 | LOW1.99 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47010 | LOW1.99 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47011 | LOW1.99 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | LOW1.99 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | LOW1.99 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | LOW1.99 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | LOW1.99 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | LOW1.99 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | LOW1.99 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | LOW1.99 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | LOW1.99 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | LOW1.99 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.3% 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-2021-46195 | LOW1.99 | libatomic 11.5.0-15.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | libatomic 11.5.0-15.el9 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | LOW1.99 | libgcc 11.5.0-14.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | libgcc 11.5.0-14.el9 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | LOW1.99 | libgomp 11.5.0-14.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | libgomp 11.5.0-14.el9 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | LOW1.99 | libstdc++ 11.5.0-14.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | libstdc++ 11.5.0-14.el9 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | LOW1.99 | openssl 1:3.5.8-2.el9_8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2021-3928 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-0351 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-1725 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-2522 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-2817 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-2819 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-2845 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-2849 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-2862 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-2874 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-2889 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-2923 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-2946 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-2980 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-2982 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-3016 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-3037 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-3099 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-3134 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-3153 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-3234 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-3235 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-3256 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-3296 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-3297 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-3324 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-3352 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-4141 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-4292 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-4293 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-0049 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-0051 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-0054 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-0288 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-0433 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-0512 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-1127 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-1170 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-1175 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-1264 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-2609 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-2610 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-46246 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4734 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-4735 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4738 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4751 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4781 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-48231 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-48232 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-48233 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-48234 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-48235 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-48236 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-48237 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-48706 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-5441 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-5535 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-22667 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-41957 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-41965 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43374 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-43802 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-45306 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47814 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1215 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-22134 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-24014 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-26603 | LOW1.99 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94266 | LOW1.98 | curl 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW1.98 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW1.98 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW1.98 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW1.98 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW1.98 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW1.98 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW1.98 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94266 | LOW1.98 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-112913 | LOW1.98 | filelock 3.32.7 fixed in 4.2.1 | — | Directly Exposed |
| CVE-2025-1152 | LOW1.89 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-82209 | LOW1.86 | curl 7.76.1-40.el9_8.8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-82209 | LOW1.86 | libcurl-minimal 7.76.1-40.el9_8.8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-9232 | LOW1.86 | openssl 1:3.5.8-2.el9_8 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-57062 | LOW1.74 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.1% 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-2023-39804 | LOW1.68 | tar 2:1.34-13.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW1.68 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW1.68 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW1.68 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW1.58 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW1.58 | gdb-gdbserver 16.3-3.1.el9_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-24515 | LOW1.5 | expat 2.5.0-6.el9_8.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-112907 | LOW1.5 | filelock 3.32.7 fixed in 4.2.1 | — | Directly Exposed |
| CVE-2026-28422 | LOW1.32 | vim-minimal 2:8.2.2637-26.el9_8.23 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| GHSA-xmj3-9gf7-h52w | LOW1 | setuptools 80.10.2 fixed in 84.1.0 | — | Directly Exposed |
| CVE-2026-4105 | NONE0 | systemd 252-67.el9_8.6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | systemd-pam 252-67.el9_8.6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-12610 | NONE0 | pam 1.5.1-28.el9_8.1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15059 | NONE0 | systemd 252-67.el9_8.6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-15059 | NONE0 | systemd-pam 252-67.el9_8.6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.