python-aiohttp (v14) 3.13.5
python-aiohttp (v13) 3.13.5 |
| CVE-2026-34993 |
|
score: 6.4 |
Medium |
| CVE-2026-47265 |
|
score: 6.6 |
Medium |
| CVE-2026-50269 |
|
score: 2.7 |
Low |
| CVE-2026-54273 |
|
score: 6.6 |
Medium |
| CVE-2026-54274 |
|
score: 6.6 |
Medium |
| CVE-2026-54275 |
|
score: 2.7 |
Low |
| CVE-2026-54276 |
|
score: 6.3 |
Medium |
| CVE-2026-54277 |
|
score: 6.6 |
Medium |
| CVE-2026-54278 |
|
score: 6.6 |
Medium |
| CVE-2026-54279 |
|
score: 1.3 |
Low |
| CVE-2026-54280 |
|
score: 1.7 |
Low |
| mbedtls3 (std) 3.6.5 |
| CVE-2025-66442 |
|
score: 5.1 |
Medium |
| CVE-2026-25835 |
|
score: 7.7 |
High |
| CVE-2026-34871 |
|
score: 6.7 |
Medium |
| CVE-2026-34872 |
|
score: 9.1 |
Critical |
| CVE-2026-34877 |
|
score: 9.8 |
Critical |
| mupdf (std) 1.27.2 |
| CVE-2026-7233 |
|
score: 1.9 |
Low |
| audiofile (std) 0.3.6 |
| CVE-2017-6827 |
|
score: 7.8 |
High |
| CVE-2017-6828 |
|
score: 7.8 |
High |
| CVE-2017-6829 |
|
score: 5.5 |
Medium |
| CVE-2017-6830 |
|
score: 5.5 |
Medium |
| CVE-2017-6831 |
|
score: 5.5 |
Medium |
| CVE-2017-6832 |
|
score: 5.5 |
Medium |
| CVE-2017-6833 |
|
score: 5.5 |
Medium |
| CVE-2017-6834 |
|
score: 5.5 |
Medium |
| CVE-2017-6835 |
|
score: 5.5 |
Medium |
| CVE-2017-6836 |
|
score: 5.5 |
Medium |
| CVE-2017-6837 |
|
score: 5.5 |
Medium |
| CVE-2017-6838 |
|
score: 5.5 |
Medium |
| CVE-2017-6839 |
|
score: 5.5 |
Medium |
| CVE-2018-13440 |
|
score: 6.5 |
Medium |
| CVE-2018-17095 |
|
score: 8.8 |
High |
| CVE-2019-13147 |
|
score: 6.5 |
Medium |
| CVE-2020-18781 |
|
score: 5.5 |
Medium |
| CVE-2022-24599 |
|
score: 6.5 |
Medium |
| avahi (std) 0.8 |
| CVE-2021-26720 |
|
score: 7.8 |
High |
| CVE-2021-3468 |
|
score: 5.5 |
Medium |
| CVE-2023-38469 |
|
score: 6.2 |
Medium |
| CVE-2023-38470 |
|
score: 6.2 |
Medium |
| CVE-2023-38471 |
|
score: 6.2 |
Medium |
| CVE-2023-38472 |
|
score: 6.2 |
Medium |
| CVE-2023-38473 |
|
score: 6.2 |
Medium |
| CVE-2025-59529 |
|
score: 5.5 |
Medium |
| CVE-2025-68276 |
|
score: 5.5 |
Medium |
| CVE-2025-68468 |
|
score: 6.5 |
Medium |
| CVE-2025-68471 |
|
score: 6.5 |
Medium |
| CVE-2026-24401 |
|
score: 6.5 |
Medium |
| CVE-2026-34933 |
|
score: 5.5 |
Medium |
| cryptopp (std) 8.9.0 |
| CVE-2023-50979 |
|
score: 5.9 |
Medium |
| CVE-2023-50980 |
|
score: 7.5 |
High |
| CVE-2023-50981 |
|
score: 7.5 |
High |
| ffmpeg8 (std) 8.1.3 |
| CVE-2025-25468 |
|
score: 6.5 |
Medium |
| CVE-2025-25469 |
|
score: 6.5 |
Medium |
| CVE-2026-107675 |
|
score: 6.0 |
Medium |
| CVE-2026-107676 |
|
score: 4.8 |
Medium |
| CVE-2026-107677 |
|
score: 5.7 |
Medium |
| CVE-2026-107678 |
|
score: 5.7 |
Medium |
| CVE-2026-107696 |
|
score: 7.1 |
High |
| CVE-2026-52295 |
|
score: 2.9 |
Low |
| CVE-2026-52296 |
|
score: 2.9 |
Low |
| CVE-2026-52297 |
|
score: 2.9 |
Low |
| CVE-2026-70628 |
|
score: 8.5 |
High |
| CVE-2026-70629 |
|
score: 6.8 |
Medium |
| CVE-2026-70630 |
|
score: 6.8 |
Medium |
| CVE-2026-70631 |
|
score: 6.8 |
Medium |
| CVE-2026-70632 |
|
score: 8.5 |
High |
| CVE-2026-96611 |
|
score: 6.9 |
Medium |
| ffmpeg (std) 9.0.2 |
| CVE-2025-25468 |
|
score: 6.5 |
Medium |
| CVE-2025-25469 |
|
score: 6.5 |
Medium |
| CVE-2026-107675 |
|
score: 6.0 |
Medium |
| CVE-2026-107676 |
|
score: 4.8 |
Medium |
| CVE-2026-107677 |
|
score: 5.7 |
Medium |
| CVE-2026-107678 |
|
score: 5.7 |
Medium |
| CVE-2026-107696 |
|
score: 7.1 |
High |
| fontforge (std) 20251009 |
| CVE-2025-15276 |
|
score: 7.8 |
High |
| CVE-2025-15277 |
|
score: 7.8 |
High |
| CVE-2025-15278 |
|
score: 7.8 |
High |
| CVE-2025-15279 |
|
score: 7.8 |
High |
| freeimage (std) 3.18.0 |
| CVE-2019-12211 |
|
score: 7.5 |
High |
| CVE-2019-12212 |
|
score: 7.5 |
High |
| CVE-2019-12213 |
|
score: 6.5 |
Medium |
| CVE-2019-12214 |
|
score: 7.5 |
High |
| CVE-2020-21426 |
|
score: 7.8 |
High |
| CVE-2020-21427 |
|
score: 7.8 |
High |
| CVE-2020-21428 |
|
score: 7.8 |
High |
| CVE-2021-33367 |
|
score: 5.5 |
Medium |
| CVE-2023-47992 |
|
score: 8.8 |
High |
| CVE-2023-47993 |
|
score: 6.5 |
Medium |
| CVE-2023-47994 |
|
score: 8.8 |
High |
| CVE-2023-47995 |
|
score: 6.5 |
Medium |
| CVE-2023-47996 |
|
score: 6.5 |
Medium |
| CVE-2023-47997 |
|
score: 6.5 |
Medium |
| CVE-2024-31570 |
|
score: 9.8 |
Critical |
| CVE-2025-65803 |
|
score: 6.5 |
Medium |
| CVE-2025-70968 |
|
score: 9.8 |
Critical |
| gimp2 (std) 2.10.38 |
| CVE-2025-2760 |
|
score: 7.8 |
High |
| CVE-2025-2761 |
|
score: 7.8 |
High |
| CVE-2025-5473 |
|
score: 8.8 |
High |
| CVE-2026-58381 |
|
score: 6.1 |
Medium |
| CVE-2026-79902 |
|
score: 5.5 |
Medium |
| CVE-2026-80101 |
|
score: 4.4 |
Medium |
| CVE-2026-82324 |
|
score: 6.1 |
Medium |
| CVE-2026-82328 |
|
score: 6.1 |
Medium |
| CVE-2026-82330 |
|
score: 6.1 |
Medium |
| CVE-2026-82343 |
|
score: 6.1 |
Medium |
| gimp (std) 3.2.6 |
| CVE-2026-59089 |
|
score: 5.5 |
Medium |
| CVE-2026-59091 |
|
score: 7.3 |
High |
| CVE-2026-66757 |
|
score: 5.5 |
Medium |
| CVE-2026-78475 |
|
score: 6.1 |
Medium |
| CVE-2026-79902 |
|
score: 5.5 |
Medium |
| CVE-2026-80101 |
|
score: 4.4 |
Medium |
| CVE-2026-82324 |
|
score: 6.1 |
Medium |
| CVE-2026-82328 |
|
score: 6.1 |
Medium |
| CVE-2026-82330 |
|
score: 6.1 |
Medium |
| CVE-2026-82343 |
|
score: 6.1 |
Medium |
| dia (std) 0.97.3 |
| CVE-2019-19451 |
|
score: 5.5 |
Medium |
| gtk2 (std) 2.24.33 |
| CVE-2014-1949 |
|
score: 7.2 |
High |
| libsoup-2.4 (std) 2.74.3 |
| CVE-2024-52530 |
|
score: 7.5 |
High |
| CVE-2024-52531 |
|
score: 6.5 |
Medium |
| CVE-2024-52532 |
|
score: 7.5 |
High |
| CVE-2025-2784 |
|
score: 7.0 |
High |
| CVE-2026-102555 |
|
score: 8.2 |
High |
| CVE-2026-102556 |
|
score: 8.6 |
High |
| CVE-2026-102557 |
|
score: 8.6 |
High |
| CVE-2026-102558 |
|
score: 8.6 |
High |
gnatcross-binutils (FARM64_R11) 2.47
gnatcross-binutils (FAMD64_R12) 2.47
gnatcross-binutils (FI386_R12) 2.47
gnatcross-binutils (OMNIOS) 2.47
gnatcross-binutils (NAMD64_R9) 2.47
gnatcross-binutils (MAMD64_R3) 2.47
gnatcross-binutils (MI386_R3) 2.47
binutils (std) 2.47 |
| CVE-2026-90801 |
|
score: 1.9 |
Low |
| CVE-2026-90802 |
|
score: 1.9 |
Low |
| CVE-2026-90803 |
|
score: 1.9 |
Low |
| CVE-2026-90804 |
|
score: 0.9 |
Low |
| CVE-2026-90828 |
|
score: 1.9 |
Low |
| CVE-2026-90829 |
|
score: 1.9 |
Low |
| CVE-2026-90830 |
|
score: 1.9 |
Low |
| CVE-2026-90831 |
|
score: 1.9 |
Low |
| CVE-2026-91779 |
|
score: 1.9 |
Low |
| CVE-2026-91780 |
|
score: 1.9 |
Low |
| CVE-2026-91781 |
|
score: 1.9 |
Low |
| CVE-2026-91782 |
|
score: 1.9 |
Low |
| bison (std) 3.8.2 |
| CVE-2026-56389 |
|
score: 6.8 |
Medium |
| CVE-2026-56390 |
|
score: 4.6 |
Medium |
coreutils (std) 9.12
coreutils (noprefix) 9.12
coreutils (ravensys) 9.12 |
| CVE-2016-2781 |
|
score: 4.6 |
Medium |
emacs (std) 31.1
emacs (desktop) 31.1 |
| CVE-2007-6109 |
|
score: 10.0 |
Critical |
| gcc14 (std) 14.4.0 |
| CVE-2023-4039 |
|
score: 4.8 |
Medium |
| gcc15 (std) 15.3.0 |
| CVE-2023-4039 |
|
score: 4.8 |
Medium |
patch (std) 2.8
patch (noprefix) 2.8 |
| CVE-2026-56288 |
|
score: 4.6 |
Medium |
| CVE-2026-56289 |
|
score: 4.6 |
Medium |
tar (std) 1.35
tar (noprefix) 1.35 |
| CVE-2026-18477 |
|
score: 4.4 |
Medium |
| CVE-2026-18508 |
|
score: 4.4 |
Medium |
| wget (std) 1.25.0 |
| CVE-2026-58469 |
|
score: 8.7 |
High |
| CVE-2026-58470 |
|
score: 6.9 |
Medium |
| CVE-2026-58471 |
|
score: 6.0 |
Medium |
| CVE-2026-58472 |
|
score: 6.0 |
Medium |
| protobuf321 (std) 21.12 |
| CVE-2026-0994 |
|
score: 8.2 |
High |
| GraphicsMagick (std) 1.3.48 |
| CVE-2007-0770 |
|
score: 9.3 |
Critical |
| CVE-2008-6621 |
|
score: 7.8 |
High |
| tidy (std) 5.8.0 |
| CVE-2025-6498 |
|
score: 1.9 |
Low |
| id3lib (std) 3.8.3 |
| CVE-2007-4460 |
|
score: 7.2 |
High |
ImageMagick (std) 7.1.2-32
ImageMagick (x11) 7.1.2-32 |
| CVE-2017-5506 |
|
score: 7.8 |
High |
| sdl1_ttf (std) 2.0.11 |
| CVE-2022-27470 |
|
score: 7.8 |
High |
| sdl1 (std) 1.2.15 |
| CVE-2019-13616 |
|
score: 8.1 |
High |
| CVE-2019-14906 |
|
score: 9.8 |
Critical |
| CVE-2019-7572 |
|
score: 8.8 |
High |
| CVE-2019-7573 |
|
score: 8.8 |
High |
| CVE-2019-7574 |
|
score: 8.8 |
High |
| CVE-2019-7575 |
|
score: 8.8 |
High |
| CVE-2019-7576 |
|
score: 8.8 |
High |
| CVE-2019-7577 |
|
score: 8.8 |
High |
| CVE-2019-7578 |
|
score: 8.1 |
High |
| CVE-2019-7635 |
|
score: 8.1 |
High |
| CVE-2019-7636 |
|
score: 8.1 |
High |
| CVE-2019-7637 |
|
score: 8.8 |
High |
| CVE-2019-7638 |
|
score: 8.8 |
High |
| CVE-2022-34568 |
|
score: 7.5 |
High |
| libsndfile (std) 1.2.2 |
| CVE-2024-50612 |
|
score: 5.5 |
Medium |
| CVE-2024-50613 |
|
score: 6.5 |
Medium |
| CVE-2025-52194 |
|
score: 7.5 |
High |
| CVE-2025-56226 |
|
score: 5.3 |
Medium |
| CVE-2026-37555 |
|
score: 7.5 |
High |
libssh2 (std) 1.11.1
libssh2 (embed) 1.11.1 |
| CVE-2025-15661 |
|
score: 8.3 |
High |
| CVE-2026-55199 |
|
score: 8.2 |
High |
| CVE-2026-55200 |
|
score: 9.2 |
Critical |
| CVE-2026-58050 |
|
score: 8.3 |
High |
| CVE-2026-58051 |
|
score: 8.3 |
High |
| CVE-2026-66032 |
|
score: 8.7 |
High |
| CVE-2026-66033 |
|
score: 8.7 |
High |
| CVE-2026-66034 |
|
score: 7.7 |
High |
| CVE-2026-66035 |
|
score: 7.7 |
High |
| CVE-2026-7598 |
|
score: 6.9 |
Medium |
libvips (std) 8.18.7
libvips (loaded) 8.18.7 |
| CVE-2026-2913 |
|
score: 1.1 |
Low |
| lua51 (std) 5.1.5 |
| CVE-2014-5461 |
|
score: 5.0 |
Medium |
| CVE-2021-43519 |
|
score: 5.5 |
Medium |
| lua52 (std) 5.2.4 |
| CVE-2021-43519 |
|
score: 5.5 |
Medium |
| lua53 (std) 5.3.6 |
| CVE-2020-15945 |
|
score: 5.5 |
Medium |
| luajit-openresty (std) 2.1-20260914 |
| CVE-2024-25176 |
|
score: 9.8 |
Critical |
| CVE-2024-25177 |
|
score: 7.5 |
High |
| CVE-2024-25178 |
|
score: 9.1 |
Critical |
| mariadb1011 (std) 10.11.19 |
| CVE-2026-35549 |
|
score: 6.5 |
Medium |
| firefox (std) 153.0.1 |
| CVE-2003-1492 |
|
score: 5.0 |
Medium |
| CVE-2007-0896 |
|
score: 4.3 |
Medium |
| CVE-2007-1970 |
|
score: 5.0 |
Medium |
| CVE-2007-2176 |
|
score: 10.0 |
Critical |
| CVE-2007-3670 |
|
score: 4.3 |
Medium |
| CVE-2007-3827 |
|
score: 5.0 |
Medium |
| CVE-2007-4013 |
|
score: 9.3 |
Critical |
| CVE-2007-6715 |
|
score: 4.3 |
Medium |
| CVE-2008-4059 |
|
score: 7.5 |
High |
| CVE-2009-2469 |
|
score: 10.0 |
Critical |
| CVE-2009-4129 |
|
score: 5.8 |
Medium |
| CVE-2009-4130 |
|
score: 5.8 |
Medium |
| CVE-2009-4630 |
|
score: 5.0 |
Medium |
| CVE-2011-0064 |
|
score: 6.8 |
Medium |
| CVE-2012-4929 |
|
score: 2.6 |
Low |
| CVE-2012-4930 |
|
score: 2.6 |
Low |
| CVE-2016-7152 |
|
score: 5.3 |
Medium |
| CVE-2016-7153 |
|
score: 5.3 |
Medium |
| CVE-2026-100756 |
|
score: 8.1 |
High |
| CVE-2026-100767 |
|
score: 8.8 |
High |
| CVE-2026-100768 |
|
score: 8.8 |
High |
| CVE-2026-100769 |
|
score: 8.8 |
High |
| CVE-2026-100770 |
|
score: 9.6 |
Critical |
| CVE-2026-100771 |
|
score: 8.1 |
High |
| CVE-2026-100772 |
|
score: 8.8 |
High |
| CVE-2026-100773 |
|
score: 8.8 |
High |
| CVE-2026-100774 |
|
score: 8.8 |
High |
| CVE-2026-100775 |
|
score: 9.6 |
Critical |
| CVE-2026-100776 |
|
score: 8.8 |
High |
| CVE-2026-100777 |
|
score: 8.8 |
High |
| CVE-2026-100778 |
|
score: 9.6 |
Critical |
| CVE-2026-100779 |
|
score: 8.8 |
High |
| CVE-2026-100780 |
|
score: 8.8 |
High |
| CVE-2026-100781 |
|
score: 9.6 |
Critical |
| CVE-2026-100782 |
|
score: 8.8 |
High |
| CVE-2026-100783 |
|
score: 4.3 |
Medium |
| CVE-2026-100784 |
|
score: 8.8 |
High |
| CVE-2026-100785 |
|
score: 8.8 |
High |
| CVE-2026-100786 |
|
score: 9.6 |
Critical |
| CVE-2026-100787 |
|
score: 9.6 |
Critical |
| CVE-2026-100808 |
|
score: 8.8 |
High |
| CVE-2026-100809 |
|
score: 8.1 |
High |
| CVE-2026-100810 |
|
score: 9.8 |
Critical |
| CVE-2026-100811 |
|
score: 9.6 |
Critical |
| CVE-2026-100812 |
|
score: 6.5 |
Medium |
| CVE-2026-100813 |
|
score: 8.8 |
High |
| CVE-2026-100814 |
|
score: 8.8 |
High |
| CVE-2026-100815 |
|
score: 8.8 |
High |
| CVE-2026-100816 |
|
score: 8.1 |
High |
| CVE-2026-100817 |
|
score: 5.4 |
Medium |
| CVE-2026-100818 |
|
score: 9.6 |
Critical |
| CVE-2026-100819 |
|
score: 9.6 |
Critical |
| CVE-2026-100820 |
|
score: 8.8 |
High |
| CVE-2026-100832 |
|
score: 8.8 |
High |
| CVE-2026-106016 |
|
score: 9.8 |
Critical |
| CVE-2026-74934 |
|
score: 7.5 |
High |
| CVE-2026-74935 |
|
score: 8.8 |
High |
| CVE-2026-74936 |
|
score: 9.8 |
Critical |
| CVE-2026-74937 |
|
score: 8.8 |
High |
| CVE-2026-74938 |
|
score: 9.1 |
Critical |
| CVE-2026-74939 |
|
score: 8.8 |
High |
| CVE-2026-74940 |
|
score: 9.8 |
Critical |
| CVE-2026-74941 |
|
score: 8.8 |
High |
| CVE-2026-74942 |
|
score: 8.8 |
High |
| CVE-2026-74943 |
|
score: 9.8 |
Critical |
| CVE-2026-74944 |
|
score: 9.8 |
Critical |
| CVE-2026-74945 |
|
score: 6.5 |
Medium |
| CVE-2026-74946 |
|
score: 8.8 |
High |
| CVE-2026-74947 |
|
score: 8.8 |
High |
| CVE-2026-74948 |
|
score: 6.5 |
Medium |
| CVE-2026-74949 |
|
score: 8.8 |
High |
| CVE-2026-74950 |
|
score: 8.8 |
High |
| CVE-2026-74952 |
|
score: 8.8 |
High |
| CVE-2026-74953 |
|
score: 8.8 |
High |
| CVE-2026-74954 |
|
score: 7.5 |
High |
| CVE-2026-74955 |
|
score: 8.8 |
High |
| CVE-2026-74956 |
|
score: 9.1 |
Critical |
| CVE-2026-74957 |
|
score: 8.1 |
High |
| CVE-2026-74958 |
|
score: 7.5 |
High |
| CVE-2026-74959 |
|
score: 9.1 |
Critical |
| CVE-2026-74960 |
|
score: 8.1 |
High |
| CVE-2026-74961 |
|
score: 9.1 |
Critical |
| CVE-2026-74962 |
|
score: 8.1 |
High |
| CVE-2026-74963 |
|
score: 5.4 |
Medium |
| CVE-2026-74964 |
|
score: 9.8 |
Critical |
| CVE-2026-74965 |
|
score: 8.8 |
High |
| CVE-2026-74966 |
|
score: 7.5 |
High |
| CVE-2026-74967 |
|
score: 5.4 |
Medium |
| CVE-2026-74968 |
|
score: 5.4 |
Medium |
| CVE-2026-74969 |
|
score: 8.8 |
High |
| CVE-2026-74970 |
|
score: 5.4 |
Medium |
| CVE-2026-74971 |
|
score: 4.3 |
Medium |
| CVE-2026-74972 |
|
score: 4.3 |
Medium |
| CVE-2026-74973 |
|
score: 4.2 |
Medium |
| CVE-2026-74974 |
|
score: 5.4 |
Medium |
| CVE-2026-74976 |
|
score: 6.5 |
Medium |
| CVE-2026-74977 |
|
score: 7.5 |
High |
| CVE-2026-74978 |
|
score: 8.1 |
High |
| CVE-2026-74979 |
|
score: 9.8 |
Critical |
| CVE-2026-74981 |
|
score: 8.1 |
High |
| CVE-2026-74982 |
|
score: 7.5 |
High |
| CVE-2026-74983 |
|
score: 8.1 |
High |
| CVE-2026-74984 |
|
score: 6.8 |
Medium |
| CVE-2026-74985 |
|
score: 9.8 |
Critical |
| CVE-2026-74986 |
|
score: 9.1 |
Critical |
| CVE-2026-74987 |
|
score: 9.8 |
Critical |
| CVE-2026-74988 |
|
score: 9.8 |
Critical |
| CVE-2026-74989 |
|
score: 9.8 |
Critical |
| CVE-2026-74990 |
|
score: 9.8 |
Critical |
| CVE-2026-75874 |
|
score: 10.0 |
Critical |
| CVE-2026-84118 |
|
score: 5.4 |
Medium |
| CVE-2026-84119 |
|
score: 9.6 |
Critical |
| CVE-2026-84120 |
|
score: 5.4 |
Medium |
| CVE-2026-84121 |
|
score: 9.6 |
Critical |
| CVE-2026-84122 |
|
score: 5.4 |
Medium |
| CVE-2026-84123 |
|
score: 8.8 |
High |
| CVE-2026-84124 |
|
score: 5.4 |
Medium |
| CVE-2026-84125 |
|
score: 5.4 |
Medium |
| CVE-2026-84126 |
|
score: 4.3 |
Medium |
| CVE-2026-84128 |
|
score: 8.8 |
High |
| CVE-2026-84129 |
|
score: 9.8 |
Critical |
| CVE-2026-84130 |
|
score: 7.5 |
High |
| CVE-2026-84131 |
|
score: 8.8 |
High |
| CVE-2026-84132 |
|
score: 7.5 |
High |
| CVE-2026-84133 |
|
score: 9.8 |
Critical |
| CVE-2026-84134 |
|
score: 9.8 |
Critical |
| CVE-2026-84136 |
|
score: 6.1 |
Medium |
| CVE-2026-84137 |
|
score: 4.3 |
Medium |
| CVE-2026-84138 |
|
score: 6.5 |
Medium |
| CVE-2026-84139 |
|
score: 6.1 |
Medium |
| CVE-2026-84140 |
|
score: 9.8 |
Critical |
| CVE-2026-84141 |
|
score: 9.8 |
Critical |
| CVE-2026-84142 |
|
score: 9.8 |
Critical |
| CVE-2026-84143 |
|
score: 9.8 |
Critical |
| CVE-2026-84144 |
|
score: 7.5 |
High |
| CVE-2026-84145 |
|
score: 7.5 |
High |
| CVE-2026-92005 |
|
score: 5.3 |
Medium |
| CVE-2026-92006 |
|
score: 8.8 |
High |
| CVE-2026-92007 |
|
score: 8.8 |
High |
| CVE-2026-92008 |
|
score: 8.8 |
High |
| CVE-2026-92009 |
|
score: 8.8 |
High |
| CVE-2026-92010 |
|
score: 8.8 |
High |
| CVE-2026-92011 |
|
score: 8.8 |
High |
| CVE-2026-92012 |
|
score: 8.8 |
High |
| CVE-2026-92013 |
|
score: 8.8 |
High |
| CVE-2026-92015 |
|
score: 8.8 |
High |
| CVE-2026-92016 |
|
score: 8.8 |
High |
| CVE-2026-92017 |
|
score: 8.8 |
High |
| CVE-2026-92018 |
|
score: 9.6 |
Critical |
| CVE-2026-92019 |
|
score: 8.1 |
High |
| CVE-2026-92020 |
|
score: 8.8 |
High |
| CVE-2026-92022 |
|
score: 8.8 |
High |
| CVE-2026-92023 |
|
score: 8.8 |
High |
| CVE-2026-92024 |
|
score: 8.8 |
High |
| CVE-2026-92025 |
|
score: 8.8 |
High |
| CVE-2026-92026 |
|
score: 8.8 |
High |
| CVE-2026-92027 |
|
score: 8.8 |
High |
| CVE-2026-92028 |
|
score: 8.8 |
High |
| CVE-2026-92029 |
|
score: 8.8 |
High |
| CVE-2026-92030 |
|
score: 5.4 |
Medium |
| CVE-2026-92031 |
|
score: 6.5 |
Medium |
| CVE-2026-92032 |
|
score: 9.6 |
Critical |
| CVE-2026-92034 |
|
score: 9.1 |
Critical |
| CVE-2026-92035 |
|
score: 9.6 |
Critical |
| CVE-2026-92036 |
|
score: 9.8 |
Critical |
| CVE-2026-92037 |
|
score: 9.8 |
Critical |
| CVE-2026-92038 |
|
score: 9.1 |
Critical |
| CVE-2026-92039 |
|
score: 6.3 |
Medium |
| CVE-2026-92040 |
|
score: 8.8 |
High |
| CVE-2026-92041 |
|
score: 9.1 |
Critical |
| CVE-2026-92042 |
|
score: 7.5 |
High |
| CVE-2026-92043 |
|
score: 8.8 |
High |
| CVE-2026-92044 |
|
score: 7.5 |
High |
| CVE-2026-92045 |
|
score: 9.6 |
Critical |
| CVE-2026-92046 |
|
score: 8.8 |
High |
| CVE-2026-92047 |
|
score: 8.8 |
High |
| CVE-2026-92048 |
|
score: 9.0 |
Critical |
| CVE-2026-92049 |
|
score: 8.8 |
High |
| CVE-2026-92050 |
|
score: 9.1 |
Critical |
| CVE-2026-92051 |
|
score: 9.1 |
Critical |
| CVE-2026-92052 |
|
score: 8.8 |
High |
| CVE-2026-92053 |
|
score: 8.8 |
High |
| CVE-2026-92054 |
|
score: 8.8 |
High |
| CVE-2026-92055 |
|
score: 8.8 |
High |
| CVE-2026-92056 |
|
score: 8.8 |
High |
| CVE-2026-92057 |
|
score: 9.1 |
Critical |
| CVE-2026-92058 |
|
score: 8.8 |
High |
| CVE-2026-92059 |
|
score: 9.3 |
Critical |
| CVE-2026-92060 |
|
score: 8.8 |
High |
| CVE-2026-92061 |
|
score: 9.8 |
Critical |
| CVE-2026-92062 |
|
score: 8.8 |
High |
| CVE-2026-92063 |
|
score: 6.5 |
Medium |
| CVE-2026-92064 |
|
score: 8.8 |
High |
| CVE-2026-92065 |
|
score: 8.8 |
High |
| CVE-2026-92066 |
|
score: 9.8 |
Critical |
| CVE-2026-92067 |
|
score: 8.8 |
High |
| CVE-2026-92068 |
|
score: 5.4 |
Medium |
| CVE-2026-92069 |
|
score: 5.4 |
Medium |
| CVE-2026-92070 |
|
score: 4.3 |
Medium |
| CVE-2026-92071 |
|
score: 9.6 |
Critical |
| CVE-2026-92072 |
|
score: 8.0 |
High |
| CVE-2026-92073 |
|
score: 8.8 |
High |
| CVE-2026-92074 |
|
score: 8.8 |
High |
| CVE-2026-92075 |
|
score: 9.1 |
Critical |
| CVE-2026-92076 |
|
score: 8.8 |
High |
| CVE-2026-92077 |
|
score: 6.5 |
Medium |
| CVE-2026-92078 |
|
score: 6.5 |
Medium |
| CVE-2026-92079 |
|
score: 9.1 |
Critical |
| CVE-2026-96869 |
|
score: 4.3 |
Medium |
| thunderbird (std) 153.0.1 |
| CVE-2008-3835 |
|
score: 7.5 |
High |
| CVE-2008-4060 |
|
score: 7.5 |
High |
| CVE-2009-1306 |
|
score: 4.3 |
Medium |
| CVE-2009-1307 |
|
score: 6.8 |
Medium |
| CVE-2009-1308 |
|
score: 4.3 |
Medium |
| CVE-2009-1309 |
|
score: 4.3 |
Medium |
| CVE-2009-1840 |
|
score: 9.3 |
Critical |
| CVE-2009-3980 |
|
score: 9.3 |
Critical |
| CVE-2009-3981 |
|
score: 9.3 |
Critical |
| CVE-2009-3982 |
|
score: 9.3 |
Critical |
| CVE-2009-3983 |
|
score: 6.8 |
Medium |
| CVE-2009-3984 |
|
score: 6.8 |
Medium |
| CVE-2009-4630 |
|
score: 5.0 |
Medium |
| CVE-2026-100756 |
|
score: 8.1 |
High |
| CVE-2026-100767 |
|
score: 8.8 |
High |
| CVE-2026-100768 |
|
score: 8.8 |
High |
| CVE-2026-100769 |
|
score: 8.8 |
High |
| CVE-2026-100770 |
|
score: 9.6 |
Critical |
| CVE-2026-100771 |
|
score: 8.1 |
High |
| CVE-2026-100772 |
|
score: 8.8 |
High |
| CVE-2026-100773 |
|
score: 8.8 |
High |
| CVE-2026-100774 |
|
score: 8.8 |
High |
| CVE-2026-100775 |
|
score: 9.6 |
Critical |
| CVE-2026-100776 |
|
score: 8.8 |
High |
| CVE-2026-100777 |
|
score: 8.8 |
High |
| CVE-2026-100778 |
|
score: 9.6 |
Critical |
| CVE-2026-100779 |
|
score: 8.8 |
High |
| CVE-2026-100780 |
|
score: 8.8 |
High |
| CVE-2026-100781 |
|
score: 9.6 |
Critical |
| CVE-2026-100782 |
|
score: 8.8 |
High |
| CVE-2026-100783 |
|
score: 4.3 |
Medium |
| CVE-2026-100784 |
|
score: 8.8 |
High |
| CVE-2026-100785 |
|
score: 8.8 |
High |
| CVE-2026-100786 |
|
score: 9.6 |
Critical |
| CVE-2026-100787 |
|
score: 9.6 |
Critical |
| CVE-2026-100808 |
|
score: 8.8 |
High |
| CVE-2026-100809 |
|
score: 8.1 |
High |
| CVE-2026-100810 |
|
score: 9.8 |
Critical |
| CVE-2026-100811 |
|
score: 9.6 |
Critical |
| CVE-2026-100812 |
|
score: 6.5 |
Medium |
| CVE-2026-100813 |
|
score: 8.8 |
High |
| CVE-2026-100814 |
|
score: 8.8 |
High |
| CVE-2026-100815 |
|
score: 8.8 |
High |
| CVE-2026-100816 |
|
score: 8.1 |
High |
| CVE-2026-100817 |
|
score: 5.4 |
Medium |
| CVE-2026-100818 |
|
score: 9.6 |
Critical |
| CVE-2026-100819 |
|
score: 9.6 |
Critical |
| CVE-2026-100820 |
|
score: 8.8 |
High |
| CVE-2026-100832 |
|
score: 8.8 |
High |
| CVE-2026-74934 |
|
score: 7.5 |
High |
| CVE-2026-74935 |
|
score: 8.8 |
High |
| CVE-2026-74936 |
|
score: 9.8 |
Critical |
| CVE-2026-74937 |
|
score: 8.8 |
High |
| CVE-2026-74938 |
|
score: 9.1 |
Critical |
| CVE-2026-74939 |
|
score: 8.8 |
High |
| CVE-2026-74940 |
|
score: 9.8 |
Critical |
| CVE-2026-74941 |
|
score: 8.8 |
High |
| CVE-2026-74942 |
|
score: 8.8 |
High |
| CVE-2026-74943 |
|
score: 9.8 |
Critical |
| CVE-2026-74944 |
|
score: 9.8 |
Critical |
| CVE-2026-74945 |
|
score: 6.5 |
Medium |
| CVE-2026-74946 |
|
score: 8.8 |
High |
| CVE-2026-74947 |
|
score: 8.8 |
High |
| CVE-2026-74948 |
|
score: 6.5 |
Medium |
| CVE-2026-74949 |
|
score: 8.8 |
High |
| CVE-2026-74950 |
|
score: 8.8 |
High |
| CVE-2026-74952 |
|
score: 8.8 |
High |
| CVE-2026-74953 |
|
score: 8.8 |
High |
| CVE-2026-74954 |
|
score: 7.5 |
High |
| CVE-2026-74955 |
|
score: 8.8 |
High |
| CVE-2026-74956 |
|
score: 9.1 |
Critical |
| CVE-2026-74957 |
|
score: 8.1 |
High |
| CVE-2026-74958 |
|
score: 7.5 |
High |
| CVE-2026-74959 |
|
score: 9.1 |
Critical |
| CVE-2026-74960 |
|
score: 8.1 |
High |
| CVE-2026-74961 |
|
score: 9.1 |
Critical |
| CVE-2026-74962 |
|
score: 8.1 |
High |
| CVE-2026-74963 |
|
score: 5.4 |
Medium |
| CVE-2026-74964 |
|
score: 9.8 |
Critical |
| CVE-2026-74965 |
|
score: 8.8 |
High |
| CVE-2026-74966 |
|
score: 7.5 |
High |
| CVE-2026-74967 |
|
score: 5.4 |
Medium |
| CVE-2026-74968 |
|
score: 5.4 |
Medium |
| CVE-2026-74969 |
|
score: 8.8 |
High |
| CVE-2026-74970 |
|
score: 5.4 |
Medium |
| CVE-2026-74971 |
|
score: 4.3 |
Medium |
| CVE-2026-74972 |
|
score: 4.3 |
Medium |
| CVE-2026-74973 |
|
score: 4.2 |
Medium |
| CVE-2026-74974 |
|
score: 5.4 |
Medium |
| CVE-2026-74976 |
|
score: 6.5 |
Medium |
| CVE-2026-74977 |
|
score: 7.5 |
High |
| CVE-2026-74978 |
|
score: 8.1 |
High |
| CVE-2026-74979 |
|
score: 9.8 |
Critical |
| CVE-2026-74981 |
|
score: 8.1 |
High |
| CVE-2026-74982 |
|
score: 7.5 |
High |
| CVE-2026-74983 |
|
score: 8.1 |
High |
| CVE-2026-74984 |
|
score: 6.8 |
Medium |
| CVE-2026-74985 |
|
score: 9.8 |
Critical |
| CVE-2026-74986 |
|
score: 9.1 |
Critical |
| CVE-2026-74987 |
|
score: 9.8 |
Critical |
| CVE-2026-74988 |
|
score: 9.8 |
Critical |
| CVE-2026-74989 |
|
score: 9.8 |
Critical |
| CVE-2026-74990 |
|
score: 9.8 |
Critical |
| CVE-2026-75874 |
|
score: 10.0 |
Critical |
| CVE-2026-84118 |
|
score: 5.4 |
Medium |
| CVE-2026-84119 |
|
score: 9.6 |
Critical |
| CVE-2026-84120 |
|
score: 5.4 |
Medium |
| CVE-2026-84121 |
|
score: 9.6 |
Critical |
| CVE-2026-84122 |
|
score: 5.4 |
Medium |
| CVE-2026-84123 |
|
score: 8.8 |
High |
| CVE-2026-84124 |
|
score: 5.4 |
Medium |
| CVE-2026-84125 |
|
score: 5.4 |
Medium |
| CVE-2026-84126 |
|
score: 4.3 |
Medium |
| CVE-2026-84128 |
|
score: 8.8 |
High |
| CVE-2026-84129 |
|
score: 9.8 |
Critical |
| CVE-2026-84130 |
|
score: 7.5 |
High |
| CVE-2026-84131 |
|
score: 8.8 |
High |
| CVE-2026-84132 |
|
score: 7.5 |
High |
| CVE-2026-84133 |
|
score: 9.8 |
Critical |
| CVE-2026-84134 |
|
score: 9.8 |
Critical |
| CVE-2026-84136 |
|
score: 6.1 |
Medium |
| CVE-2026-84137 |
|
score: 4.3 |
Medium |
| CVE-2026-84138 |
|
score: 6.5 |
Medium |
| CVE-2026-84139 |
|
score: 6.1 |
Medium |
| CVE-2026-84140 |
|
score: 9.8 |
Critical |
| CVE-2026-84141 |
|
score: 9.8 |
Critical |
| CVE-2026-84142 |
|
score: 9.8 |
Critical |
| CVE-2026-84143 |
|
score: 9.8 |
Critical |
| CVE-2026-84144 |
|
score: 7.5 |
High |
| CVE-2026-84145 |
|
score: 7.5 |
High |
| CVE-2026-84637 |
|
score: 9.8 |
Critical |
| CVE-2026-84639 |
|
score: 9.1 |
Critical |
| CVE-2026-84640 |
|
score: 7.5 |
High |
| CVE-2026-84641 |
|
score: 7.5 |
High |
| CVE-2026-84642 |
|
score: 7.5 |
High |
| CVE-2026-92005 |
|
score: 5.3 |
Medium |
| CVE-2026-92006 |
|
score: 8.8 |
High |
| CVE-2026-92007 |
|
score: 8.8 |
High |
| CVE-2026-92008 |
|
score: 8.8 |
High |
| CVE-2026-92009 |
|
score: 8.8 |
High |
| CVE-2026-92010 |
|
score: 8.8 |
High |
| CVE-2026-92011 |
|
score: 8.8 |
High |
| CVE-2026-92012 |
|
score: 8.8 |
High |
| CVE-2026-92013 |
|
score: 8.8 |
High |
| CVE-2026-92015 |
|
score: 8.8 |
High |
| CVE-2026-92016 |
|
score: 8.8 |
High |
| CVE-2026-92017 |
|
score: 8.8 |
High |
| CVE-2026-92018 |
|
score: 9.6 |
Critical |
| CVE-2026-92019 |
|
score: 8.1 |
High |
| CVE-2026-92020 |
|
score: 8.8 |
High |
| CVE-2026-92022 |
|
score: 8.8 |
High |
| CVE-2026-92023 |
|
score: 8.8 |
High |
| CVE-2026-92024 |
|
score: 8.8 |
High |
| CVE-2026-92025 |
|
score: 8.8 |
High |
| CVE-2026-92026 |
|
score: 8.8 |
High |
| CVE-2026-92027 |
|
score: 8.8 |
High |
| CVE-2026-92028 |
|
score: 8.8 |
High |
| CVE-2026-92029 |
|
score: 8.8 |
High |
| CVE-2026-92030 |
|
score: 5.4 |
Medium |
| CVE-2026-92031 |
|
score: 6.5 |
Medium |
| CVE-2026-92032 |
|
score: 9.6 |
Critical |
| CVE-2026-92034 |
|
score: 9.1 |
Critical |
| CVE-2026-92035 |
|
score: 9.6 |
Critical |
| CVE-2026-92036 |
|
score: 9.8 |
Critical |
| CVE-2026-92037 |
|
score: 9.8 |
Critical |
| CVE-2026-92038 |
|
score: 9.1 |
Critical |
| CVE-2026-92039 |
|
score: 6.3 |
Medium |
| CVE-2026-92040 |
|
score: 8.8 |
High |
| CVE-2026-92041 |
|
score: 9.1 |
Critical |
| CVE-2026-92042 |
|
score: 7.5 |
High |
| CVE-2026-92043 |
|
score: 8.8 |
High |
| CVE-2026-92044 |
|
score: 7.5 |
High |
| CVE-2026-92045 |
|
score: 9.6 |
Critical |
| CVE-2026-92046 |
|
score: 8.8 |
High |
| CVE-2026-92047 |
|
score: 8.8 |
High |
| CVE-2026-92048 |
|
score: 9.0 |
Critical |
| CVE-2026-92049 |
|
score: 8.8 |
High |
| CVE-2026-92050 |
|
score: 9.1 |
Critical |
| CVE-2026-92051 |
|
score: 9.1 |
Critical |
| CVE-2026-92052 |
|
score: 8.8 |
High |
| CVE-2026-92053 |
|
score: 8.8 |
High |
| CVE-2026-92054 |
|
score: 8.8 |
High |
| CVE-2026-92055 |
|
score: 8.8 |
High |
| CVE-2026-92056 |
|
score: 8.8 |
High |
| CVE-2026-92057 |
|
score: 9.1 |
Critical |
| CVE-2026-92058 |
|
score: 8.8 |
High |
| CVE-2026-92059 |
|
score: 9.3 |
Critical |
| CVE-2026-92060 |
|
score: 8.8 |
High |
| CVE-2026-92061 |
|
score: 9.8 |
Critical |
| CVE-2026-92062 |
|
score: 8.8 |
High |
| CVE-2026-92063 |
|
score: 6.5 |
Medium |
| CVE-2026-92064 |
|
score: 8.8 |
High |
| CVE-2026-92065 |
|
score: 8.8 |
High |
| CVE-2026-92066 |
|
score: 9.8 |
Critical |
| CVE-2026-92067 |
|
score: 8.8 |
High |
| CVE-2026-92068 |
|
score: 5.4 |
Medium |
| CVE-2026-92069 |
|
score: 5.4 |
Medium |
| CVE-2026-92070 |
|
score: 4.3 |
Medium |
| CVE-2026-92071 |
|
score: 9.6 |
Critical |
| CVE-2026-92072 |
|
score: 8.0 |
High |
| CVE-2026-92073 |
|
score: 8.8 |
High |
| CVE-2026-92074 |
|
score: 8.8 |
High |
| CVE-2026-92075 |
|
score: 9.1 |
Critical |
| CVE-2026-92076 |
|
score: 8.8 |
High |
| CVE-2026-92077 |
|
score: 6.5 |
Medium |
| CVE-2026-92078 |
|
score: 6.5 |
Medium |
| CVE-2026-92079 |
|
score: 9.1 |
Critical |
| CVE-2026-92238 |
|
score: 9.8 |
Critical |
| CVE-2026-92239 |
|
score: 8.1 |
High |
| CVE-2026-92240 |
|
score: 9.1 |
Critical |
| CVE-2026-96869 |
|
score: 4.3 |
Medium |
| mumble (std) 1.5.915 |
| CVE-2025-71264 |
|
score: 3.7 |
Low |
| nasm (std) 3.02 |
| CVE-2026-6067 |
|
score: 5.5 |
Medium |
| CVE-2026-6068 |
|
score: 9.6 |
Critical |
| CVE-2026-6069 |
|
score: 7.5 |
High |
| openssl30 (std) 3.6.2 |
| CVE-2026-14457 |
|
score: 7.5 |
High |
| CVE-2026-18798 |
|
score: 7.5 |
High |
| CVE-2026-34180 |
|
score: 7.5 |
High |
| CVE-2026-34181 |
|
score: 7.4 |
High |
| CVE-2026-34182 |
|
score: 9.1 |
Critical |
| CVE-2026-34183 |
|
score: 7.5 |
High |
| CVE-2026-35188 |
|
score: 5.0 |
Medium |
| CVE-2026-35189 |
|
score: 5.3 |
Medium |
| CVE-2026-35191 |
|
score: 3.7 |
Low |
| CVE-2026-42764 |
|
score: 7.5 |
High |
| CVE-2026-42765 |
|
score: 7.5 |
High |
| CVE-2026-42766 |
|
score: 5.9 |
Medium |
| CVE-2026-42767 |
|
score: 5.9 |
Medium |
| CVE-2026-42768 |
|
score: 3.7 |
Low |
| CVE-2026-42769 |
|
score: 5.3 |
Medium |
| CVE-2026-42770 |
|
score: 3.7 |
Low |
| CVE-2026-42772 |
|
score: 5.3 |
Medium |
| CVE-2026-45445 |
|
score: 7.5 |
High |
| CVE-2026-45446 |
|
score: 4.8 |
Medium |
| CVE-2026-45447 |
|
score: 8.8 |
High |
| CVE-2026-54872 |
|
score: 3.7 |
Low |
| CVE-2026-54873 |
|
score: 7.5 |
High |
| CVE-2026-54874 |
|
score: 7.5 |
High |
| CVE-2026-54875 |
|
score: 3.7 |
Low |
| CVE-2026-63072 |
|
score: 7.5 |
High |
| CVE-2026-63073 |
|
score: 9.8 |
Critical |
| CVE-2026-63074 |
|
score: 5.9 |
Medium |
| CVE-2026-63075 |
|
score: 7.5 |
High |
| CVE-2026-63076 |
|
score: 7.5 |
High |
| CVE-2026-72897 |
|
score: 7.5 |
High |
| CVE-2026-7383 |
|
score: 8.1 |
High |
| CVE-2026-75803 |
|
score: 9.1 |
Critical |
| CVE-2026-75804 |
|
score: 5.3 |
Medium |
| CVE-2026-75805 |
|
score: 5.3 |
Medium |
| CVE-2026-75806 |
|
score: 5.3 |
Medium |
| CVE-2026-77696 |
|
score: 3.7 |
Low |
| CVE-2026-84782 |
|
score: 8.2 |
High |
| CVE-2026-84784 |
|
score: 7.5 |
High |
| CVE-2026-9076 |
|
score: 7.5 |
High |
| db4 (std) 4.8.30 |
| CVE-2017-3604 |
|
score: 7.0 |
High |
| CVE-2017-3605 |
|
score: 7.0 |
High |
| CVE-2017-3606 |
|
score: 7.0 |
High |
| CVE-2017-3607 |
|
score: 7.0 |
High |
| CVE-2017-3608 |
|
score: 7.0 |
High |
| CVE-2017-3609 |
|
score: 7.0 |
High |
| CVE-2017-3610 |
|
score: 7.0 |
High |
| CVE-2017-3611 |
|
score: 7.0 |
High |
| CVE-2017-3612 |
|
score: 7.0 |
High |
| CVE-2017-3613 |
|
score: 7.0 |
High |
| CVE-2017-3614 |
|
score: 7.0 |
High |
| CVE-2017-3615 |
|
score: 7.0 |
High |
| CVE-2017-3616 |
|
score: 7.0 |
High |
| CVE-2017-3617 |
|
score: 7.0 |
High |
| CVE-2019-2708 |
|
score: 3.3 |
Low |
| CVE-2020-2981 |
|
score: 7.0 |
High |
| db5 (std) 5.3.28 |
| CVE-2017-3604 |
|
score: 7.0 |
High |
| CVE-2017-3605 |
|
score: 7.0 |
High |
| CVE-2017-3606 |
|
score: 7.0 |
High |
| CVE-2017-3607 |
|
score: 7.0 |
High |
| CVE-2017-3608 |
|
score: 7.0 |
High |
| CVE-2017-3609 |
|
score: 7.0 |
High |
| CVE-2017-3610 |
|
score: 7.0 |
High |
| CVE-2017-3611 |
|
score: 7.0 |
High |
| CVE-2017-3612 |
|
score: 7.0 |
High |
| CVE-2017-3613 |
|
score: 7.0 |
High |
| CVE-2017-3614 |
|
score: 7.0 |
High |
| CVE-2017-3615 |
|
score: 7.0 |
High |
| CVE-2017-3616 |
|
score: 7.0 |
High |
| CVE-2017-3617 |
|
score: 7.0 |
High |
| CVE-2019-2708 |
|
score: 3.3 |
Low |
| CVE-2020-2981 |
|
score: 7.0 |
High |
| perl-5.42 (std) 5.42.2 |
| CVE-2026-13221 |
|
score: 9.1 |
Critical |
| CVE-2026-57432 |
|
score: 8.4 |
High |
| CVE-2026-8376 |
|
score: 9.8 |
Critical |
python-pip (v13) 26.2.1
python-pip (v14) 26.2.1 |
| CVE-2018-20225 |
|
score: 7.8 |
High |
| qemu (std) 11.1.2 |
| CVE-2021-20255 |
|
score: 5.5 |
Medium |
| CVE-2023-1386 |
|
score: 3.3 |
Low |
qt5-qtdeclarative (std) 5.15.18
qt5-qtbase (std) 5.15.18
qt5-qtmultimedia (std) 5.15.18
qt5-qtx11extras (std) 5.15.18
qt5-qtimageformats (std) 5.15.18
qt5-qtscript (std) 5.15.18
qt5-qtxmlpatterns (std) 5.15.18
qt5-qttools (std) 5.15.18
qt5-qtsvg (std) 5.15.18 |
| CVE-2025-30348 |
|
score: 5.8 |
Medium |
| readymedia (std) 1.3.3 |
| CVE-2023-47430 |
|
score: 7.5 |
High |
| t1lib (std) 5.1.2 |
| CVE-2010-2642 |
|
score: 7.6 |
High |
| CVE-2011-0433 |
|
score: 6.8 |
Medium |
| CVE-2011-5244 |
|
score: 6.8 |
Medium |
| tinc (std) 1.0.37 |
| CVE-2013-1428 |
|
score: 6.5 |
Medium |
| upx (std) 5.2.1 |
| CVE-2023-23456 |
|
score: 5.3 |
Medium |
| CVE-2023-23457 |
|
score: 5.3 |
Medium |
| xorg-xfont (std) 1.5.4 |
| CVE-2026-56002 |
|
score: 8.5 |
High |