CVE-2025-67733 [High] | Security Vulnerability in Valkey

Valkey is a distributed key-value database. Prior to versions 9.0.2, 8.1.6, 8.0.7, and 7.2.12, a malicious user can use scripting commands to inject arbitrary information into the response stream for the given client, potentially corrupting or returning tampered data to other users on the same connection. The error handling code for lua scripts does not properly handle null characters. Versions 9.0.2, 8.1.6, 8.0.7, and 7.2.12 fix the issue.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.02%	0.41%	+0.40%
2	2026-02-24	—	0.02%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.02%

0.41%

+0.40%

2026-02-24

—

0.02%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
8.5	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/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: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:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	3.1	4.7	[email protected]
7.1	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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: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:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.8	4.2	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

8.5

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/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: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:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

3.1

4.7

[email protected]

7.1

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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: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:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.8

4.2

[email protected]

OS Trackers for CVE-2025-67733

vendor	priority	summary	link
`alpine`	—	CVE-2025-67733: 1 source package rows (valkey); 30 state rows across 5 repos (3.20-main, 3.21-main, 3.22-main, 3.23-main, edge-main); fixed 4, open 26.	https://security.alpinelinux.org/vuln/CVE-2025-67733
`debian`	unimportant	CVE-2025-67733 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-67733
`redhat`	high	—	https://access.redhat.com/security/cve/CVE-2025-67733
`suse`	medium	CVE-2025-67733 severity moderate: SUSE including 9 source package names (valkey-8.0.7-150600.13.20.1, valkey-8.0.7-150700.3.14.1, …), 9 product×package rows across 3 product lines (SUSE Linux Enterprise Module for Server Applications 15 SP7, openSUSE Leap 15.6, openSUSE Tumbleweed): Fixed 6, First Fixed 3.	https://www.suse.com/security/cve/CVE-2025-67733/
`ubuntu`	medium	CVE-2025-67733 medium priority: Ubuntu including 1 source packages (valkey), 4 status rows across 4 suites (jammy, noble, questing, upstream): released 2, DNE 1, needs-triage 1.	https://ubuntu.com/security/CVE-2025-67733

Affected software / configurations for CVE-2025-67733

Vendor	Product	Version	Raw CPE
lfprojects	valkey	< 7.2.12	cpe:2.3:a:lfprojects:valkey::::::::
lfprojects	valkey	>= 8.0.0, < 8.0.7	cpe:2.3:a:lfprojects:valkey::::::::
lfprojects	valkey	>= 8.1.0, < 8.1.6	cpe:2.3:a:lfprojects:valkey::::::::
lfprojects	valkey	>= 9.0.0, < 9.0.2	cpe:2.3:a:lfprojects:valkey::::::::

References for CVE-2025-67733

URL	Tags
https://github.com/valkey-io/valkey/security/advisories/GHSA-p876-p7q5-hv2m	Vendor Advisory

URL

CVE-2025-67733 | Valkey Affected by RESP Protocol Injection via Lua error_reply

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

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

Weakness enumeration for CVE-2025-67733

OS Trackers for CVE-2025-67733

Affected software / configurations for CVE-2025-67733

References for CVE-2025-67733