CVE-2023-41056 | Redis vulnerable to integer overflow in certain payloads

Redis is an in-memory database that persists on disk. Redis incorrectly handles resizing of memory buffers which can result in integer overflow that leads to heap overflow and potential remote code execution. This issue has been patched in version 7.0.15 and 7.2.4.

Published: 2024-01-10 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-41056 is rated Moderate Risk (56.8/100): CVSS High severity, with medium exploitation likelihood (EPSS 2.58%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-41056

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 7.32% 2.58% -4.74%
2 2026-05-27 7.51% 7.32% -0.18%
3 2026-05-22 — 7.51% —

Full EPSS history (33 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-41056

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.1 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.2 5.9 [email protected]
8.1 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.2 5.9 [email protected]

Weakness enumeration for CVE-2023-41056

OS Trackers for CVE-2023-41056

vendor priority summary link
alpine — CVE-2023-41056: 1 source package rows (redis); 27 state rows across 8 repos (3.17-main, 3.18-main, 3.19-main, 3.20-community, 3.21-community, 3.22-community, edge-community, edge-main); fixed 8, open 19. https://security.alpinelinux.org/vuln/CVE-2023-41056
debian unimportant CVE-2023-41056 unimportant priority: Debian including 1 source packages (redis), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2023-41056
gentoo normal CVE-2023-41056: 1 GLSA(s) (202408-05), 1 atom(s) (dev-db/redis); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2023-41056
redhat high — https://access.redhat.com/security/cve/CVE-2023-41056
suse high CVE-2023-41056 severity important: SUSE including 3 source package names (redis, redis-7.2.4-1.1, redis7), 24 product×package rows across 23 product lines (SUSE Enterprise Storage 7.1, SUSE Linux Enterprise High Performance Computing 15 SP2-LTSS, … (23 product lines)): Known Not Affected 23, Fixed 1. https://www.suse.com/security/cve/CVE-2023-41056/
ubuntu medium CVE-2023-41056 medium priority: Ubuntu including 1 source packages (redis), 9 status rows across 9 suites (bionic, focal, jammy, lunar, mantic, noble, trusty, upstream, xenial): not-affected 6, ignored 2, released 1. https://ubuntu.com/security/CVE-2023-41056

Affected software / configurations for CVE-2023-41056

Vendor Product Version Raw CPE
redis redis >= 7.0.9, < 7.0.15 cpe:2.3:a:redis:redis:*:*:*:*:*:*:*:*
redis redis >= 7.2.0, < 7.2.4 cpe:2.3:a:redis:redis:*:*:*:*:*:*:*:*
fedoraproject fedora 38 cpe:2.3:o:fedoraproject:fedora:38:*:*:*:*:*:*:*
fedoraproject fedora 39 cpe:2.3:o:fedoraproject:fedora:39:*:*:*:*:*:*:*

References for CVE-2023-41056

cvelogic Threat Intelligence