Last scanned:
AI verdict failed due to an error.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2022-23521 | HIGH7.64 | git 2.36.2-r0 fixed in 2.36.4-r0 | 56.3% Actively Exploited | Post-Exploit |
| CVE-2022-41903 | MEDIUM6.76 | git 2.36.2-r0 fixed in 2.36.4-r0 | 44.3% High Exploitation Risk | Post-Exploit |
| CVE-2023-25652 | MEDIUM5.85 | git 2.36.2-r0 fixed in 2.36.6-r0 | 51.9% Actively Exploited | Post-Exploit |
| CVE-2023-0286 | MEDIUM5.77 | openssl 1.1.1q-r0 fixed in 1.1.1t-r0 | 59.5% Actively Exploited | Post-Exploit |
| CVE-2022-39260 | MEDIUM5.28 | git 2.36.2-r0 fixed in 2.36.3-r0 | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-4450 | MEDIUM5.17 | openssl 1.1.1q-r0 fixed in 1.1.1t-r0 | 20.4% High Exploitation Risk | Post-Exploit |
| CVE-2023-2650 | MEDIUM5.07 | openssl 1.1.1q-r0 fixed in 1.1.1u-r0 | 75.1% Actively Exploited | Post-Exploit |
| CVE-2023-29007 | MEDIUM4.68 | git 2.36.2-r0 fixed in 2.36.6-r0 | 6.1% Low-Moderate Risk | Post-Exploit |
| CVE-2023-23946 | MEDIUM4.5 | git 2.36.2-r0 fixed in 2.36.5-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0215 | MEDIUM4.5 | openssl 1.1.1q-r0 fixed in 1.1.1t-r0 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0464 | MEDIUM4.5 | openssl 1.1.1q-r0 fixed in 1.1.1t-r1 | 3.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-4304 | MEDIUM4.07 | openssl 1.1.1q-r0 fixed in 1.1.1t-r0 | 16.2% High Exploitation Risk | Post-Exploit |
| CVE-2022-39253 | LOW3.3 | git 2.36.2-r0 fixed in 2.36.3-r0 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0465 | LOW3.18 | openssl 1.1.1q-r0 fixed in 1.1.1t-r2 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-3446 | LOW3.18 | openssl 1.1.1q-r0 fixed in 1.1.1u-r2 | 6.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-3817 | LOW3.18 | openssl 1.1.1q-r0 fixed in 1.1.1v-r0 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5678 | LOW3.18 | openssl 1.1.1q-r0 fixed in 1.1.1w-r1 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-42366 | LOW2.8 | busybox 1.35.0-r17 fixed in 1.35.0-r18 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-22490 | LOW2.8 | git 2.36.2-r0 fixed in 2.36.5-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-25815 | LOW1.12 | git 2.36.2-r0 fixed in 2.36.6-r0 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-23521 | NONE0 | git-perl 2.36.2-r0 fixed in 2.36.4-r0 | 56.3% Actively Exploited | Not Applicable |
| CVE-2022-41903 | NONE0 | git-perl 2.36.2-r0 fixed in 2.36.4-r0 | 44.3% High Exploitation Risk | Not Applicable |
| CVE-2022-32221 | NONE0 | libcurl 7.83.1-r3 fixed in 7.83.1-r4 | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-38545 | NONE0 | libcurl 7.83.1-r3 fixed in 8.4.0-r0 | 78.5% Actively Exploited | Not Applicable |
| CVE-2022-23521 | NONE0 | perl-git 2.36.2-r0 fixed in 2.36.4-r0 | 56.3% Actively Exploited | Not Applicable |
| CVE-2022-41903 | NONE0 | perl-git 2.36.2-r0 fixed in 2.36.4-r0 | 44.3% High Exploitation Risk | Not Applicable |
| CVE-2023-23914 | NONE0 | libcurl 7.83.1-r3 fixed in 7.83.1-r6 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-39260 | NONE0 | git-perl 2.36.2-r0 fixed in 2.36.3-r0 | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-27533 | NONE0 | libcurl 7.83.1-r3 fixed in 8.0.1-r0 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-27534 | NONE0 | libcurl 7.83.1-r3 fixed in 8.0.1-r0 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-39260 | NONE0 | perl-git 2.36.2-r0 fixed in 2.36.3-r0 | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-42915 | NONE0 | libcurl 7.83.1-r3 fixed in 7.83.1-r4 | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2023-29007 | NONE0 | git-perl 2.36.2-r0 fixed in 2.36.6-r0 | 6.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-2603 | NONE0 | libcap 2.64-r0 fixed in 2.64-r1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-29491 | NONE0 | ncurses-libs 6.3_p20220521-r0 fixed in 6.3_p20220521-r1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-29491 | NONE0 | ncurses-terminfo-base 6.3_p20220521-r0 fixed in 6.3_p20220521-r1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-47038 | NONE0 | perl 5.34.1-r0 fixed in 5.34.2-r0 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-29007 | NONE0 | perl-git 2.36.2-r0 fixed in 2.36.6-r0 | 6.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-43680 | NONE0 | expat 2.4.9-r0 fixed in 2.5.0-r0 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-52425 | NONE0 | expat 2.4.9-r0 fixed in 2.6.0-r0 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2024-28757 | NONE0 | expat 2.4.9-r0 fixed in 2.6.2-r0 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-23946 | NONE0 | git-perl 2.36.2-r0 fixed in 2.36.5-r0 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-25652 | NONE0 | git-perl 2.36.2-r0 fixed in 2.36.6-r0 | 51.9% Actively Exploited | Not Applicable |
| CVE-2022-4450 | NONE0 | libcrypto1.1 1.1.1q-r0 fixed in 1.1.1t-r0 | 20.4% High Exploitation Risk | Not Applicable |
| CVE-2023-0215 | NONE0 | libcrypto1.1 1.1.1q-r0 fixed in 1.1.1t-r0 | 4.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-0464 | NONE0 | libcrypto1.1 1.1.1q-r0 fixed in 1.1.1t-r1 | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-42916 | NONE0 | libcurl 7.83.1-r3 fixed in 7.83.1-r4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-43551 | NONE0 | libcurl 7.83.1-r3 fixed in 7.83.1-r5 | 16.5% High Exploitation Risk | Not Applicable |
| CVE-2023-28319 | NONE0 | libcurl 7.83.1-r3 fixed in 8.1.0-r0 | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-38039 | NONE0 | libcurl 7.83.1-r3 fixed in 8.3.0-r0 | 62.2% Actively Exploited | Not Applicable |
| CVE-2022-4450 | NONE0 | libssl1.1 1.1.1q-r0 fixed in 1.1.1t-r0 | 20.4% High Exploitation Risk | Not Applicable |
| CVE-2023-0215 | NONE0 | libssl1.1 1.1.1q-r0 fixed in 1.1.1t-r0 | 4.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-0464 | NONE0 | libssl1.1 1.1.1q-r0 fixed in 1.1.1t-r1 | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-35945 | NONE0 | nghttp2-libs 1.47.0-r0 fixed in 1.47.0-r1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-44487 | NONE0 | nghttp2-libs 1.47.0-r0 fixed in 1.47.0-r2 | 100.0% Actively Exploited | Not Applicable |
| CVE-2022-41409 | NONE0 | pcre2 10.40-r0 fixed in 10.42-r0 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-23946 | NONE0 | perl-git 2.36.2-r0 fixed in 2.36.5-r0 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-25652 | NONE0 | perl-git 2.36.2-r0 fixed in 2.36.6-r0 | 51.9% Actively Exploited | Not Applicable |
| CVE-2023-0286 | NONE0 | libcrypto1.1 1.1.1q-r0 fixed in 1.1.1t-r0 | 59.5% Actively Exploited | Not Applicable |
| CVE-2023-0286 | NONE0 | libssl1.1 1.1.1q-r0 fixed in 1.1.1t-r0 | 59.5% Actively Exploited | Not Applicable |
| CVE-2025-26519 | NONE0 | musl 1.2.3-r0 fixed in 1.2.3-r4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-26519 | NONE0 | musl-utils 1.2.3-r0 fixed in 1.2.3-r4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-2650 | NONE0 | libcrypto1.1 1.1.1q-r0 fixed in 1.1.1u-r0 | 75.1% Actively Exploited | Not Applicable |
| CVE-2023-23915 | NONE0 | libcurl 7.83.1-r3 fixed in 7.83.1-r6 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-23916 | NONE0 | libcurl 7.83.1-r3 fixed in 7.83.1-r6 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-46218 | NONE0 | libcurl 7.83.1-r3 fixed in 8.5.0-r0 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-2650 | NONE0 | libssl1.1 1.1.1q-r0 fixed in 1.1.1u-r0 | 75.1% Actively Exploited | Not Applicable |
| CVE-2022-4304 | NONE0 | libcrypto1.1 1.1.1q-r0 fixed in 1.1.1t-r0 | 16.2% High Exploitation Risk | Not Applicable |
| CVE-2022-43552 | NONE0 | libcurl 7.83.1-r3 fixed in 7.83.1-r5 | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-27535 | NONE0 | libcurl 7.83.1-r3 fixed in 8.0.1-r0 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-27536 | NONE0 | libcurl 7.83.1-r3 fixed in 8.0.1-r0 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-27537 | NONE0 | libcurl 7.83.1-r3 fixed in 8.0.1-r0 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2023-28320 | NONE0 | libcurl 7.83.1-r3 fixed in 8.1.0-r0 | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-28321 | NONE0 | libcurl 7.83.1-r3 fixed in 8.1.0-r0 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-4304 | NONE0 | libssl1.1 1.1.1q-r0 fixed in 1.1.1t-r0 | 16.2% High Exploitation Risk | Not Applicable |
| CVE-2023-52426 | NONE0 | expat 2.4.9-r0 fixed in 2.6.0-r0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-39253 | NONE0 | git-perl 2.36.2-r0 fixed in 2.36.3-r0 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-22490 | NONE0 | git-perl 2.36.2-r0 fixed in 2.36.5-r0 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-27538 | NONE0 | libcurl 7.83.1-r3 fixed in 8.0.1-r0 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-39253 | NONE0 | perl-git 2.36.2-r0 fixed in 2.36.3-r0 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-22490 | NONE0 | perl-git 2.36.2-r0 fixed in 2.36.5-r0 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-24056 | NONE0 | pkgconf 1.8.0-r1 fixed in 1.8.1-r0 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-42366 | NONE0 | ssl_client 1.35.0-r17 fixed in 1.35.0-r18 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-0465 | NONE0 | libcrypto1.1 1.1.1q-r0 fixed in 1.1.1t-r2 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-3446 | NONE0 | libcrypto1.1 1.1.1q-r0 fixed in 1.1.1u-r2 | 6.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-3817 | NONE0 | libcrypto1.1 1.1.1q-r0 fixed in 1.1.1v-r0 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-5678 | NONE0 | libcrypto1.1 1.1.1q-r0 fixed in 1.1.1w-r1 | 4.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-46219 | NONE0 | libcurl 7.83.1-r3 fixed in 8.5.0-r0 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-0465 | NONE0 | libssl1.1 1.1.1q-r0 fixed in 1.1.1t-r2 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-3446 | NONE0 | libssl1.1 1.1.1q-r0 fixed in 1.1.1u-r2 | 6.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-3817 | NONE0 | libssl1.1 1.1.1q-r0 fixed in 1.1.1v-r0 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-5678 | NONE0 | libssl1.1 1.1.1q-r0 fixed in 1.1.1w-r1 | 4.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-28322 | NONE0 | libcurl 7.83.1-r3 fixed in 8.1.0-r0 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-38546 | NONE0 | libcurl 7.83.1-r3 fixed in 8.4.0-r0 | 6.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-2602 | NONE0 | libcap 2.64-r0 fixed in 2.64-r1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-25815 | NONE0 | git-perl 2.36.2-r0 fixed in 2.36.6-r0 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-25815 | NONE0 | perl-git 2.36.2-r0 fixed in 2.36.6-r0 | 1.0% 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.
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.