Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. In this Metasploit framework container, exploiting exposed libraries such as CVE-2026-63072 or CVE-2026-85396 could allow an attacker to corrupt process memory, cause denial of service, or write files outside intended extraction paths, disrupting availability or compromising data integrity. The image also carries many lower-severity exposed and post-exploit findings, but the calculated score remains CAUTION rather than DANGEROUS because no exposed finding reaches the higher severity thresholds in the provided inputs. No specific compensating control in the provided inputs is documented to fully eliminate these findings.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-63072 | MEDIUM6.38 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-93990 | MEDIUM6.38 | libexpat 2.8.4-r0 fixed in 2.8.5-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63072 | MEDIUM6.38 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-54904 | MEDIUM6.38 | concurrent-ruby 1.3.5 fixed in >= 1.3.7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-54297 | MEDIUM6.38 | faraday 2.7.11 fixed in ~> 1.10.6, >= 2.14.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-79770 | MEDIUM6.38 | nokogiri 1.18.10 fixed in >= 1.19.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-80212 | MEDIUM6.38 | resolv 0.3.0 fixed in ~> 0.3.2, >= 0.7.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-85396 | MEDIUM6.38 | rubyzip 3.3.0 fixed in >= 3.4.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-54463 | MEDIUM6.38 | websocket-driver 0.7.7 fixed in >= 0.8.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54465 | MEDIUM6.38 | websocket-driver 0.7.7 fixed in >= 0.8.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-61666 | MEDIUM6.38 | websocket-driver 0.7.7 fixed in >= 0.8.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | MEDIUM6.29 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | MEDIUM6.29 | libssl3 3.3.7-r0 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42246 | MEDIUM6.29 | net-imap 0.4.19 fixed in ~> 0.3.10, ~> 0.4.24, ~> 0.5.14, >= 0.6.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42246 | MEDIUM6.29 | net-imap 0.5.6 fixed in ~> 0.3.10, ~> 0.4.24, ~> 0.5.14, >= 0.6.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47242 | MEDIUM6.21 | net-imap 0.4.19 fixed in ~> 0.5.15, >= 0.6.4.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-47242 | MEDIUM6.21 | net-imap 0.5.6 fixed in ~> 0.5.15, >= 0.6.4.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-35611 | MEDIUM5.52 | addressable 2.8.7 fixed in >= 2.9.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33637 | MEDIUM5.52 | faraday 2.7.11 fixed in >= 2.14.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-43857 | MEDIUM5.52 | net-imap 0.4.19 fixed in ~> 0.2.5, ~> 0.3.9, ~> 0.4.20, >= 0.5.7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42256 | MEDIUM5.52 | net-imap 0.4.19 fixed in ~> 0.4.24, ~> 0.5.14, >= 0.6.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-43857 | MEDIUM5.52 | net-imap 0.5.6 fixed in ~> 0.2.5, ~> 0.3.9, ~> 0.4.20, >= 0.5.7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42256 | MEDIUM5.52 | net-imap 0.5.6 fixed in ~> 0.4.24, ~> 0.5.14, >= 0.6.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM5.3 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42766 | MEDIUM5.3 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42258 | MEDIUM5.3 | net-imap 0.4.19 fixed in ~> 0.4.24, ~> 0.5.14, >= 0.6.4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42258 | MEDIUM5.3 | net-imap 0.5.6 fixed in ~> 0.4.24, ~> 0.5.14, >= 0.6.4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-47240 | MEDIUM5.18 | net-imap 0.4.19 fixed in ~> 0.5.15, >= 0.6.4.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-47240 | MEDIUM5.18 | net-imap 0.5.6 fixed in ~> 0.5.15, >= 0.6.4.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.02 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-72897 | MEDIUM5.02 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.02 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.02 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-102633 | MEDIUM5.02 | libexpat 2.8.4-r0 fixed in 2.9.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.02 | libssl3 3.3.7-r0 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-72897 | MEDIUM5.02 | libssl3 3.3.7-r0 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.02 | libssl3 3.3.7-r0 fixed in 3.3.7-r2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.02 | libssl3 3.3.7-r0 fixed in 3.3.7-r2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-47241 | MEDIUM5.02 | net-imap 0.4.19 fixed in ~> 0.5.15, >= 0.6.4.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-47241 | MEDIUM5.02 | net-imap 0.5.6 fixed in ~> 0.5.15, >= 0.6.4.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25765 | MEDIUM4.93 | faraday 2.7.11 fixed in ~> 1.10.5, >= 2.14.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib 1.3.1-r2 fixed in 1.3.2-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54905 | MEDIUM4.67 | concurrent-ruby 1.3.5 fixed in >= 1.3.7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54522 | MEDIUM4.59 | msgpack 1.6.1 fixed in >= 1.8.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-73648 | MEDIUM4.59 | rails-html-sanitizer 1.6.2 fixed in >= 1.7.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | MEDIUM4.5 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM4.5 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84784 | MEDIUM4.5 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | MEDIUM4.5 | libssl3 3.3.7-r0 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM4.5 | libssl3 3.3.7-r0 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84784 | MEDIUM4.5 | libssl3 3.3.7-r0 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14762 | MEDIUM4.5 | aws-sdk-s3 1.182.0 fixed in >= 1.208.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-79771 | MEDIUM4.5 | nokogiri 1.18.10 fixed in >= 1.19.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-79772 | MEDIUM4.5 | nokogiri 1.18.10 fixed in >= 1.19.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-58767 | MEDIUM4.5 | rexml 3.3.9 fixed in >= 3.4.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-58767 | MEDIUM4.5 | rexml 3.4.1 fixed in >= 3.4.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54464 | MEDIUM4.5 | websocket-driver 0.7.7 fixed in >= 0.8.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-92392 | MEDIUM4.13 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-54875 | MEDIUM4 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54875 | MEDIUM4 | libssl3 3.3.7-r0 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-73490 | MEDIUM4 | loofah 2.24.1 fixed in >= 2.25.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5773 | LOW3.82 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63072 | LOW3.82 | openssl 3.3.7-r0 fixed in 3.3.7-r1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-47736 | LOW3.82 | puma 6.6.0 fixed in ~> 7.2.1, >= 8.0.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-47737 | LOW3.82 | puma 6.6.0 fixed in ~> 7.2.1, >= 8.0.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-54619 | LOW3.82 | sqlite3 2.9.4 fixed in >= 2.9.5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54620 | LOW3.82 | sqlite3 2.9.4 fixed in >= 2.9.5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | LOW3.77 | openssl 3.3.7-r0 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19553 | LOW3.77 | pyc 3.12.14-r0 fixed in 3.12.15-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19553 | LOW3.77 | python3 3.12.14-r0 fixed in 3.12.15-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-82049 | LOW3.62 | pyc 3.12.14-r0 fixed in 3.12.15-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-82049 | LOW3.62 | python3 3.12.14-r0 fixed in 3.12.15-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63073 | LOW3.54 | openssl 3.3.7-r0 fixed in 3.3.7-r1 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-80213 | LOW3.4 | resolv 0.3.0 fixed in ~> 0.3.2, >= 0.7.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3784 | LOW3.31 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-15310 | LOW3.31 | pyc 3.12.14-r0 fixed in 3.12.15-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-17084 | LOW3.31 | pyc 3.12.14-r0 fixed in 3.12.15-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-15310 | LOW3.31 | python3 3.12.14-r0 fixed in 3.12.15-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-17084 | LOW3.31 | python3 3.12.14-r0 fixed in 3.12.15-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-33210 | LOW3.28 | json 2.15.1 fixed in ~> 2.15.2.1, ~> 2.17.1.2, >= 2.19.2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-42768 | LOW3.21 | openssl 3.3.7-r0 fixed in 3.3.7-r1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW3.18 | openssl 3.3.7-r0 fixed in 3.3.7-r1 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-35189 | LOW3.15 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.15 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.15 | libssl3 3.3.7-r0 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.15 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54696 | LOW3.15 | json 2.15.1 fixed in >= 2.19.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | LOW3.01 | openssl 3.3.7-r0 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-72897 | LOW3.01 | openssl 3.3.7-r0 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-75805 | LOW3.01 | openssl 3.3.7-r0 fixed in 3.3.7-r2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-77696 | LOW3.01 | openssl 3.3.7-r0 fixed in 3.3.7-r2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.01 | openssl 3.3.7-r0 fixed in 3.3.7-r1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 3.3.7-r0 fixed in 3.3.7-r1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-54906 | LOW3 | concurrent-ruby 1.3.5 fixed in >= 1.3.7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42257 | LOW3 | net-imap 0.4.19 fixed in ~> 0.4.24, ~> 0.5.14, >= 0.6.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42257 | LOW3 | net-imap 0.5.6 fixed in ~> 0.4.24, ~> 0.5.14, >= 0.6.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-27820 | LOW3 | zlib 3.1.1 fixed in ~> 3.0.1, ~> 3.1.2, >= 3.2.3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl 3.3.7-r0 fixed in 3.3.7-r1 | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-41316 | LOW2.92 | erb 4.0.3 fixed in ~> 4.0.3.1, ~> 4.0.4.1, ~> 6.0.1.1, >= 6.0.4 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-41316 | LOW2.92 | erb 5.0.3 fixed in ~> 4.0.3.1, ~> 4.0.4.1, ~> 6.0.1.1, >= 6.0.4 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-87910 | LOW2.91 | pyc 3.12.14-r0 fixed in 3.12.15-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-87910 | LOW2.91 | python3 3.12.14-r0 fixed in 3.12.15-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | openssl 3.3.7-r0 fixed in 3.3.7-r1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-34183 | LOW2.7 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63076 | LOW2.7 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34183 | LOW2.7 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63076 | LOW2.7 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34183 | LOW2.7 | openssl 3.3.7-r0 fixed in 3.3.7-r1 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63076 | LOW2.7 | openssl 3.3.7-r0 fixed in 3.3.7-r1 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-75804 | LOW2.7 | openssl 3.3.7-r0 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-75806 | LOW2.7 | openssl 3.3.7-r0 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-84784 | LOW2.7 | openssl 3.3.7-r0 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-15806 | LOW2.7 | pyc 3.12.14-r0 fixed in 3.12.15-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-19672 | LOW2.7 | pyc 3.12.14-r0 fixed in 3.12.15-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-15806 | LOW2.7 | python3 3.12.14-r0 fixed in 3.12.15-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-19672 | LOW2.7 | python3 3.12.14-r0 fixed in 3.12.15-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW2.66 | libcrypto3 3.3.7-r0 fixed in 3.3.7-r1 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34182 | LOW2.66 | libssl3 3.3.7-r0 fixed in 3.3.7-r1 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34182 | LOW2.66 | openssl 3.3.7-r0 fixed in 3.3.7-r1 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-77214 | LOW2.51 | libexpat 2.8.4-r0 fixed in 2.9.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | LOW2.48 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-92392 | LOW2.48 | curl 8.14.1-r2 fixed in 8.14.1-r3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | LOW2.48 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-19445 | LOW2.48 | pyc 3.12.14-r0 fixed in 3.12.15-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19445 | LOW2.48 | python3 3.12.14-r0 fixed in 3.12.15-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-54875 | LOW2.4 | openssl 3.3.7-r0 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-22184 | LOW2.39 | zlib 1.3.1-r2 fixed in 1.3.2-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-33306 | LOW2.29 | bcrypt 3.1.20 fixed in >= 3.1.22 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42245 | LOW2.29 | net-imap 0.4.19 fixed in ~> 0.4.24, ~> 0.5.14, >= 0.6.4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-42245 | LOW2.29 | net-imap 0.5.6 fixed in ~> 0.4.24, ~> 0.5.14, >= 0.6.4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-61594 | LOW2.29 | uri 0.13.2 fixed in ~> 0.12.5, ~> 0.13.3, >= 1.0.4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-35189 | LOW1.89 | openssl 3.3.7-r0 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW1.89 | openssl 3.3.7-r0 fixed in 3.3.7-r1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-75803 | LOW1.89 | openssl 3.3.7-r0 fixed in 3.3.7-r1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-46394 | LOW1.68 | busybox 1.37.0-r12 fixed in 1.37.0-r14 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-46394 | LOW1.68 | busybox-binsh 1.37.0-r12 fixed in 1.37.0-r14 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-46394 | LOW1.68 | ssl_client 1.37.0-r12 fixed in 1.37.0-r14 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68121 | NONE0 | stdlib v1.24.0 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-45445 | NONE0 | openssl-dev 3.3.7-r0 fixed in 3.3.7-r1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-39821 | NONE0 | stdlib v1.24.0 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-45447 | NONE0 | openssl-dev 3.3.7-r0 fixed in 3.3.7-r1 | 4.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-19445 | NONE0 | python3-pyc 3.12.14-r0 fixed in 3.12.15-r0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-19445 | NONE0 | python3-pycache-pyc0 3.12.14-r0 fixed in 3.12.15-r0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56858 | NONE0 | stdlib v1.24.0 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-40200 | NONE0 | musl-utils 1.2.5-r9 fixed in 1.2.5-r11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39822 | NONE0 | stdlib v1.24.0 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34183 | NONE0 | openssl-dev 3.3.7-r0 fixed in 3.3.7-r1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-63072 | NONE0 | openssl-dev 3.3.7-r0 fixed in 3.3.7-r1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-63076 | NONE0 | openssl-dev 3.3.7-r0 fixed in 3.3.7-r1 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-41493 | NONE0 | yard 0.9.37 fixed in >= 0.9.42 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-22874 | NONE0 | stdlib v1.24.0 fixed in 1.24.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61726 | NONE0 | stdlib v1.24.0 fixed in 1.24.12, 1.25.6 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-61729 | NONE0 | stdlib v1.24.0 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25679 | NONE0 | stdlib v1.24.0 fixed in 1.25.8, 1.26.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.24.0 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32280 | NONE0 | stdlib v1.24.0 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32281 | NONE0 | stdlib v1.24.0 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32283 | NONE0 | stdlib v1.24.0 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33811 | NONE0 | stdlib v1.24.0 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | stdlib v1.24.0 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-33818 | NONE0 | stdlib v1.24.0 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-39820 | NONE0 | stdlib v1.24.0 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39836 | NONE0 | stdlib v1.24.0 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42499 | NONE0 | stdlib v1.24.0 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.24.0 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56853 | NONE0 | stdlib v1.24.0 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56859 | NONE0 | stdlib v1.24.0 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56860 | NONE0 | stdlib v1.24.0 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-56862 | NONE0 | stdlib v1.24.0 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78667 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-78669 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97031 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58183 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61728 | NONE0 | stdlib v1.24.0 fixed in 1.24.12, 1.25.6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-84782 | NONE0 | openssl-dev 3.3.7-r0 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-34182 | NONE0 | openssl-dev 3.3.7-r0 fixed in 3.3.7-r1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-19553 | NONE0 | python3-pyc 3.12.14-r0 fixed in 3.12.15-r0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-19553 | NONE0 | python3-pycache-pyc0 3.12.14-r0 fixed in 3.12.15-r0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-82049 | NONE0 | python3-pyc 3.12.14-r0 fixed in 3.12.15-r0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-82049 | NONE0 | python3-pycache-pyc0 3.12.14-r0 fixed in 3.12.15-r0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-47907 | NONE0 | stdlib v1.24.0 fixed in 1.23.12, 1.24.6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-4673 | NONE0 | stdlib v1.24.0 fixed in 1.23.10, 1.24.4 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-15310 | NONE0 | python3-pyc 3.12.14-r0 fixed in 3.12.15-r0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-17084 | NONE0 | python3-pyc 3.12.14-r0 fixed in 3.12.15-r0 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-15310 | NONE0 | python3-pycache-pyc0 3.12.14-r0 fixed in 3.12.15-r0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-17084 | NONE0 | python3-pycache-pyc0 3.12.14-r0 fixed in 3.12.15-r0 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-47906 | NONE0 | stdlib v1.24.0 fixed in 1.23.12, 1.24.6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61727 | NONE0 | stdlib v1.24.0 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39825 | NONE0 | stdlib v1.24.0 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56866 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94439 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32282 | NONE0 | stdlib v1.24.0 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42768 | NONE0 | openssl-dev 3.3.7-r0 fixed in 3.3.7-r1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-32289 | NONE0 | stdlib v1.24.0 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94448 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-54872 | NONE0 | openssl-dev 3.3.7-r0 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72897 | NONE0 | openssl-dev 3.3.7-r0 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-75805 | NONE0 | openssl-dev 3.3.7-r0 fixed in 3.3.7-r2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-77696 | NONE0 | openssl-dev 3.3.7-r0 fixed in 3.3.7-r2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42770 | NONE0 | openssl-dev 3.3.7-r0 fixed in 3.3.7-r1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63073 | NONE0 | openssl-dev 3.3.7-r0 fixed in 3.3.7-r1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-9076 | NONE0 | openssl-dev 3.3.7-r0 fixed in 3.3.7-r1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97032 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-87910 | NONE0 | python3-pyc 3.12.14-r0 fixed in 3.12.15-r0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-87910 | NONE0 | python3-pycache-pyc0 3.12.14-r0 fixed in 3.12.15-r0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-6042 | NONE0 | musl-utils 1.2.5-r9 fixed in 1.2.5-r10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32288 | NONE0 | stdlib v1.24.0 fixed in 1.25.9, 1.26.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22871 | NONE0 | stdlib v1.24.0 fixed in 1.23.8, 1.24.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-27142 | NONE0 | stdlib v1.24.0 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39823 | NONE0 | stdlib v1.24.0 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39826 | NONE0 | stdlib v1.24.0 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-75804 | NONE0 | openssl-dev 3.3.7-r0 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-75806 | NONE0 | openssl-dev 3.3.7-r0 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-84784 | NONE0 | openssl-dev 3.3.7-r0 fixed in 3.3.7-r2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42766 | NONE0 | openssl-dev 3.3.7-r0 fixed in 3.3.7-r1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-15806 | NONE0 | python3-pyc 3.12.14-r0 fixed in 3.12.15-r0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-19672 | NONE0 | python3-pyc 3.12.14-r0 fixed in 3.12.15-r0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-15806 | NONE0 | python3-pycache-pyc0 3.12.14-r0 fixed in 3.12.15-r0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-19672 | NONE0 | python3-pycache-pyc0 3.12.14-r0 fixed in 3.12.15-r0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-49342 | NONE0 | yard 0.9.37 fixed in >= 0.9.44 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22873 | NONE0 | stdlib v1.24.0 fixed in 1.23.9, 1.24.3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-47912 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58185 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58187 | NONE0 | stdlib v1.24.0 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58189 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61723 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-61724 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61725 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61730 | NONE0 | stdlib v1.24.0 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.24.0 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42507 | NONE0 | stdlib v1.24.0 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-78663 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58186 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-54875 | NONE0 | openssl-dev 3.3.7-r0 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22870 | NONE0 | stdlib v1.24.0 fixed in 1.23.7, 1.24.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-35189 | NONE0 | openssl-dev 3.3.7-r0 fixed in 3.3.7-r2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45446 | NONE0 | openssl-dev 3.3.7-r0 fixed in 3.3.7-r1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-75803 | NONE0 | openssl-dev 3.3.7-r0 fixed in 3.3.7-r1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56857 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-27139 | NONE0 | stdlib v1.24.0 fixed in 1.25.8, 1.26.1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58251 | NONE0 | busybox 1.37.0-r12 fixed in 1.37.0-r14 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58251 | NONE0 | busybox-binsh 1.37.0-r12 fixed in 1.37.0-r14 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-1965_1 | NONE0 | curl 8.14.1-r2 fixed in 8.14.1-r3 | — | Not Applicable |
| CVE-2026-1965_2 | NONE0 | curl 8.14.1-r2 fixed in 8.14.1-r3 | — | Not Applicable |
| CVE-2026-1965_1 | NONE0 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | — | Not Applicable |
| CVE-2026-1965_2 | NONE0 | libcurl 8.14.1-r2 fixed in 8.14.1-r3 | — | Not Applicable |
| CVE-2024-58251 | NONE0 | ssl_client 1.37.0-r12 fixed in 1.37.0-r14 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-85091 | NONE0 | zlib 1.3.1-r2 fixed in 1.3.2-r1 | 0.4% Theoretical Threat | Not Applicable |
| GHSA-6jxj-px6v-747w | NONE0 | crass 1.0.6 fixed in >= 1.0.7 | — | Not Applicable |
| GHSA-6wmf-3r64-vcwv | NONE0 | crass 1.0.6 fixed in >= 1.0.7 | — | Not Applicable |
| GHSA-8vfg-2r28-hvhj | NONE0 | crass 1.0.6 fixed in >= 1.0.7 | — | Not Applicable |
| GHSA-wwpr-jff3-395c | NONE0 | crass 1.0.6 fixed in >= 1.0.7 | — | Not Applicable |
| CVE-2026-67431 | NONE0 | mcp 0.13.0 fixed in >= 0.23.0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-67432 | NONE0 | mcp 0.13.0 fixed in >= 0.23.0 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-63118 | NONE0 | mcp 0.13.0 fixed in >= 0.23.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63119 | NONE0 | mcp 0.13.0 fixed in >= 0.23.0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-67430 | NONE0 | mcp 0.13.0 fixed in >= 0.23.0 | 0.5% Theoretical Threat | Not Applicable |
| GHSA-5prr-v3j2-97mh | NONE0 | nokogiri 1.18.10 fixed in >= 1.19.4 | — | Not Applicable |
| GHSA-5v8h-3h3q-446p | NONE0 | nokogiri 1.18.10 fixed in >= 1.19.4 | — | Not Applicable |
| GHSA-8678-w3jw-xfc2 | NONE0 | nokogiri 1.18.10 fixed in >= 1.19.4 | — | Not Applicable |
| GHSA-9cv2-cfxc-v4v2 | NONE0 | nokogiri 1.18.10 fixed in >= 1.19.4 | — | Not Applicable |
| GHSA-p67v-3w7g-wjg7 | NONE0 | nokogiri 1.18.10 fixed in >= 1.19.4 | — | Not Applicable |
| GHSA-phwj-rprq-35pp | NONE0 | nokogiri 1.18.10 fixed in >= 1.19.4 | — | Not Applicable |
| GHSA-wfpw-mmfh-qq69 | NONE0 | nokogiri 1.18.10 fixed in >= 1.19.4 | — | Not Applicable |
| GHSA-wjv4-x9w8-wm3h | NONE0 | nokogiri 1.18.10 fixed in >= 1.19.4 | — | Not Applicable |
| GHSA-g9g8-vgvw-g3vf | NONE0 | nokogiri 1.18.10 fixed in >= 1.19.4 | — | Not Applicable |
| GHSA-mwm8-39rw-8826 | NONE0 | sqlite3 2.9.4 fixed in >= 2.9.6 | — | Not Applicable |
| CVE-2025-0913 | NONE0 | stdlib v1.24.0 fixed in 1.23.10, 1.24.4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-58188 | NONE0 | stdlib v1.24.0 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.24.0 fixed in 1.26.9, 1.27.2 | 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.