CVE-2022-35951 [High] | Integer Overflow in Redis

Redis is an in-memory database that persists on disk. Versions 7.0.0 and above, prior to 7.0.5 are vulnerable to an Integer Overflow. Executing an `XAUTOCLAIM` command on a stream key in a specific state, with a specially crafted `COUNT` argument may cause an integer overflow, a subsequent heap overflow, and potentially lead to remote code execution. This has been patched in Redis version 7.0.5. No known workarounds exist.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	18.65%	2.72%	-15.93%
2	2026-06-09	36.94%	18.65%	-18.29%
3	2026-01-19	—	36.94%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

18.65%

2.72%

-15.93%

2026-06-09

36.94%

18.65%

-18.29%

2026-01-19

—

36.94%

—

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]
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

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]

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-2022-35951

vendor	priority	summary	link
`alpine`	critical	CVE-2022-35951: 1 source package rows (redis); 12 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 4.	https://security.alpinelinux.org/vuln/CVE-2022-35951
`debian`	unimportant	CVE-2022-35951 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-2022-35951
`gentoo`	high	CVE-2022-35951: 1 GLSA(s) (202209-17), 1 atom(s) (dev-db/redis); latest impact high.	https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2022-35951
`redhat`	high	—	https://access.redhat.com/security/cve/CVE-2022-35951
`suse`	high	CVE-2022-35951 severity important: SUSE including 2 source package names (redis, redis-7.0.5-1.1), 12 product×package rows across 12 product lines (SUSE Enterprise Storage 7, SUSE Linux Enterprise High Performance Computing 15 SP2-ESPOS, … (12 product lines)): Known Not Affected 11, Fixed 1.	https://www.suse.com/security/cve/CVE-2022-35951/
`ubuntu`	medium	CVE-2022-35951 medium priority: Ubuntu including 1 source packages (redis), 10 status rows across 10 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, trusty, upstream, xenial): not-affected 7, ignored 2, released 1.	https://ubuntu.com/security/CVE-2022-35951

Affected software / configurations for CVE-2022-35951

Vendor	Product	Version	Raw CPE
redis	redis	>= 7.0.0, < 7.0.5	cpe:2.3:a:redis:redis::::::::
fedoraproject	fedora	37	cpe:2.3:o:fedoraproject:fedora:37:::::::*

References for CVE-2022-35951

URL	Tags
https://github.com/redis/redis/security/advisories/GHSA-5gc4-76rx-22c9	Third Party Advisory
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/A7INCOOFPPEAKNDBZU3TIZJPYXBULI2C/
https://security.gentoo.org/glsa/202209-17	Third Party Advisory
https://security.netapp.com/advisory/ntap-20221020-0005/	Third Party Advisory

URL

CVE-2022-35951 | Redis subject to Integer Overflow leading to Remote Code Execution via Heap Overflow

Exploit prediction scoring system (EPSS) score for CVE-2022-35951

Common vulnerability scoring system (CVSS) metrics for CVE-2022-35951

Weakness enumeration for CVE-2022-35951

OS Trackers for CVE-2022-35951

Affected software / configurations for CVE-2022-35951

References for CVE-2022-35951