Threadlinqs IntelligenceStart free

Vendor1 product tracked

Debian vulnerabilities & exploitation

25 in CISA KEV5 ransomware-linked3 with public exploit

As of 2026-10-05, Threadlinqs tracks 26 Debian CVEs, 25 in the CISA Known Exploited Vulnerabilities catalog, 5 used in ransomware campaigns, linked to 61 tracked threat campaigns and 12 named threat actors.

CVEs
26Since 2016
CISA KEV
2596% of CVEs
Critical
8CVSS v3 9.0+
Avg CVSS
8/10Max 10
Threats
61Linked campaigns
Actors
12Named in campaigns

Data as of:

Exploitation timeline

Threadlinqs has recorded 26 Debian CVEs published between and . The busiest month was 2023-04 (2 new CVEs). 25 of them (96%) are listed in CISA KEV, which means exploitation in the wild has been confirmed.

Most exploited vulnerabilities

Ranked with CISA KEV listings first, then EPSS exploit probability, then CVSS score. Showing 26 of 26 tracked Debian CVEs.

Products affected

Threadlinqs normalises CPE and CNA product records across all 26 CVEs; 1 distinct Debian product is affected. The most frequently affected:

  • Linux 26 CVEs

Threat activity

61 tracked threat campaigns reference Debian products or exploit Debian CVEs; the 25 most recent are listed.

Threat actors targeting Debian

Named threat actors attributed to campaigns that involve Debian products or CVEs, with the number of linked campaigns:

How to prioritise Debian patching

This order follows the data Threadlinqs holds for Debian, not a generic severity checklist:

  • 25 of 26 Debian CVEs (96%) are in CISA KEV: treat them as actively exploited and remediate them first, starting with CVE-2017-8291, CVE-2022-0543, CVE-2020-1472.
  • 5 CVEs are known to be used in ransomware campaigns; patch these ahead of other KEV entries on internet-facing systems.
  • Outside KEV, the highest EPSS scores are CVE-2019-12111 (3.4%).
  • 8 CVEs score Critical and 10 High on CVSS v3 (maximum 10, average 8); sequence these after KEV and high-EPSS items.
  • 3 CVEs have a public exploit or proof of concept recorded, which shortens the time from disclosure to attack.

About this data

Vendor attribution comes from the CNA and CPE product records of each CVE, folded to one vendor name; CVSS, EPSS and KEV status are read from the Threadlinqs CVE catalog; campaign and actor links come from tracked threat records. Counts reflect the data as of 2026-10-05 and refresh daily.