CVE-2025-27151 [Medium]

Redis is an open source, in-memory database that persists on disk. In versions starting from 7.0.0 to before 8.0.2, a stack-based buffer overflow exists in redis-check-aof due to the use of memcpy with strlen(filepath) when copying a user-supplied file path into a fixed-size stack buffer. This allows an attacker to overflow the stack and potentially achieve code execution. This issue has been patched in version 8.0.2.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-03-25	0.06%	0.27%	+0.21%
2	2025-12-23	0.05%	0.06%	+0.01%
3	2025-11-24	—	0.05%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-03-25

0.06%

0.27%

+0.21%

2025-12-23

0.05%

0.06%

+0.01%

2025-11-24

—

0.05%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
4.7	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/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:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.0	3.6	[email protected]
9.8	3.1	CRITICAL	`CVSS:3.1/AV:N/AC:L/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:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. 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.	3.9	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

4.7

3.1

MEDIUM

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/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:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.0

3.6

[email protected]

9.8

3.1

CRITICAL

CVSS:3.1/AV:N/AC:L/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:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
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.

3.9

5.9

[email protected]

OS Trackers for CVE-2025-27151

vendor	priority	summary	link
`alpine`	—	CVE-2025-27151: 3 source package rows (redict, redis, valkey); 67 state rows across 9 repos (3.18-main, 3.19-main, 3.20-main, 3.21-community, 3.21-main, 3.22-community, 3.22-main, edge-community, edge-main); fixed 15, open 52.	https://security.alpinelinux.org/vuln/CVE-2025-27151
`debian`	unimportant	CVE-2025-27151 unimportant 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-27151
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2025-27151
`suse`	medium	CVE-2025-27151 severity moderate: SUSE including 21 source package names (8.0.2-2.17:valkey-8.0.2-150600.13.11.1, redis, …), 48 product×package rows across 27 product lines (Container private-registry/harbor-valkey, Image pr_15_6, … (27 product lines)): Fixed 29, Known Not Affected 19.	https://www.suse.com/security/cve/CVE-2025-27151/
`ubuntu`	medium	CVE-2025-27151 medium priority: Ubuntu including 1 source packages (redis), 10 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 6, ignored 2, needed 1, released 1.	https://ubuntu.com/security/CVE-2025-27151

Affected software / configurations for CVE-2025-27151

Vendor	Product	Version	Raw CPE
redis	redis	>= 7.0.0, < 7.2.9	cpe:2.3:a:redis:redis::::::::
redis	redis	>= 7.4.0, < 7.4.4	cpe:2.3:a:redis:redis::::::::
redis	redis	>= 8.0.0, < 8.0.2	cpe:2.3:a:redis:redis::::::::

References for CVE-2025-27151

URL	Tags
https://github.com/redis/redis/commit/643b5db235cb82508e72f11c7b4bbfc7dc39be56	Patch
https://github.com/redis/redis/releases/tag/8.0.2	Release Notes
https://github.com/redis/redis/security/advisories/GHSA-5453-q98w-cmvm	Third Party Advisory

URL

CVE-2025-27151 | redis-check-aof may lead to stack overflow and potential RCE

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

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

Weakness enumeration for CVE-2025-27151

OS Trackers for CVE-2025-27151

Affected software / configurations for CVE-2025-27151

References for CVE-2025-27151