This image is safe for production use. While 37 post-exploit vulnerabilities were identified, none are exposed on the attack surface of the running container. The highest severity post-exploit finding is CVE-2005-2541, rated at 3.6, concerning the `tar` utility. Exploitation of CVE-2005-2541 requires an attacker to first place and then induce the extraction of a malicious archive within the container, which is considered a low contextual risk given the container's primary role of running python3.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2005-2541 | LOW3.6 | tar 1.35+dfsg-3.1 No fix yet | 3.8% Low-Moderate Risk | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.35+dfsg-3.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.17.4-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.7-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.7-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 3.0.3 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-56433 | LOW2.16 | passwd 1:4.17.4-2 No fix yet | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-8376 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-42496 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23949 | NONE0 | jaraco.context 5.3.0 fixed in 6.1.0 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48962 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2018-20796 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2018-20796 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42497 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-9538 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-6238 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libblkid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | liblastlog2-2 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libmount1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libsmartcols1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libuuid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6357 | NONE0 | pip 24.0 fixed in 26.1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libblkid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | liblastlog2-2 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libmount1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libsmartcols1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libuuid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27171 | NONE0 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-24049 | NONE0 | wheel 0.45.1 fixed in 0.46.2 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libblkid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | liblastlog2-2 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34743 | NONE0 | liblzma5 5.8.1-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libmount1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libsmartcols1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libuuid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-8869 | NONE0 | pip 24.0 fixed in 25.3 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42250 | NONE0 | libbz2-1.0 1.0.8-6 No fix yet | — | Not Applicable |
| CVE-2026-5450 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3219 | NONE0 | pip 24.0 fixed in 26.1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2007-5686 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libblkid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | liblastlog2-2 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libmount1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libsmartcols1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libuuid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2021-45346 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2010-4756 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2010-4756 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-1703 | NONE0 | pip 24.0 fixed in 26.0 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2011-3374 | NONE0 | libapt-pkg7.0 3.0.3 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-56433 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 4.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-70873 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libsystemd0 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libsystemd0 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2011-4116 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.37-2+b9 No fix yet | — | Not Applicable |
| CVE-2026-34180 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34181 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34182 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34183 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42764 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42766 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42767 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42768 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42769 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42770 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45445 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45446 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45447 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-7383 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-9076 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login.defs 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-34180 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34181 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34182 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34183 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42764 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42766 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42767 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42768 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42769 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42770 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45445 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45446 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45447 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-7383 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-9076 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34180 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34181 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34182 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34183 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42764 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42766 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42767 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42768 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42769 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42770 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45445 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45446 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45447 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-7383 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-9076 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-48959 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2025-15649 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-48961 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 3.14-4 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.35+dfsg-3.1 No fix yet | — | Not Applicable |