CVE-2021-32687: Integer overflow issue with intsets in Redis
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 4% (FIRST EPSS); higher than 90.7% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: redis (AlmaLinux:8) 5.0.3-5.module_el8.4.0+2583+b9845322, 6.0.9-5.module_el8.4.0+2584+1bb0d2aa, 6.0.9-5.module_el8.5.0+67+a3c431d9; redis-devel (AlmaLinux:8) 6.0.9-5.module_el8.5.0+67+a3c431d9, 5.0.3-5.module_el8.4.0+2583+b9845322, 5.0.3-5.module_el8.5.0+66+fc19ec12; redis-doc (AlmaLinux:8) 5.0.3-5.module_el8.4.0+2583+b9845322, 6.0.9-5.module_el8.4.0+2584+1bb0d2aa.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to redis (AlmaLinux:8) 5.0.3-5.module_el8.4.0+2583+b9845322, 6.0.9-5.module_el8.4.0+2584+1bb0d2aa, 6.0.9-5.module_el8.5.0+67+a3c431d9; redis-devel (AlmaLinux:8) 6.0.9-5.module_el8.5.0+67+a3c431d9, 5.0.3-5.module_el8.4.0+2583+b9845322, 5.0.3-5.module_el8.5.0+66+fc19ec12; redis-doc (AlmaLinux:8) 5.0.3-5.module_el8.4.0+2583+b9845322, 6.0.9-5.module_el8.4.0+2584+1bb0d2aa or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Redis is an open source, in-memory database that persists on disk. An integer overflow bug affecting all versions of Redis can be exploited to corrupt the heap and potentially be used to leak arbitrary contents of the heap or trigger remote code execution. The vulnerability involves changing the default set-max-intset-entries configuration parameter to a very large value and constructing specially crafted commands to manipulate sets. The problem is fixed in Redis versions 6.2.6, 6.0.16 and 5.0.14. An additional workaround to mitigate the problem without patching the redis-server executable is to prevent users from modifying the set-max-intset-entries configuration parameter. This can be done using ACL to restrict unprivileged users from using the CONFIG SET command.
- Published
- Oct 4, 2021
- Updated
- Jun 16, 2026
- EPSS
- 4.0% · 90th percentile
- CWE
- CWE-190
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.0%
CNA vs NVD score
- NVD
- 7.5
- CNA · GitHub_M
- 7.5
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| redis | redis | cpe:2.3:a:redis:redis |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| netapp | management services for element software | cpe:2.3:a:netapp:management_services_for_element_software |
| netapp | management services for netapp hci | cpe:2.3:a:netapp:management_services_for_netapp_hci |
| oracle | communications operations monitor | cpe:2.3:a:oracle:communications_operations_monitor |
Using redis? Add it to your stack and be the first to know about CVEs like this one. (Redis)
Is Redis on your server exposed to the internet?
The free port scanner finds the open ports on your server and matches the service versions it can read against known vulnerabilities. No account needed.
Run a port scanAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redis redis5.0.0 and later · before 5.0.14
- redis redis6.0.0 and later · before 6.0.16
- redis redis6.2.0 and later · before 6.2.6
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
redis redis
- < 5.0.14, >= 6.0.0, < 6.0.16, >= 6.2.0, < 6.2.6affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | redis | before 5.0.3-5.module_el8.4.0+2583+b9845322 | 5.0.3-5.module_el8.4.0+2583+b9845322 |
| AlmaLinux:8 | redis | before 6.0.9-5.module_el8.4.0+2584+1bb0d2aa | 6.0.9-5.module_el8.4.0+2584+1bb0d2aa |
| AlmaLinux:8 | redis | before 6.0.9-5.module_el8.5.0+67+a3c431d9 | 6.0.9-5.module_el8.5.0+67+a3c431d9 |
| AlmaLinux:8 | redis | before 5.0.3-5.module_el8.5.0+66+fc19ec12 | 5.0.3-5.module_el8.5.0+66+fc19ec12 |
| AlmaLinux:8 | redis-devel | before 6.0.9-5.module_el8.5.0+67+a3c431d9 | 6.0.9-5.module_el8.5.0+67+a3c431d9 |
| AlmaLinux:8 | redis-devel | before 5.0.3-5.module_el8.4.0+2583+b9845322 | 5.0.3-5.module_el8.4.0+2583+b9845322 |
| AlmaLinux:8 | redis-devel | before 5.0.3-5.module_el8.5.0+66+fc19ec12 | 5.0.3-5.module_el8.5.0+66+fc19ec12 |
| AlmaLinux:8 | redis-devel | before 6.0.9-5.module_el8.4.0+2584+1bb0d2aa | 6.0.9-5.module_el8.4.0+2584+1bb0d2aa |
| AlmaLinux:8 | redis-doc | before 5.0.3-5.module_el8.4.0+2583+b9845322 | 5.0.3-5.module_el8.4.0+2583+b9845322 |
| AlmaLinux:8 | redis-doc | before 6.0.9-5.module_el8.4.0+2584+1bb0d2aa | 6.0.9-5.module_el8.4.0+2584+1bb0d2aa |
| Alpine:v3.11 | redis | from 5.0.0 · before 5.0.14-r0 | 5.0.14-r0 |
| Alpine:v3.13 | redis | from 5.0.0 · before 6.0.16-r0 | 6.0.16-r0 |
| Alpine:v3.14 | redis | from 5.0.0 · before 6.2.6-r0 | 6.2.6-r0 |
| Debian:10 | redis | before 5:5.0.14-1+deb10u1 | 5:5.0.14-1+deb10u1 |
| Debian:11 | redis | before 5:6.0.16-1+deb11u1 | 5:6.0.16-1+deb11u1 |
| Debian:12 | redis | before 5:6.0.16-1 | 5:6.0.16-1 |
| Debian:9 | redis | before 3:3.2.6-3+deb9u8 | 3:3.2.6-3+deb9u8 |
| openSUSE:Leap 15.3 | redis | before 6.0.14-6.8.1 | 6.0.14-6.8.1 |
| openSUSE:Tumbleweed | redis | before 6.2.6-1.1 | 6.2.6-1.1 |
| Red Hat:enterprise_linux:8::appstream | redis | before 0:5.0.3-5.module+el8.4.0+12927+b9845322 | 0:5.0.3-5.module+el8.4.0+12927+b9845322 |
| Red Hat:enterprise_linux:8::appstream | redis | before 0:6.0.9-5.module+el8.4.0+12929+1bb0d2aa | 0:6.0.9-5.module+el8.4.0+12929+1bb0d2aa |
| Red Hat:enterprise_linux:8::appstream | redis-debuginfo | before 0:6.0.9-5.module+el8.4.0+12929+1bb0d2aa | 0:6.0.9-5.module+el8.4.0+12929+1bb0d2aa |
| Red Hat:enterprise_linux:8::appstream | redis-debuginfo | before 0:5.0.3-5.module+el8.4.0+12927+b9845322 | 0:5.0.3-5.module+el8.4.0+12927+b9845322 |
| Red Hat:enterprise_linux:8::appstream | redis-debugsource | before 0:6.0.9-5.module+el8.4.0+12929+1bb0d2aa | 0:6.0.9-5.module+el8.4.0+12929+1bb0d2aa |
+24
Same product
redis: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0543It was discovered, that redis, a persistent key-value database, due to a packaging issue, is prone to a (Debian-specific) Lua sandbox escapeKEV100Now
- CVE-2025-49844Redis Lua Use-After-Free may lead to remote code execution64This week
- CVE-2023-36824Heap overflow in COMMAND GETKEYS and ACL evaluation in Redis58Plan
Published before and after this one in the same product
- ← EarlierCVE-2021-32672Oct 4, 2021 · Vulnerability in Lua Debugger in Redis18Monitor
- ← EarlierCVE-2021-32675Oct 4, 2021 · DoS vulnerability in Redis35Monitor
- Later →CVE-2021-32762Oct 4, 2021 · Integer overflow that can lead to heap overflow in redis-cli, redis-sentinel on some platforms36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:redis | 5.0.3-5.module_el8.4.0+2583+b9845322 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:redis-devel | 5.0.3-5.module_el8.5.0+66+fc19ec12 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:redis-doc | 5.0.3-5.module_el8.4.0+2583+b9845322 · AlmaLinux:8 | Package registry (OSV) |
| alpine:redis | 5.0.14-r0 · Alpine:v3.11 | Package registry (OSV) |
| debian:redis | 5:6.0.16-1 · Debian:12 | Package registry (OSV) |
| opensuse:redis | 6.0.14-6.8.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| red hat:redis | 0:5.0.3-5.module+el8.4.0+12927+b9845322 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:redis-debuginfo | 0:5.0.3-5.module+el8.4.0+12927+b9845322 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:redis-debugsource | 0:5.0.3-5.module+el8.4.0+12927+b9845322 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:redis-devel | 0:5.0.3-5.module+el8.4.0+12927+b9845322 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:redis-doc | 0:5.0.3-5.module+el8.4.0+12927+b9845322 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:rh-redis5-redis | 0:5.0.5-3.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-redis5-redis-debuginfo | 0:5.0.5-3.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| rocky linux:redis | 0:5.0.3-5.module+el8.5.0+657+2674830e · Rocky Linux:8 | Package registry (OSV) |
| suse:redis | 6.0.14-6.8.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-21-0989 · Dec 13, 2021(IBM Güvenlik Bildirimi)
- TR-21-0801 · Oct 5, 2021(Redis Güvenlik Zafiyeti)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- github.com/redis/redis/security/advisories/GHSA-m3mf-8x9w-r27q
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HTYQ5ZF37HNGTZWVNJD3VXP7I6MEEF42/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VL5KXFN3ATM7IIM7Q4O4PWTSRGZ5744Z/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WR5WKJWXD4D6S3DJCZ56V74ESLTDQRAB/
- security.gentoo.org/glsa/202209-17
- security.netapp.com/advisory/ntap-20211104-0003/
- www.debian.org/security/2021/dsa-5001
- www.oracle.com/security-alerts/cpuapr2022.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.