Threadlinqs IntelligenceStart free

VulnerabilityCVE-2022-0543Published 2022-02-18

CVE-2022-0543 — Redis

criticalCISA KEVRansomwarePublic exploit7 PoC reposNuclei template

As of 2026-05-21, CVE-2022-0543 is a CRITICAL-severity vulnerability in Redis, CVSS v3.1 10, EPSS 99.3% (99.9th percentile). It is listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-03-28), with a US federal remediation deadline of 2022-04-18, and CISA links it to known ransomware campaigns. Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2022-0543, most recently “P2Pinfect Kubernetes Compromise — Exposed Redis Enables Persistent GKE Botnet Enrollment with Six-Month Dormancy (CVE-2022-0543, CVE-2025-11953, CVE-2025-49844)”.

CVSS v3.1
10/10Critical
EPSS
99.3%Higher than 99.9% of scored CVEs
CISA KEV
ListedAdded · due 2022-04-18
Tracked threats
1Campaigns referencing it
Priority
10/10Threadlinqs triage score
Published
Updated 2026-05-21
CVSS v3.1 10 (CRITICAL) · EPSS 99.3% (higher than 99.9% of all scored CVEs) · Priority 10/10 · Published 2022-02-18

Last updated:

What is CVE-2022-0543?

It was discovered, that redis, a persistent key-value database, due to a packaging issue, is prone to a (Debian-specific) Lua sandbox escape, which could result in remote code execution.

The record classifies CVE-2022-0543 under weakness class CWE-862. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. 3 affected-product entries are recorded, across 3 vendors, listed below. The identifier was first published 1735 days ago.

Severity and exploitation probability

CVSS v3.1 base score
10 — CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS (FIRST)
99.3% probability of exploitation in the next 30 days, higher than 99.9% of all scored CVEs
CISA KEV
Listed since 2022-03-28, federal remediation deadline 2022-04-18 — used in known ransomware campaigns
Threadlinqs priority
10/10 — CISA lists it as used in ransomware, which Threadlinqs scores at the maximum
Published
2022-02-18

Is CVE-2022-0543 being exploited?

CISA added CVE-2022-0543 to the Known Exploited Vulnerabilities catalog on 2022-03-28, which means the agency holds evidence of exploitation in the wild; US federal civilian agencies had to remediate it by 2022-04-18 under BOD 22-01. CISA flags the vulnerability as one used in known ransomware campaigns. Weaponised exploit code for CVE-2022-0543 is publicly available. 7 public proof-of-concept repositories are tracked for this identifier. A ProjectDiscovery Nuclei detection template exists (network/cves/2022/CVE-2022-0543.yaml). It currently carries a trending score of 50 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2022-0543

The record marks a vendor fix as available for CVE-2022-0543. Patch reference: https://bugs.debian.org/1005787. Vendor advisory: https://www.debian.org/security/2022/dsa-5081. Because CVE-2022-0543 is KEV-listed, US federal civilian agencies were required to apply the vendor fix, or stop using the product, by 2022-04-18. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2022-0543

1 tracked threat in the Threadlinqs corpus references CVE-2022-0543, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Enriched from CVE.org, NVD, FIRST EPSS, CISA KEV, public proof-of-concept repositories, ProjectDiscovery Nuclei. This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Mailing list and disclosure

Other references