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 PROB
- 99%
- EPSS %ILE
- 100%
- KEV
- ⚠ Exploited
Published
February 18, 2022
Last Modified
November 10, 2025
Advisory Details (6)
Auto-updated Sep 5, 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-09-08 | 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.
Affected Packages
(5 across 5 ecosystems)
Debian:10(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| redis | 5:5.0.14-1+deb10u1 ... 5:5.0.7-7~bpo10+1 (20 versions) | 5:5.0.14-1+deb10u2 | — |
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| redis | 5:6.0.15-1, 5:6.0.16-1, 5:6.0.16-1+deb11u1, 5:6.0.16-1~bpo10+1, 5:6.0.16-1~bpo11+1 | 5:6.0.16-1+deb11u2 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| redis | — | 5:6.0.16-2 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| redis | — | 5:6.0.16-2 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| redis | — | 5:6.0.16-2 | — |
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 68× in last 7d / 344× 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 1,108 total refreshes for this CVE.
- 2026-09-08 13:05 UTCGHSA enrichment
- 2026-09-08 09:07 UTCGHSA enrichment
- 2026-09-08 05:07 UTCGHSA enrichment
- 2026-09-08 01:07 UTCVendor advisory
- 2026-09-08 01:07 UTCGHSA enrichment
- 2026-09-07 21:11 UTCVendor advisory
- 2026-09-07 21:11 UTCGHSA enrichment
- 2026-09-07 17:13 UTCVendor advisory
- 2026-09-07 17:13 UTCGHSA enrichment
- 2026-09-07 13:15 UTCGHSA enrichment
- 2026-09-07 09:16 UTCGHSA enrichment
- 2026-09-07 05:16 UTCGHSA enrichment
- 2026-09-07 01:16 UTCVendor advisory
- 2026-09-07 01:16 UTCGHSA enrichment
- 2026-09-06 21:19 UTCVendor advisory
- 2026-09-06 21:19 UTCGHSA enrichment
- 2026-09-06 17:22 UTCVendor advisory
- 2026-09-06 17:22 UTCGHSA enrichment
- 2026-09-06 13:24 UTCVendor advisory
- 2026-09-06 13:24 UTCGHSA enrichment
- 2026-09-06 09:27 UTCVendor advisory
- 2026-09-06 09:27 UTCGHSA enrichment
- 2026-09-06 05:30 UTCVendor advisory
- 2026-09-06 05:30 UTCGHSA enrichment
- 2026-09-06 01:33 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-06 01:33 UTCGHSA enrichment
- 2026-09-05 21:36 UTCVendor advisory
- 2026-09-05 21:36 UTCGHSA enrichment
- 2026-09-05 17:39 UTCEG score recompute
- 2026-09-05 17:39 UTCVendor advisory
- 2026-09-05 17:39 UTCGHSA enrichment
- 2026-09-05 15:25 UTCEPSS rescore
- 2026-09-05 13:39 UTCVendor advisory
- 2026-09-05 13:39 UTCGHSA enrichment
- 2026-09-05 09:40 UTCVendor advisory
- 2026-09-05 09:40 UTCGHSA enrichment
- 2026-09-05 05:43 UTCVendor advisory
- 2026-09-05 05:43 UTCGHSA enrichment
- 2026-09-05 01:46 UTCVendor advisory
- 2026-09-05 01:46 UTCGHSA enrichment
- 2026-09-04 21:49 UTCVendor advisory
- 2026-09-04 21:49 UTCGHSA enrichment
- 2026-09-04 17:52 UTCGHSA enrichment
- 2026-09-04 17:38 UTCCISA KEV update
- 2026-09-04 13:54 UTCVendor advisory
- 2026-09-04 13:54 UTCGHSA enrichment
- 2026-09-04 09:56 UTCGHSA enrichment
- 2026-09-04 05:55 UTCGHSA enrichment
- 2026-09-04 01:56 UTCGHSA enrichment
- 2026-09-03 21:58 UTCVendor advisory
- 2026-09-03 21:57 UTCGHSA enrichment
- 2026-09-03 17:57 UTCGHSA enrichment
- 2026-09-03 13:59 UTCGHSA enrichment
- 2026-09-03 10:01 UTCVendor advisory
- 2026-09-03 10:01 UTCGHSA enrichment
- 2026-09-03 06:03 UTCGHSA enrichment
- 2026-09-03 02:04 UTCGHSA enrichment
- 2026-09-02 22:04 UTCGHSA enrichment
- 2026-09-02 18:06 UTCGHSA enrichment
- 2026-09-02 17:33 UTCCISA KEV update
- 2026-09-02 14:08 UTCGHSA enrichment
- 2026-09-02 10:12 UTCGHSA enrichment
- 2026-09-02 06:14 UTCGHSA enrichment
- 2026-09-02 02:16 UTCGHSA enrichment
- 2026-09-01 22:16 UTCVendor advisory
- 2026-09-01 22:16 UTCGHSA enrichment
- 2026-09-01 18:19 UTCGHSA enrichment
- 2026-09-01 14:22 UTCGHSA enrichment
- 2026-09-01 10:24 UTCGHSA enrichment
- 2026-09-01 06:27 UTCGHSA enrichment
- 2026-09-01 02:29 UTCGHSA enrichment
- 2026-08-31 22:29 UTCVendor advisory
- 2026-08-31 22:29 UTCGHSA enrichment
- 2026-08-31 18:32 UTCGHSA enrichment
- 2026-08-31 14:34 UTCGHSA enrichment
- 2026-08-31 14:19 UTCCISA KEV update
- 2026-08-31 10:36 UTCGHSA enrichment
- 2026-08-31 06:37 UTCVendor advisory
- 2026-08-31 06:37 UTCGHSA enrichment
- 2026-08-31 02:40 UTCVendor advisory
- 2026-08-31 02:39 UTCGHSA enrichment
- 2026-08-30 22:42 UTCEG score recompute
- 2026-08-30 22:42 UTCVendor advisory
- 2026-08-30 22:42 UTCGHSA enrichment
- 2026-08-30 19:14 UTCEPSS rescore
- 2026-08-30 18:45 UTCVendor advisory
- 2026-08-30 18:45 UTCGHSA enrichment
- 2026-08-30 14:48 UTCVendor advisory
- 2026-08-30 14:48 UTCGHSA enrichment
- 2026-08-30 10:49 UTCGHSA enrichment
- 2026-08-30 06:50 UTCGHSA enrichment
- 2026-08-30 02:52 UTCVendor advisory
- 2026-08-30 02:52 UTCGHSA enrichment
- 2026-08-29 22:55 UTCVendor advisory
- 2026-08-29 22:55 UTCGHSA enrichment
- 2026-08-29 18:57 UTCGHSA enrichment
- 2026-08-29 14:59 UTCVendor advisory
- 2026-08-29 14:59 UTCGHSA enrichment
- 2026-08-29 11:01 UTCGHSA enrichment
- 2026-08-29 07:01 UTCVendor advisory
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 ↗
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
See which npm, PyPI, Go, and Maven packages are affected by 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.