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.
CVE-2022-0543
Score elevated to 10.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-28), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 10.0 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
A fix is available — apply it.
- CVSS v3
- 10.0
- EG Score
- 10.0(high)
- EG Risk
- 100(Act)EG Risk 100/100SSVC: Act
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity100% × 45%Exploitation100% × 40%Automatability100% × 15%Action: Fix now — active exploitation, automatable, high impact. - EPSS
- 99.9%
- KEV
- ⚠ Exploited
Published
February 18, 2022
Last Modified
November 10, 2025
Advisory Details (6)
Auto-updated Jul 18, 2026[SECURITY] [DSA 5081-1] redis security update
https://lists.debian.org/debian-security-announce/2022/msg00048.html#1005787 - redis: CVE-2022-0543 - Debian Bug report logs
https://bugs.debian.org/1005787Packet Storm Security
http://packetstormsecurity.com/files/166885/Redis-Lua-Sandbox-Escape.htmlAn unexpected Redis sandbox escape affecting only Debian, Ubuntu, and other Debian derivatives
https://www.ubercomp.com/posts/2022-01-20_redis_on_debian_rcePatch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | redis-tools (5:6.0.15-1ubuntu0.1) @ impish | 2026-07-22 | ubuntu |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 60× in last 7d / 315× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 598 total refreshes for this CVE.
- 2026-07-24 14:15 UTCEPSS rescore
- 2026-07-24 14:15 UTCEPSS rescore
- 2026-07-23 02:06 UTCEG score recompute
- 2026-07-22 23:53 UTCEG score recompute
- 2026-07-22 23:53 UTCVendor advisory
- 2026-07-22 23:53 UTCGHSA enrichment
- 2026-07-22 22:53 UTCEG score recompute
- 2026-07-22 19:55 UTCGHSA enrichment
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 15:57 UTCVendor advisory
- 2026-07-22 15:57 UTCGHSA enrichment
- 2026-07-22 11:59 UTCGHSA enrichment
- 2026-07-22 08:02 UTCGHSA enrichment
- 2026-07-22 04:05 UTCGHSA enrichment
- 2026-07-22 00:08 UTCGHSA enrichment
- 2026-07-21 20:10 UTCVendor advisory
- 2026-07-21 20:10 UTCGHSA enrichment
- 2026-07-21 16:12 UTCEG score recompute
- 2026-07-21 16:12 UTCGHSA enrichment
- 2026-07-21 15:22 UTCEPSS rescore
- 2026-07-21 15:22 UTCEPSS rescore
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 12:15 UTCGHSA enrichment
- 2026-07-21 08:17 UTCGHSA enrichment
- 2026-07-21 04:19 UTCVendor advisory
Show 75 moreShow fewer
- 2026-07-21 04:19 UTCGHSA enrichment
- 2026-07-21 00:21 UTCVendor advisory
- 2026-07-21 00:21 UTCGHSA enrichment
- 2026-07-20 20:24 UTCEG score recompute
- 2026-07-20 20:24 UTCVendor advisory
- 2026-07-20 20:23 UTCGHSA enrichment
- 2026-07-20 17:05 UTCEPSS rescore
- 2026-07-20 16:26 UTCVendor advisory
- 2026-07-20 16:25 UTCGHSA enrichment
- 2026-07-20 12:28 UTCVendor advisory
- 2026-07-20 12:28 UTCGHSA enrichment
- 2026-07-20 08:30 UTCVendor advisory
- 2026-07-20 08:29 UTCGHSA enrichment
- 2026-07-20 04:33 UTCVendor advisory
- 2026-07-20 04:32 UTCGHSA enrichment
- 2026-07-20 00:35 UTCGHSA enrichment
- 2026-07-19 20:37 UTCVendor advisory
- 2026-07-19 20:37 UTCGHSA enrichment
- 2026-07-19 16:40 UTCVendor advisory
- 2026-07-19 16:40 UTCGHSA enrichment
- 2026-07-19 12:43 UTCGHSA enrichment
- 2026-07-19 08:45 UTCVendor advisory
- 2026-07-19 08:45 UTCGHSA enrichment
- 2026-07-19 04:47 UTCVendor advisory
- 2026-07-19 04:47 UTCGHSA enrichment
- 2026-07-19 00:50 UTCVendor advisory
- 2026-07-19 00:50 UTCGHSA enrichment
- 2026-07-18 20:53 UTCVendor advisory
- 2026-07-18 20:53 UTCGHSA enrichment
- 2026-07-18 16:56 UTCVendor advisory
- 2026-07-18 16:56 UTCGHSA enrichment
- 2026-07-18 12:59 UTCVendor advisory
- 2026-07-18 12:59 UTCGHSA enrichment
- 2026-07-18 09:01 UTCVendor advisory
- 2026-07-18 09:01 UTCGHSA enrichment
- 2026-07-18 05:03 UTCGHSA enrichment
- 2026-07-18 01:06 UTCVendor advisory
- 2026-07-18 01:06 UTCGHSA enrichment
- 2026-07-17 21:09 UTCVendor advisory
- 2026-07-17 21:09 UTCGHSA enrichment
- 2026-07-17 17:11 UTCGHSA enrichment
- 2026-07-17 13:13 UTCGHSA enrichment
- 2026-07-17 09:16 UTCEG score recompute
- 2026-07-17 09:16 UTCGHSA enrichment
- 2026-07-17 05:18 UTCGHSA enrichment
- 2026-07-17 01:20 UTCGHSA enrichment
- 2026-07-16 21:22 UTCVendor advisory
- 2026-07-16 21:22 UTCGHSA enrichment
- 2026-07-16 17:25 UTCVendor advisory
- 2026-07-16 17:24 UTCGHSA enrichment
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 13:27 UTCGHSA enrichment
- 2026-07-16 09:30 UTCVendor advisory
- 2026-07-16 09:30 UTCGHSA enrichment
- 2026-07-16 05:33 UTCVendor advisory
- 2026-07-16 05:33 UTCGHSA enrichment
- 2026-07-16 01:36 UTCVendor advisory
- 2026-07-16 01:36 UTCGHSA enrichment
- 2026-07-15 21:38 UTCGHSA enrichment
- 2026-07-15 17:40 UTCVendor advisory
- 2026-07-15 17:40 UTCGHSA enrichment
- 2026-07-15 16:49 UTCCISA KEV update
- 2026-07-15 15:04 UTCCISA KEV update
- 2026-07-15 13:43 UTCVendor advisory
- 2026-07-15 13:43 UTCGHSA enrichment
- 2026-07-15 09:44 UTCGHSA enrichment
- 2026-07-15 05:45 UTCVendor advisory
- 2026-07-15 05:45 UTCGHSA enrichment
- 2026-07-15 01:48 UTCVendor advisory
- 2026-07-15 01:48 UTCGHSA enrichment
- 2026-07-14 21:51 UTCVendor advisory
- 2026-07-14 21:51 UTCGHSA enrichment
- 2026-07-14 18:05 UTCCISA KEV update
- 2026-07-14 17:54 UTCGHSA enrichment
- 2026-07-14 13:48 UTCGHSA enrichment
Publicly available exploits
(5 references)Working exploit code is in the public domain (1 Metasploit module) (3 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCSiennaSkies/redisHackFirst seen May 10, 2023
redis未授权、redis_CVE-2022-0543检测利用二合一脚本
Open source ↗ - GitHub PoCz92g/CVE-2022-0543First seen Jul 6, 2022
Redis 沙盒逃逸(CVE-2022-0543)POC&EXP
Open source ↗ - GitHub PoC0x7eTeam/CVE-2022-0543First seen Mar 16, 2022
CVE-2022-0543_RCE,Redis Lua沙盒绕过 命令执行
Open source ↗ - Metasploitexploit/linux/redis/redis_debian_sandbox_escape✓ verifiedFirst seen Feb 18, 2022
Redis Lua Sandbox Escape
Open source ↗ - Nucleinetwork/cves/2022/CVE-2022-0543.yamlFirst seen Jan 1, 2022
Redis Sandbox Escape - Remote Code Execution
Open source ↗
Related CVEs(same vendor + same CWE)
Same vendor
10 shownubuntu
Same CWE
10 shownCWE-862
Frequently asked(6)
What is CVE-2022-0543?
When was CVE-2022-0543 disclosed?
Is CVE-2022-0543 actively exploited?
What is the CVSS score of CVE-2022-0543?
Which products are affected by CVE-2022-0543?
How do I remediate CVE-2022-0543?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2022-0543
Is Your Infrastructure Affected by CVE-2022-0543?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.