Threadlinqs IntelligenceStart free

Vendor6 products tracked

Apache vulnerabilities & exploitation

5 in CISA KEV1 ransomware-linked5 with public exploit

As of 2026-11-07, Threadlinqs tracks 5 Apache CVEs, 5 in the CISA Known Exploited Vulnerabilities catalog, 1 used in ransomware campaigns, linked to 28 tracked threat campaigns and 12 named threat actors.

CVEs
5Since 2016
CISA KEV
5100% of CVEs
Critical
3CVSS v3 9.0+
Avg CVSS
9.2/10Max 10
Threats
28Linked campaigns
Actors
12Named in campaigns

Data as of:

Exploitation timeline

Threadlinqs has recorded 5 Apache CVEs published between and . The busiest month was 2026-04 (1 new CVE). 5 of them (100%) 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 5 of 5 tracked Apache CVEs.

Products affected

Threadlinqs normalises CPE and CNA product records across all 5 CVEs; 6 distinct Apache products are affected. The most frequently affected:

  • ActiveMQ Classic 1 CVE
  • Aurora 1 CVE
  • Log4j 1 CVE
  • Shiro 1 CVE
  • Solr 1 CVE
  • Tomcat 1 CVE

Threat activity

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

Threat actors targeting Apache

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

How to prioritise Apache patching

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

  • 5 of 5 Apache CVEs (100%) are in CISA KEV: treat them as actively exploited and remediate them first, starting with CVE-2021-44228, CVE-2020-1938, CVE-2019-17558.
  • 1 CVE is known to be used in ransomware campaigns; patch these ahead of other KEV entries on internet-facing systems.
  • 3 CVEs score Critical and 2 High on CVSS v3 (maximum 10, average 9.2); sequence these after KEV and high-EPSS items.
  • 5 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-07 and refresh daily.