Threadlinqs IntelligenceStart free

Vendor1 product tracked

redis vulnerabilities & exploitation

1 in CISA KEV1 ransomware-linked6 with public exploit

As of 2026-10-10, Threadlinqs tracks 7 redis CVEs, 1 in the CISA Known Exploited Vulnerabilities catalog, 1 used in ransomware campaigns, linked to 7 tracked threat campaigns and 1 named threat actor.

CVEs
7Since 2022
CISA KEV
114% of CVEs
Critical
3CVSS v3 9.0+
Avg CVSS
9.1/10Max 10
Threats
7Linked campaigns
Actors
1Named in campaigns

Data as of:

Exploitation timeline

Threadlinqs has recorded 7 redis CVEs published between and . The busiest month was 2026-05 (3 new CVEs). 1 of them (14%) 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 7 of 7 tracked redis CVEs.

Products affected

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

  • Redis 7 CVEs

Threat activity

7 tracked threat campaigns reference redis products or exploit redis CVEs:

Threat actors targeting redis

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

How to prioritise redis patching

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

  • 1 of 7 redis CVEs (14%) are in CISA KEV: treat them as actively exploited and remediate them first, starting with CVE-2022-0543.
  • 1 CVE is 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-2025-49844 (82.3%), CVE-2025-62507 (6.8%), CVE-2026-25243 (3.7%).
  • 3 CVEs score Critical and 4 High on CVSS v3 (maximum 10, average 9.1); sequence these after KEV and high-EPSS items.
  • 6 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-10 and refresh daily.