Redis Unix-domain socket may have be exposed with the wrong permissions for a short time window.
Noroxi assessment
Priority: Monitor (action score 14/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: 0.43% (FIRST EPSS).
- Someone with local access to the system 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) 6.2.17-1.module_el8.10.0+3946+3de613d5; redis-devel (AlmaLinux:8) 6.2.17-1.module_el8.10.0+3946+3de613d5; redis-doc (AlmaLinux:8) 6.2.17-1.module_el8.10.0+3946+3de613d5.
Low priority for now. Upgrade to redis (AlmaLinux:8) 6.2.17-1.module_el8.10.0+3946+3de613d5; redis-devel (AlmaLinux:8) 6.2.17-1.module_el8.10.0+3946+3de613d5; redis-doc (AlmaLinux:8) 6.2.17-1.module_el8.10.0+3946+3de613d5 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 in-memory database that persists on disk. On startup, Redis begins listening on a Unix socket before adjusting its permissions to the user-provided configuration. If a permissive umask(2) is used, this creates a race condition that enables, during a short period of time, another process to establish an otherwise unauthorized connection. This problem has existed since Redis 2.6.0-RC1. This issue has been addressed in Redis versions 7.2.2, 7.0.14 and 6.2.14. Users are advised to upgrade. For users unable to upgrade, it is possible to work around the problem by disabling Unix sockets, starting Redis with a restrictive umask, or storing the Unix socket file in a protected directory.
- Published
- Oct 18, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 36th percentile
- CWE
- CWE-668
Report tools
Action score
14
Monitor
Low priority for now.
- CVSS
- 14 / 40 · 3.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CNA vs NVD score
- NVD
- 3.6
- CNA · GitHub_M
- 3.6
- 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 |
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 redis2.6.0 and later · before 6.2.14
- redis redis7.0.0 and later · before 7.0.14
- redis redis7.2.0 and later · before 7.2.2
- redis redis2.6.0
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
- >= 2.6.0-rc1, < 6.2.14, >= 7.0.0, < 7.0.14, >= 7.1.0, < 7.2.2affected
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 6.2.17-1.module_el8.10.0+3946+3de613d5 | 6.2.17-1.module_el8.10.0+3946+3de613d5 |
| AlmaLinux:8 | redis-devel | before 6.2.17-1.module_el8.10.0+3946+3de613d5 | 6.2.17-1.module_el8.10.0+3946+3de613d5 |
| AlmaLinux:8 | redis-doc | before 6.2.17-1.module_el8.10.0+3946+3de613d5 | 6.2.17-1.module_el8.10.0+3946+3de613d5 |
| AlmaLinux:9 | redis | before 6.2.17-1.el9_5 | 6.2.17-1.el9_5 |
| AlmaLinux:9 | redis | before 7.2.6-1.module_el9.5.0+130+36ae7635 | 7.2.6-1.module_el9.5.0+130+36ae7635 |
| AlmaLinux:9 | redis-devel | before 7.2.6-1.module_el9.5.0+130+36ae7635 | 7.2.6-1.module_el9.5.0+130+36ae7635 |
| AlmaLinux:9 | redis-devel | before 6.2.17-1.el9_5 | 6.2.17-1.el9_5 |
| AlmaLinux:9 | redis-doc | before 6.2.17-1.el9_5 | 6.2.17-1.el9_5 |
| AlmaLinux:9 | redis-doc | before 7.2.6-1.module_el9.5.0+130+36ae7635 | 7.2.6-1.module_el9.5.0+130+36ae7635 |
| Alpine:v3.15 | redis | from 2.6.0 · before 6.2.14-r0 | 6.2.14-r0 |
| Alpine:v3.16 | redis | from 2.6.0 · before 7.0.14-r0 | 7.0.14-r0 |
| Alpine:v3.19 | redis | from 2.6.0 · before 7.2.2-r0 | 7.2.2-r0 |
| Debian:10 | redis | before 5:5.0.14-1+deb10u5 | 5:5.0.14-1+deb10u5 |
| Debian:11 | redis | before 5:6.0.16-1+deb11u3 | 5:6.0.16-1+deb11u3 |
| Debian:12 | redis | before 5:7.0.15-1~deb12u1 | 5:7.0.15-1~deb12u1 |
| Debian:13 | redis | before 5:7.0.14-1 | 5:7.0.14-1 |
| openSUSE:Tumbleweed | redis | before 7.2.2-1.1 | 7.2.2-1.1 |
| Red Hat:enterprise_linux:8::appstream | redis | before 0:6.2.17-1.module+el8.10.0+22680+748527fd | 0:6.2.17-1.module+el8.10.0+22680+748527fd |
| Red Hat:enterprise_linux:8::appstream | redis-debuginfo | before 0:6.2.17-1.module+el8.10.0+22680+748527fd | 0:6.2.17-1.module+el8.10.0+22680+748527fd |
| Red Hat:enterprise_linux:8::appstream | redis-debugsource | before 0:6.2.17-1.module+el8.10.0+22680+748527fd | 0:6.2.17-1.module+el8.10.0+22680+748527fd |
| Red Hat:enterprise_linux:8::appstream | redis-devel | before 0:6.2.17-1.module+el8.10.0+22680+748527fd | 0:6.2.17-1.module+el8.10.0+22680+748527fd |
| Red Hat:enterprise_linux:8::appstream | redis-doc | before 0:6.2.17-1.module+el8.10.0+22680+748527fd | 0:6.2.17-1.module+el8.10.0+22680+748527fd |
| Red Hat:enterprise_linux:9::appstream | redis | before 0:7.2.6-1.module+el9.5.0+22422+63e067d8 | 0:7.2.6-1.module+el9.5.0+22422+63e067d8 |
| Red Hat:enterprise_linux:9::appstream | redis | before 0:6.2.17-1.el9_5 | 0:6.2.17-1.el9_5 |
+15
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-31294Jul 15, 2023 · Redis before 6cbea7d allows a replica to cause an assertion failure in a primary server by sending a non-administrative command (specificall23Monitor
- ← EarlierCVE-2023-41053Sep 6, 2023 · Redis SORT_RO may bypass ACL configuration13Monitor
- Later →CVE-2023-41056Jan 10, 2024 · Redis vulnerable to integer overflow in certain payloads33Monitor
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 | 7.2.6-1.module_el9.5.0+130+36ae7635 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:redis-devel | 7.2.6-1.module_el9.5.0+130+36ae7635 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:redis-doc | 7.2.6-1.module_el9.5.0+130+36ae7635 · AlmaLinux:9 | Package registry (OSV) |
| alpine:redis | 6.2.14-r0 · Alpine:v3.15 | Package registry (OSV) |
| debian:redis | 5:7.0.15-1~deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:redis | 6.2.6-150400.3.25.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:redis7 | 7.0.8-150500.3.9.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| red hat:redis | 0:7.2.6-1.module+el9.5.0+22422+63e067d8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:redis-debuginfo | 0:7.2.6-1.module+el9.5.0+22422+63e067d8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:redis-debugsource | 0:7.2.6-1.module+el9.5.0+22422+63e067d8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:redis-devel | 0:7.2.6-1.module+el9.5.0+22422+63e067d8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:redis-doc | 0:7.2.6-1.module+el9.5.0+22422+63e067d8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| rocky linux:redis | 0:6.2.17-1.module+el8.10.0+1923+5b85c6a7 · Rocky Linux:8 | Package registry (OSV) |
| suse:redis | 6.2.6-150400.3.25.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP4 | Package registry (OSV) |
| suse:redis7 | 7.0.8-150500.3.9.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP5 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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.
Technical details
Attack conditions
- Someone with local access to the system 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
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-668 · Exposure of Resource to Wrong SphereCVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- github.com/redis/redis/security/advisories/GHSA-ghmp-889m-7cvx
- lists.debian.org/debian-lts-announce/2023/10/msg00032.html
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/464JPNBWE433ZGYXO3KN72VR3KJPWHAW/
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BNEK2K4IE7MPKRD6H36JXZMJKYS6I5GQ/
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DZMGTTV5XM4LA66FSIJSETNBBRRPJYOQ/
- security.netapp.com/advisory/ntap-20231116-0014/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.