Threadlinqs IntelligenceStart free

Vendor2 products tracked

Linux vulnerabilities & exploitation

21 in CISA KEV3 ransomware-linked71 with public exploit

As of 2026-11-19, Threadlinqs tracks 162 Linux CVEs, 21 in the CISA Known Exploited Vulnerabilities catalog, 3 used in ransomware campaigns, linked to 131 tracked threat campaigns and 12 named threat actors.

CVEs
162Since 2009
CISA KEV
2113% of CVEs
Critical
10CVSS v3 9.0+
Avg CVSS
8/10Max 9.8
Threats
131Linked campaigns
Actors
12Named in campaigns

Data as of:

Exploitation timeline

Threadlinqs has recorded 162 Linux CVEs published between and . The busiest month was 2026-07 (37 new CVEs). 21 of them (13%) 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 60 of 162 tracked Linux CVEs.

Products affected

Threadlinqs normalises CPE and CNA product records across all 162 CVEs; 2 distinct Linux products are affected. The most frequently affected:

  • Linux 128 CVEs
  • Kernel 34 CVEs

Threat activity

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

Threat actors targeting Linux

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

How to prioritise Linux patching

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

  • 21 of 162 Linux CVEs (13%) are in CISA KEV: treat them as actively exploited and remediate them first, starting with CVE-2022-0847, CVE-2018-15982, CVE-2016-5195.
  • 3 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-2022-22972 (56.3%), CVE-2017-16995 (30.1%), CVE-2010-1173 (21.2%).
  • 10 CVEs score Critical and 86 High on CVSS v3 (maximum 9.8, average 8); sequence these after KEV and high-EPSS items.
  • 71 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-11-19 and refresh daily.