Vulnerable source packages among backports for stable

Note that the list below is based on source packages. This means that packages are not listed here once a new, fixed source version has been uploaded to the archive, even if there are still some vulnerable binary packages present in the archive.


PackageBugUrgencyRemote
linuxCVE-2013-7445not yet assignedno
CVE-2018-12928lowno
CVE-2019-15213not yet assignedno
CVE-2019-16089not yet assignedno
CVE-2019-19449not yet assignedno
CVE-2019-19814not yet assignedno
CVE-2019-20794not yet assignedno
CVE-2020-14304not yet assignedno
CVE-2020-36694not yet assignedno
CVE-2021-3847not yet assignedno
CVE-2021-3864not yet assignedno
CVE-2023-3397not yet assignedno
CVE-2023-4010not yet assignedno
CVE-2023-6238not yet assignedno
CVE-2023-6240not yet assignedno
CVE-2023-31082not yet assignedno
CVE-2023-37454not yet assignedno
CVE-2024-2193not yet assignedno
CVE-2024-21803not yet assignedno
CVE-2024-24864not yet assignedno
CVE-2024-56709not yet assignedno
CVE-2025-38676not yet assignedno
CVE-2025-38677not yet assignedno
CVE-2025-38731not yet assignedno
CVE-2025-38732not yet assignedno
CVE-2025-38733not yet assignedno
CVE-2025-38734not yet assignedno
CVE-2025-38735not yet assignedno
CVE-2025-38736not yet assignedno
CVE-2025-38737not yet assignedno
CVE-2025-39673not yet assignedno
CVE-2025-39674not yet assignedno
CVE-2025-39675not yet assignedno
CVE-2025-39676not yet assignedno
CVE-2025-39677not yet assignedno
CVE-2025-39678not yet assignedno
CVE-2025-39679not yet assignedno
CVE-2025-39680not yet assignedno
CVE-2025-39681not yet assignedno
CVE-2025-39682not yet assignedno
CVE-2025-39683not yet assignedno
CVE-2025-39684not yet assignedno
CVE-2025-39685not yet assignedno
CVE-2025-39686not yet assignedno
CVE-2025-39687not yet assignedno
CVE-2025-39689not yet assignedno
CVE-2025-39690not yet assignedno
CVE-2025-39691not yet assignedno
CVE-2025-39692not yet assignedno
CVE-2025-39693not yet assignedno
CVE-2025-39694not yet assignedno
CVE-2025-39695not yet assignedno
CVE-2025-39696not yet assignedno
CVE-2025-39697not yet assignedno
CVE-2025-39698not yet assignedno
CVE-2025-39699not yet assignedno
CVE-2025-39700not yet assignedno
CVE-2025-39701not yet assignedno
CVE-2025-39702not yet assignedno
CVE-2025-39703not yet assignedno
CVE-2025-39704not yet assignedno
CVE-2025-39705not yet assignedno
CVE-2025-39706not yet assignedno
CVE-2025-39707not yet assignedno
CVE-2025-39708not yet assignedno
CVE-2025-39709not yet assignedno
CVE-2025-39710not yet assignedno
CVE-2025-39711not yet assignedno
CVE-2025-39712not yet assignedno
CVE-2025-39713not yet assignedno
CVE-2025-39714not yet assignedno
CVE-2025-39715not yet assignedno
CVE-2025-39716not yet assignedno
CVE-2025-39717not yet assignedno
CVE-2025-39718not yet assignedno
CVE-2025-39719not yet assignedno
CVE-2025-39720not yet assignedno
CVE-2025-39721not yet assignedno
CVE-2025-39722not yet assignedno
CVE-2025-39723not yet assignedno
CVE-2025-39724not yet assignedno
CVE-2025-39765not yet assignedno
CVE-2025-39766not yet assignedno
CVE-2025-39767not yet assignedno
CVE-2025-39768not yet assignedno
CVE-2025-39769not yet assignedno
CVE-2025-39770not yet assignedno
CVE-2025-39771not yet assignedno
CVE-2025-39772not yet assignedno
CVE-2025-39773not yet assignedno
CVE-2025-39774not yet assignedno
CVE-2025-39775not yet assignedno
CVE-2025-39776not yet assignedno
CVE-2025-39777not yet assignedno
CVE-2025-39779not yet assignedno
CVE-2025-39780not yet assignedno
CVE-2025-39781not yet assignedno
CVE-2025-39782not yet assignedno
CVE-2025-39783not yet assignedno
CVE-2025-39784not yet assignedno
CVE-2025-39785not yet assignedno
CVE-2025-39786not yet assignedno
CVE-2025-39787not yet assignedno
CVE-2025-39788not yet assignedno
CVE-2025-39789not yet assignedno
CVE-2025-39790not yet assignedno
CVE-2025-39791not yet assignedno
CVE-2025-39800not yet assignedno
CVE-2025-39801not yet assignedno
CVE-2025-39802not yet assignedno
CVE-2025-39803not yet assignedno
CVE-2025-39804not yet assignedno
CVE-2025-39805not yet assignedno
CVE-2025-39806not yet assignedno
CVE-2025-39807not yet assignedno
CVE-2025-39808not yet assignedno
CVE-2025-39809not yet assignedno
CVE-2025-39810not yet assignedno
CVE-2025-39811not yet assignedno
CVE-2025-39812not yet assignedno
CVE-2025-39813not yet assignedno
CVE-2025-39814not yet assignedno
CVE-2025-39815not yet assignedno
CVE-2025-39816not yet assignedno
CVE-2025-39817not yet assignedno
CVE-2025-39818not yet assignedno
CVE-2025-39819not yet assignedno
CVE-2025-39820not yet assignedno
CVE-2025-39821not yet assignedno
CVE-2025-39822not yet assignedno
CVE-2025-39823not yet assignedno
CVE-2025-39824not yet assignedno
CVE-2025-39825not yet assignedno
CVE-2025-39826not yet assignedno
CVE-2025-39827not yet assignedno
CVE-2025-39828not yet assignedno
CVE-2025-39829not yet assignedno
CVE-2025-39830not yet assignedno
CVE-2025-39831not yet assignedno
CVE-2025-39832not yet assignedno
CVE-2025-39833not yet assignedno
CVE-2025-39834not yet assignedno
CVE-2025-39835not yet assignedno
CVE-2025-39836not yet assignedno
CVE-2025-40300not yet assignedno
suricataCVE-2025-53538not yet assignedno

If a "**" is included, the urgency field was automatically assigned by the NVD (National Vulnerability Database). Note that this rating is automatically derived from a set of known factors about the issue (such as access complexity, confidentiality impact, exploitability, remediation level, and others). Human intervention is involved in determining the values of these factors, but the rating itself comes from a fully automated formula.


Search for package or bug name: Reporting problems