Threadlinqs IntelligenceStart free

Vendor4 products tracked

RARLAB vulnerabilities & exploitation

3 in CISA KEV2 ransomware-linked5 with public exploit

As of 2026-10-15, Threadlinqs tracks 5 RARLAB CVEs, 3 in the CISA Known Exploited Vulnerabilities catalog, 2 used in ransomware campaigns, linked to 14 tracked threat campaigns and 11 named threat actors.

CVEs
5Since 2023
CISA KEV
360% of CVEs
Critical
0CVSS v3 9.0+
Avg CVSS
8/10Max 8.8
Threats
14Linked campaigns
Actors
11Named in campaigns

Data as of:

Exploitation timeline

Threadlinqs has recorded 5 RARLAB CVEs published between and . The busiest month was 2023-08 (1 new CVE). 3 of them (60%) 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 RARLAB CVEs.

Products affected

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

  • WinRAR 5 CVEs
  • RAR 1 CVE
  • UnRAR 1 CVE
  • UnRAR.dll 1 CVE

Threat activity

14 tracked threat campaigns reference RARLAB products or exploit RARLAB CVEs:

Threat actors targeting RARLAB

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

How to prioritise RARLAB patching

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

  • 3 of 5 RARLAB CVEs (60%) are in CISA KEV: treat them as actively exploited and remediate them first, starting with CVE-2023-38831, CVE-2025-8088, CVE-2025-6218.
  • 2 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-40477 (11.4%), CVE-2026-14191 (0.4%).
  • 0 CVEs score Critical and 5 High on CVSS v3 (maximum 8.8, average 8); 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-10-15 and refresh daily.