Skip to content
Weekly Signal
Live intelligence Updated 19 Aug 2026 · 20:27 UTC

Redis · Debian-specific Redis Servers, Redis

CVE-2022-0543

Debian-specific Redis Server Lua Sandbox Escape Vulnerability

Recommended action

Treat this as an immediate remediation priority. Apply updates per vendor instructions.

View response plan
CVSS10.0
EPSS99.3%
KEVYes
ExploitationConfirmed exploitation
PatchPatch or guidance available ↓

Assessment

Why it matters

CISA lists this vulnerability as known to be exploited; exploitation is confirmed; EPSS is 99.3%; technical severity is CVSS 10.0.

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.

Who should care

  • Teams operating Debian-specific Redis Servers, Redis
  • Vulnerability and exposure management teams
  • Security operations teams monitoring exploitation activity

Response plan

What I would do

  1. Confirm whether Debian-specific Redis Servers, Redis is present in the environment.
  2. Identify affected versions and establish whether vulnerable services are exposed or reachable.
  3. Apply updates per vendor instructions.
  4. Review relevant security telemetry for evidence of attempted or successful exploitation.
  5. Document the remediation decision and track it to verified completion.

Vendor remediation

Patch and remediation links

Use the vendor source below to confirm the correct fixed version, package or mitigation for your affected product.

Technical details

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CWE
CWE-862
Affected versions
Redis Debian-specific Redis Servers; Redis Redis (Version: -)
Published
18 February 2022
Attack vector
Network
Privileges required
None
User interaction
None

Signal timeline

  1. CVE published
  2. Added to CISA KEV
  3. Latest EPSS score: 99.3%
  4. Signal calculated at 85

External references

Live public intelligence This assessment combines public-source evidence. Validate the affected product, version and exposure against your own environment before making a risk decision.