Last scanned:
This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker could remotely execute arbitrary code on the server via crafted TLS handshake (CVE-2026-34875) or malicious XML input (CVE-2026-6653), and perform HTTP request smuggling (CVE-2025-58068) to bypass security controls or poison caches. The image contains 331 known vulnerabilities in its exposed surface, with 16 rated high or critical severity. Additionally, the image is from an unverified community publisher with very low download count, further increasing risk.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-34875 | HIGH8.33 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-6653 | HIGH8.33 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2025-58068 | HIGH7.73 | eventlet 0.37.0 fixed in 0.40.3 | 0.4% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-36691 | HIGH7.5 | libjxl0.11 0.11.2-0.1~deb13u2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34069 | HIGH7.5 | Werkzeug 2.3.8 fixed in 3.0.3 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-49767 | HIGH7.5 | Werkzeug 2.3.8 fixed in 3.0.6 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-49769 | HIGH7.5 | waitress 2.1.2 fixed in 3.0.1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12797 | HIGH7.4 | cryptography 43.0.3 fixed in 44.0.1 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | HIGH7.1 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | — | Directly Exposed |
| CVE-2016-9580 | HIGH7.04 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2016-9581 | HIGH7.04 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2018-16376 | HIGH7.04 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-58010 | MEDIUM6.97 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-37555 | MEDIUM6.97 | libsndfile1 1.2.2-2+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0966 | MEDIUM6.97 | libssh-4 0.11.2-1+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34873 | MEDIUM6.8 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-15370 | MEDIUM6.7 | libssh-4 0.11.2-1+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | libexpat1 2.7.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8176 | MEDIUM6.63 | libtiff6 4.7.0-3+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8177 | MEDIUM6.63 | libtiff6 4.7.0-3+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | MEDIUM6.63 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-9937 | MEDIUM6.5 | libjbig0 2.1-6.1+b2 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2016-10505 | MEDIUM6.5 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9115 | MEDIUM6.5 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9116 | MEDIUM6.5 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9117 | MEDIUM6.5 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6988 | MEDIUM6.5 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-59843 | MEDIUM6.5 | libssh-4 0.11.2-1+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-59844 | MEDIUM6.5 | libssh-4 0.11.2-1+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2018-10126 | MEDIUM6.5 | libtiff6 4.7.0-3+deb13u2 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1210 | MEDIUM6.5 | libtiff6 4.7.0-3+deb13u2 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56208 | MEDIUM6.46 | libaom3 3.12.1-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45186 | MEDIUM6.38 | libexpat1 2.7.1-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34872 | MEDIUM6.38 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-1000520 | MEDIUM6.38 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-3731 | MEDIUM6.38 | libssh-4 0.11.2-1+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | Markdown 3.7 fixed in 3.8.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32597 | MEDIUM6.38 | PyJWT 2.10.1 fixed in 2.12.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-6866 | MEDIUM6.38 | flask-cors 5.0.1 fixed in 6.0.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-48526 | MEDIUM6.29 | PyJWT 2.10.1 fixed in 2.13.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12912 | MEDIUM6.21 | libtiff6 4.7.0-3+deb13u2 fixed in 4.7.0-3+deb13u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | MEDIUM6.21 | libtiff6 4.7.0-3+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl1 2.3.2-2+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56209 | MEDIUM6.03 | libaom3 3.12.1-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56210 | MEDIUM6.03 | libaom3 3.12.1-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56211 | MEDIUM6.03 | libaom3 3.12.1-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5673 | MEDIUM6.03 | libtheoradec1 1.2.0~alpha1+dfsg-6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5673 | MEDIUM6.03 | libtheoraenc1 1.2.0~alpha1+dfsg-6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20796 | MEDIUM6 | libc-bin 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2018-20796 | MEDIUM6 | libc6 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2016-9113 | MEDIUM6 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 3.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2016-9114 | MEDIUM6 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 3.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-16232 | MEDIUM6 | libtiff6 4.7.0-3+deb13u2 No fix yet | 4.8% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2024-26461 | MEDIUM5.9 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-59847 | MEDIUM5.9 | libssh-4 0.11.2-1+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM5.87 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM5.87 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56410 | MEDIUM5.87 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56411 | MEDIUM5.87 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25834 | MEDIUM5.52 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-39329 | MEDIUM5.52 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-37769 | MEDIUM5.52 | libpixman-1-0 0.44.0-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-50613 | MEDIUM5.52 | libsndfile1 1.2.2-2+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-26007 | MEDIUM5.52 | cryptography 43.0.3 fixed in 46.0.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl1 2.3.2-2+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0964 | MEDIUM5.35 | libssh-4 0.11.2-1+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | libexpat1 2.7.1-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-59845 | MEDIUM5.3 | libssh-4 0.11.2-1+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-59848 | MEDIUM5.3 | libssh-4 0.11.2-1+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.25.5-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | libexpat1 2.7.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | MEDIUM5.02 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-66442 | MEDIUM5.02 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48524 | MEDIUM5.02 | PyJWT 2.10.1 fixed in 2.13.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-52584 | MEDIUM5 | libjxl0.11 0.11.2-0.1~deb13u2 No fix yet | — | Directly Exposed |
| CVE-2024-35195 | MEDIUM4.76 | requests 2.31.0 fixed in 2.32.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.7.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | libexpat1 2.7.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-39328 | MEDIUM4.67 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng16-16t64 1.6.48-1+deb13u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0967 | MEDIUM4.67 | libssh-4 0.11.2-1+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-61143 | MEDIUM4.67 | libtiff6 4.7.0-3+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25645 | MEDIUM4.67 | requests 2.31.0 fixed in 2.33.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25645 | MEDIUM4.67 | requests 2.32.3 fixed in 2.33.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48523 | MEDIUM4.59 | PyJWT 2.10.1 fixed in 2.13.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30999 | MEDIUM4.5 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-30999 | MEDIUM4.5 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-30999 | MEDIUM4.5 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-30999 | MEDIUM4.5 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-30999 | MEDIUM4.5 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-30999 | MEDIUM4.5 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | MEDIUM4.5 | libpng16-16t64 1.6.48-1+deb13u5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30999 | MEDIUM4.5 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-30999 | MEDIUM4.5 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-30999 | MEDIUM4.5 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libuuid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48525 | MEDIUM4.5 | PyJWT 2.10.1 fixed in 2.13.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49766 | MEDIUM4.5 | Werkzeug 2.3.8 fixed in 3.0.6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-66221 | MEDIUM4.5 | Werkzeug 2.3.8 fixed in 3.1.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-21860 | MEDIUM4.5 | Werkzeug 2.3.8 fixed in 3.1.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27199 | MEDIUM4.5 | Werkzeug 2.3.8 fixed in 3.1.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34073 | MEDIUM4.5 | cryptography 43.0.3 fixed in 46.0.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-6839 | MEDIUM4.5 | flask-cors 5.0.1 fixed in 6.0.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-47081 | MEDIUM4.5 | requests 2.31.0 fixed in 2.32.4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-47081 | MEDIUM4.5 | requests 2.32.3 fixed in 2.32.4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-59850 | MEDIUM4.3 | libssh-4 0.11.2-1+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-61145 | MEDIUM4.25 | libtiff6 4.7.0-3+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49768 | MEDIUM4.08 | waitress 2.1.2 fixed in 3.0.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-48962 | LOW3.98 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59846 | LOW3.9 | libssh-4 0.11.2-1+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2011-3374 | LOW3.7 | libapt-pkg7.0 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39327 | LOW3.65 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27205 | LOW3.65 | Flask 2.2.5 fixed in 3.1.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27205 | LOW3.65 | Flask 3.1.1 fixed in 3.1.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2005-2541 | LOW3.6 | tar 1.35+dfsg-3.1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-48522 | LOW3.57 | PyJWT 2.10.1 fixed in 2.13.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | perl-base 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-bin 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-41080 | LOW3.15 | libexpat1 2.7.1-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59849 | LOW3.1 | libssh-4 0.11.2-1+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-57432 | LOW3.02 | perl-base 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6357 | LOW2.96 | pip 25.0.1 fixed in 26.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.35+dfsg-3.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8643 | LOW2.8 | pip 25.0.1 fixed in 26.1.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-70873 | LOW2.8 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0965 | LOW2.8 | libssh-4 0.11.2-1+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | LOW2.78 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW2.78 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2018-5709 | LOW2.7 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2018-5709 | LOW2.7 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2018-5709 | LOW2.7 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | bsdutils 1: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.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | mount 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.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 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.4% Theoretical Threat | Post-Exploit |
| CVE-2025-8869 | LOW2.7 | pip 25.0.1 fixed in 25.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-0968 | LOW2.63 | libssh-4 0.11.2-1+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48959 | LOW2.55 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3219 | LOW2.55 | pip 25.0.1 fixed in 26.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.17.4-2 No fix yet | 0.9% 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.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.13-1 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-2026-41992 | LOW2.29 | gzip 1.13-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW2.29 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW2.29 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.7-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-24515 | LOW2.12 | libexpat1 2.7.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8534 | LOW2.12 | libtiff6 4.7.0-3+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | LOW1.99 | perl-base 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-1703 | LOW1.99 | pip 25.0.1 fixed in 26.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-1365 | NONE0 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1372 | NONE0 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-1352 | NONE0 | libelf1t64 0.192-4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-0856 | NONE0 | libcaca0 0.99.beta20-5+deb13u1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2018-18064 | NONE0 | libcairo-gobject2 1.18.4-1+b1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-18064 | NONE0 | libcairo2 1.18.4-1+b1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-54371 | NONE0 | libattr1 1:2.5.2-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libblkid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libsmartcols1 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-7475 | NONE0 | libcairo-gobject2 1.18.4-1+b1 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-7475 | NONE0 | libcairo2 1.18.4-1+b1 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2025-1371 | NONE0 | libelf1t64 0.192-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1377 | NONE0 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-14330 | NONE0 | libpulse0 17.0+dfsg1-2+b1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23679 | NONE0 | libusb-1.0-0 2:1.0.28-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-47104 | NONE0 | libusb-1.0-0 2:1.0.28-1 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.4% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libblkid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libmount1 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libsmartcols1 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | login 1:4.16.0-2+really2.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.4% Theoretical Threat | Not Applicable |
| CVE-2007-5686 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.7.0-5 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-2025-1376 | NONE0 | libelf1t64 0.192-4 No fix yet | 0.3% 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 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-25068 | NONE0 | libasound2-data 1.2.14-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25068 | NONE0 | libasound2t64 1.2.14-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-25260 | NONE0 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-7883 | NONE0 | libllvm19 1:19.1.7-3+b1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-50422 | NONE0 | libcairo-gobject2 1.18.4-1+b1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-50422 | NONE0 | libcairo2 1.18.4-1+b1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-13573 | NONE0 | libllvm19 1:19.1.7-3+b1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-13574 | NONE0 | libllvm19 1:19.1.7-3+b1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.5+20250216-2 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-53615 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53910 | NONE0 | diffutils 1:3.10-4 No fix yet | — | Not Applicable |
| CVE-2026-13858 | NONE0 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64830 | NONE0 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64831 | NONE0 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64832 | NONE0 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64833 | NONE0 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64834 | NONE0 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64835 | NONE0 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65703 | NONE0 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65704 | NONE0 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65705 | NONE0 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65706 | NONE0 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-56109 | NONE0 | libasound2-data 1.2.14-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56109 | NONE0 | libasound2t64 1.2.14-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-13858 | NONE0 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64830 | NONE0 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64831 | NONE0 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64832 | NONE0 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64833 | NONE0 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64834 | NONE0 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64835 | NONE0 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65703 | NONE0 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65704 | NONE0 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65705 | NONE0 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65706 | NONE0 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-13858 | NONE0 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64830 | NONE0 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64831 | NONE0 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64832 | NONE0 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64833 | NONE0 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64834 | NONE0 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64835 | NONE0 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65703 | NONE0 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65704 | NONE0 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65705 | NONE0 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65706 | NONE0 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-13858 | NONE0 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64830 | NONE0 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64831 | NONE0 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64832 | NONE0 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64833 | NONE0 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64834 | NONE0 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64835 | NONE0 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65703 | NONE0 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65704 | NONE0 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65705 | NONE0 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65706 | NONE0 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-13858 | NONE0 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64830 | NONE0 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64831 | NONE0 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64832 | NONE0 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64833 | NONE0 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64834 | NONE0 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64835 | NONE0 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65703 | NONE0 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65704 | NONE0 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65705 | NONE0 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65706 | NONE0 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-13858 | NONE0 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64830 | NONE0 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64831 | NONE0 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64832 | NONE0 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64833 | NONE0 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64834 | NONE0 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64835 | NONE0 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65703 | NONE0 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65704 | NONE0 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65705 | NONE0 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65706 | NONE0 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-56131 | NONE0 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56407 | NONE0 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56408 | NONE0 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56409 | NONE0 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-45913 | NONE0 | libgbm1 25.0.7-2+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libgbm1 25.0.7-2+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libgbm1 25.0.7-2+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libgbm1 25.0.7-2+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45924 | NONE0 | libgl1 1.7.0-1+b2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45913 | NONE0 | libgl1-mesa-dri 25.0.7-2+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libgl1-mesa-dri 25.0.7-2+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libgl1-mesa-dri 25.0.7-2+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libgl1-mesa-dri 25.0.7-2+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45924 | NONE0 | libglvnd0 1.7.0-1+b2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45913 | NONE0 | libglx-mesa0 25.0.7-2+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libglx-mesa0 25.0.7-2+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libglx-mesa0 25.0.7-2+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libglx-mesa0 25.0.7-2+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45924 | NONE0 | libglx0 1.7.0-1+b2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2025-29070 | NONE0 | liblcms2-2 2.16-2+deb13u2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-25835 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25833 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34871 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34877 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25832 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34874 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34876 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-35336 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-49300 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-50579 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-50580 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-50581 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-50583 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-50584 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-50585 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-50586 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-50587 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-50588 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-50640 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-50713 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-54435 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-54441 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-13858 | NONE0 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64830 | NONE0 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64831 | NONE0 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64832 | NONE0 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64833 | NONE0 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64834 | NONE0 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64835 | NONE0 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65703 | NONE0 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65704 | NONE0 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65705 | NONE0 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65706 | NONE0 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2023-45927 | NONE0 | libslang2 2.3.3-5+b2 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-45929 | NONE0 | libslang2 2.3.3-5+b2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55868 | NONE0 | libsrt1.5-gnutls 1.5.4-1 No fix yet | — | Not Applicable |
| CVE-2026-55869 | NONE0 | libsrt1.5-gnutls 1.5.4-1 No fix yet | — | Not Applicable |
| CVE-2026-13858 | NONE0 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64830 | NONE0 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64831 | NONE0 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64832 | NONE0 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64833 | NONE0 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64834 | NONE0 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64835 | NONE0 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65703 | NONE0 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65704 | NONE0 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65705 | NONE0 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65706 | NONE0 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-13858 | NONE0 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64830 | NONE0 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64831 | NONE0 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64832 | NONE0 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64833 | NONE0 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64834 | NONE0 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-64835 | NONE0 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65703 | NONE0 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65704 | NONE0 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65705 | NONE0 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-65706 | NONE0 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiff6 4.7.0-3+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2025-25467 | NONE0 | libx264-164 2:0.164.3108+git31e19f9-2+b1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login.defs 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2023-45913 | NONE0 | mesa-libgallium 25.0.7-2+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | mesa-libgallium 25.0.7-2+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | mesa-libgallium 25.0.7-2+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | mesa-libgallium 25.0.7-2+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-53615 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-57433 | 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 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | 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 |
| CVE-2026-53615 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| GHSA-537c-gmf6-5ccf | NONE0 | cryptography 43.0.3 fixed in 48.0.1 | — | Not Applicable |
| CVE-2024-6844 | NONE0 | flask-cors 5.0.1 fixed in 6.0.0 | 0.3% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.