Threadlinqs IntelligenceStart free

Vendor1 product tracked

Fedoraproject vulnerabilities & exploitation

19 in CISA KEV3 ransomware-linked2 with public exploit

As of 2026-10-05, Threadlinqs tracks 20 Fedoraproject CVEs, 19 in the CISA Known Exploited Vulnerabilities catalog, 3 used in ransomware campaigns, linked to 29 tracked threat campaigns and 12 named threat actors.

CVEs
20Since 2016
CISA KEV
1995% of CVEs
Critical
4CVSS v3 9.0+
Avg CVSS
7.7/10Max 10
Threats
29Linked campaigns
Actors
12Named in campaigns

Data as of:

Exploitation timeline

Threadlinqs has recorded 20 Fedoraproject CVEs published between and . The busiest month was 2021-11 (3 new CVEs). 19 of them (95%) 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 20 of 20 tracked Fedoraproject CVEs.

Products affected

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

  • Fedora 20 CVEs

Threat activity

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

Threat actors targeting Fedoraproject

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

How to prioritise Fedoraproject patching

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

  • 19 of 20 Fedoraproject CVEs (95%) are in CISA KEV: treat them as actively exploited and remediate them first, starting with CVE-2020-1472, CVE-2021-44228, 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-2023-29483 (1.9%).
  • 4 CVEs score Critical and 9 High on CVSS v3 (maximum 10, average 7.7); sequence these after KEV and high-EPSS items.
  • 2 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.