CVE-2025-32023 [High] | RCE in Redis

Redis is an open source, in-memory database that persists on disk. From 2.8 to before 8.0.3, 7.4.5, 7.2.10, and 6.2.19, an authenticated user may use a specially crafted string to trigger a stack/heap out of bounds write on hyperloglog operations, potentially leading to remote code execution. The bug likely affects all Redis versions with hyperloglog operations implemented. This vulnerability is fixed in 8.0.3, 7.4.5, 7.2.10, and 6.2.19. An additional workaround to mitigate the problem without patching the redis-server executable is to prevent users from executing hyperloglog operations. This can be done using ACL to restrict HLL commands.

EDB-ID	Source	Kind	Published	Link
52477	exploit_db	edb	2026-02-04	Exploit-DB ↗

EDB-ID

Source

Kind

Published

Link

52477

exploit_db

edb

2026-02-04

Exploit-DB ↗

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-05-03	12.62%	18.44%	+5.82%
2	2026-04-30	12.78%	12.62%	-0.16%
3	2026-04-28	—	12.78%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-05-03

12.62%

18.44%

+5.82%

2026-04-30

12.78%

12.62%

-0.16%

2026-04-28

—

12.78%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.0	3.1	HIGH	`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. 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.	1.0	5.9	[email protected]
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. 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.	1.8	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.0

3.1

HIGH

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
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.

1.0

5.9

[email protected]

7.8

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
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.

1.8

5.9

[email protected]

OS Trackers for CVE-2025-32023

vendor	priority	summary	link
`alpine`	—	CVE-2025-32023: 3 source package rows (redict, redis, valkey); 98 state rows across 7 repos (3.19-main, 3.20-main, 3.21-main, 3.22-community, 3.22-main, edge-community, edge-main); fixed 13, open 85.	https://security.alpinelinux.org/vuln/CVE-2025-32023
`debian`	not yet assigned	CVE-2025-32023 not yet assigned priority: Debian including 3 source packages (redict, redis, valkey), 10 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 10.	https://security-tracker.debian.org/tracker/CVE-2025-32023
`gentoo`	high	CVE-2025-32023: 1 GLSA(s) (202511-05), 2 atom(s) (dev-db/redict, dev-db/redis); latest impact high.	https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2025-32023
`redhat`	high	—	https://access.redhat.com/security/cve/CVE-2025-32023
`suse`	high	CVE-2025-32023 severity important: SUSE including 25 source package names (8.0.2-2.17:valkey-8.0.2-150600.13.14.1, redis-6.0.14-150200.6.40.1, …), 49 product×package rows across 26 product lines (Container private-registry/harbor-valkey, Image pr_15_6, … (26 product lines)): Fixed 49.	https://www.suse.com/security/cve/CVE-2025-32023/
`ubuntu`	medium	CVE-2025-32023 medium priority: Ubuntu including 3 source packages (redict, redis, valkey), 22 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 6, needed 6, released 4, DNE 3, needs-triage 2, not-affected 1.	https://ubuntu.com/security/CVE-2025-32023

Affected software / configurations for CVE-2025-32023

Vendor	Product	Version	Raw CPE
redis	redis	>= 2.8.0, < 6.2.19	cpe:2.3:a:redis:redis::::::::
redis	redis	>= 7.2.0, < 7.2.10	cpe:2.3:a:redis:redis::::::::
redis	redis	>= 7.4.0, < 7.4.5	cpe:2.3:a:redis:redis::::::::
redis	redis	>= 8.0.0, < 8.0.3	cpe:2.3:a:redis:redis::::::::

References for CVE-2025-32023

URL	Tags
https://github.com/redis/redis/commit/50188747cbfe43528d2719399a2a3c9599169445	Patch
https://github.com/redis/redis/releases/tag/6.2.19	Release Notes
https://github.com/redis/redis/releases/tag/7.2.10	Release Notes
https://github.com/redis/redis/releases/tag/7.4.5	Release Notes
https://github.com/redis/redis/releases/tag/8.0.3	Release Notes
https://github.com/redis/redis/security/advisories/GHSA-rp2m-q4j6-gr43	Third Party Advisory
https://www.exploit-db.com/exploits/52477

URL

CVE-2025-32023 | Redis allows out of bounds writes in hyperloglog commands leading to RCE

Public exploit references (Exploit-DB) for CVE-2025-32023

Exploit prediction scoring system (EPSS) score for CVE-2025-32023

Common vulnerability scoring system (CVSS) metrics for CVE-2025-32023

Weakness enumeration for CVE-2025-32023

OS Trackers for CVE-2025-32023

Affected software / configurations for CVE-2025-32023

References for CVE-2025-32023